Full keyboard navigation
Completing every flow without a mouse, plus focus order and a visible focus ring.
Accessibility
We audit against WCAG 2.2 AA with automated scans and real screen reader sessions.
Automated tools catch roughly a third of the problems; the rest are found by hand. Full keyboard navigation, focus order, screen reader announcements, contrast and motion preferences are all tested manually.
From the checklist
33 check items
NVDA / VoiceOver sessions
With a real screen reader; automated scans catch only about a third.
Contrast and text scaling
WCAG 2.2 AA contrast ratios and clipping at 200% zoom.
Form labels and error announcements
Name, role and state for every field; errors announced through a live region.
How we run it
- An automated scan sweeps the obvious violations — that catches roughly a third of the problems.
- We attempt every critical flow end to end using the keyboard alone.
- The same flows are walked with NVDA and VoiceOver; anything not announced is a finding.
- Contrast, 200% zoom, 320-pixel reflow and motion preferences are checked by hand.
What you get
- A finding list mapped onto WCAG 2.2 AA success criteria
- Audio recordings of the screen reader sessions
- A keyboard navigation map showing where the focus order breaks
Out of scope
- We do not issue a VPAT or a formal conformance statement; we give the findings and the criterion mapping.
- Writing content and producing alternative text are out of scope.
What this typically turns up
- Form errors are never announced to screen readers
- Focus stays on the page behind when a modal opens
- The menu caret is 22 pixels, under the WCAG 2.2 target size
Questions about this service
Which standard do you work to?
WCAG 2.2 AA. On request we also report AAA criteria in a separate section.
We already run an automated tool — what is different?
Automated tools catch measurable violations. Focus order, whether announcements make sense and keyboard traps are only found by hand, and most findings come from there.
Are mobile apps covered?
Yes. The same flows are walked with VoiceOver on iOS and TalkBack on Android.
Included in
Other services
Functional testingDo the critical flows work end to endRegression testingDid the new release break the old oneCompatibility matrixReal device and browser matrixPerformance & loadLoad speed and behaviour under loadSecurity reviewApplication review on the OWASP Top 10API testingSchema, error codes and boundariesPayment testingPayments, refunds and subscriptions with real cardsUsability reviewFlows that work but wear people downLocalization testingCountry by country, with native speakers
Don't test the next release alongside your users.
Sign up in the panel, pick what you want tested, pay. The first findings start landing in the same panel within hours.