How we test
Every audit has two layers: automatic checks across the whole site, and a person using your key pages the way customers with disabilities do.
The two layers
1. Automatic checks
We load every page in your sitemap in a real browser, wait for apps to load, and run the axe-core WCAG 2.2 rules plus our own checks for headings, zoom, page language and links that act like buttons.
Good at: missing labels, contrast, missing alt text. Blind to: whether things actually work.
2. A person, by hand
A tester goes through your key journeys with only a keyboard, then again with a screen reader, on desktop and phone. Every pop-up and app on those pages is opened and used.
Good at: keyboard traps, confusing announcements, focus that gets lost, alt text that is wrong.
Tools and browsers
Each pairing is a way real people commonly browse.
| Setup | Browser | What we check |
|---|---|---|
| Keyboard only | Chrome, Firefox, Safari | Every control reachable, visible focus, no traps, Escape closes pop-ups |
| NVDA (Windows) | Chrome, Firefox | Names, roles, prices, errors and live updates read correctly |
| VoiceOver (Mac) | Safari | The same, plus headings and landmarks |
| VoiceOver (iPhone) | Safari | Swipe order, tap targets, mobile menu and cart |
| Zoom and reflow | Chrome | Text at 200% and the page at 400% with no sideways scrolling |
What we promise, and what we don't
We promise to test against WCAG 2.2 Level AA, to report every problem we find in plain words, and to re-test after fixes.
We don't promise that a site is "100% compliant" or lawsuit-proof. No honest tester can. Websites change every time an app updates.
We are not a law firm. If you have received a demand letter, talk to a lawyer; we can share our report with them.