Accessibility Testing & Process

What you'll learn

• What automated tools catch — and the ~70% they cannot
• A repeatable 15-minute keyboard-only audit you can run on any page
• How to drive VoiceOver and NVDA well enough to find real bugs
• Where to put a11y assertions: unit, component, and end-to-end
• How to triage findings with an impact × frequency × difficulty matrix
• Team rituals — checklists, code review prompts, and definition-of-done
• How to fail a CI build on the right things without drowning the team in noise

1. 01
   Automated checks: axe-core, Lighthouse, WAVE

   What each tool catches, what each misses, and why automation only finds about a third of issues.
   14 min
2. 02
   Manual checks: the keyboard-only audit

   A structured 15-minute walkthrough you can run on any page, even the ones that aren’t yours.
   13 min
3. 03
   Manual checks: the screen-reader audit

   Driving VoiceOver and NVDA, plus the specific patterns to listen for.
   17 min
4. 04
   Color and contrast tools

   DevTools contrast picker, browser extensions, and how to negotiate brand-color compromises.
   11 min
5. 05
   Component-level testing

   Testing Library queries by role, jest-axe, and the right level to catch a11y bugs cheaply.
   15 min
6. 06
   End-to-end a11y testing

   Playwright + axe scanning real pages in CI — and what to actually fail the build on.
   14 min
7. 07
   Running an audit on an existing app

   A priority matrix, a reporting template, and how to sequence fixes when the backlog is huge.
   16 min
8. 08
   Putting a11y in the pipeline

   Design checklists, code-review prompts, definition-of-done, and team rituals that actually stick.
   15 min