Accessibility
Last reviewed November 6, 2026. Our goal, how we test, what we know is not perfect yet, and how to tell us about a problem.
1. Our goal
We want everyone to be able to use xeaura.com and the websites we build, including people who use a screen reader, a keyboard instead of a mouse, zoomed-in text, captions or voice control.
Our goal is to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That goal covers xeaura.com, the Xeaura client app, and every client website we design and build.
WCAG is the international standard published by the World Wide Web Consortium (W3C). Level AA is the level the U.S. Department of Justice uses in its rule for state and local government websites.
2. How we test
Automated scans: before we release a new client website, or a demo we turn into a client's website, every page of it is scanned with axe, an open-source accessibility testing tool, against the WCAG 2.0, 2.1 and 2.2 level A and AA rules it can test. Each page is scanned at a phone width and a desktop width. The scan checks things a machine can see, such as missing image descriptions, form fields without labels, and text that does not stand out enough from its background.
A website cannot be released while the scan reports a critical or serious problem on any of its pages.
We are adding a manual keyboard check before each launch: a person going through the website with a keyboard only, checking that every link, button and form can be reached and used, that the order makes sense, and that you can always see where you are on the page.
3. Known limits
We are honest about what this does not cover yet:
Automated scans catch only part of the accessibility problems a website can have. They do not replace testing by people, including people with disabilities, and some problems will get past them.
A quick edit that changes only a website's details, and not its design or code, is not scanned again before it goes live.
Personal Pages are not scanned when they are released.
Content a client adds or changes themselves (their photos, documents, PDFs and videos), and services from other companies that appear on a site (such as maps, booking tools, payment pages, chat windows and social media feeds), may not meet our goal, and we cannot always change them.
Websites we built before November 6, 2026 were not all tested this way.
4. Report a problem
If something on xeaura.com, in the Xeaura client app or on a website we built is hard or impossible for you to use, please tell us. You do not need to know the technical cause.
Email support@xeaura.com or call (949) 328-7102. It helps to include the web address of the page, what you were trying to do, and what happened. If you use assistive technology, telling us which one helps us reproduce the problem.
We reply within 1 business day (Monday to Friday, 9am to 5pm Pacific Time). We will tell you what we found and what we will change.
For xeaura.com and the Xeaura client app, we can help you get the information or service another way in the meantime. For a website we built for a business, we will pass your request to that business straight away.
5. About this statement
This statement was written on November 6, 2026. We review it when our testing changes.
This page describes our goal and how we work. It is not a guarantee, and it does not change our service agreement. How we handle information is in our privacy policy.