How we test
Every criterion is tested by hand, with the tools your users rely on
Automated scanners check only part of WCAG. We use them as a first pass, then test every criterion ourselves with screen readers, the keyboard, voice control, zoom and contrast settings. Here is exactly what that involves.
The process
Five steps, the same on every project
01
Scope
We agree on the screens and complete tasks to test, the standard and the platforms, following the W3C evaluation method (WCAG-EM).
02
Scan
Automated tools run on every screen in scope, including dialogs and error states. They point us to likely problems; they never decide a result.
03
Test by hand
We check every WCAG criterion on every screen against the W3C explanations of what it requires.
04
Use assistive technology
We complete each task with screen readers, the keyboard and voice control, on desktop and on real phones.
05
Report and retest
Each finding gets a severity, steps to reproduce and a recommended fix. After your team fixes issues, we retest.
The test kit
The assistive technology and tools we use
Every report lists the exact versions we tested with, so results can be reproduced and compared over time.
| What | On | What we check with it |
|---|---|---|
| Screen readers | NVDA and JAWS on Windows; VoiceOver on macOS | A full pass of every task in Firefox, Chrome and Safari |
| Mobile screen readers | VoiceOver on iPhone; TalkBack on Android | Every task at phone width, on physical devices |
| Keyboard only | Every platform above | Reaching and operating every control, focus order and focus visibility |
| Voice control | Dragon on Windows; Voice Control on macOS | Whether controls can be spoken by their visible names |
| Zoom and reflow | Browser zoom to 400%; text spacing overrides | Content that overlaps, is cut off or needs sideways scrolling |
| High contrast | Windows contrast themes; forced colors | Custom controls and focus indicators that disappear |
| Contrast measurement | Colour Contrast Analyser | Text, icons, borders and focus indicators |
| Automated tools | axe DevTools, WAVE, W3C HTML checker | A first pass only |
We also check content with reading tools such as Immersive Reader and automatic translation. Those checks go beyond WCAG and are reported as advisories.
Severity
Every finding gets a severity, so you know what to fix first
- CriticalSome people can't finish the task at all.
- HighThe task is hard, or needs a major workaround.
- MediumA workaround exists, but it costs time or effort.
- LowA minor problem.
- AdvisoryMeets WCAG but still causes problems. Not counted as a failure in the ACR.
Every finding
Each finding is written so someone who wasn't there can reproduce it
- The screen and the exact element
- What it was tested with
- Who it affects
- Steps to reproduce
- What happens, and what should happen
- A recommended fix, often with code
- The WCAG criteria and W3C references
What we don't do
- Sell overlays, plugins or software
- Deliver reports from automated scans alone
- "Certify" products; there is no official VPAT certification
- Guarantee legal compliance
Testing is led by a Department of Homeland Security Section 508 Trusted Tester.
Want this level of detail for your product?
Tell us what you need tested. You get a fixed quote within two business days.