Recommended accessibility testing tools
Automated tools detect only part of the defects (often estimated at 30 to 40%). Combine them with manual keyboard and screen-reader testing and with real users.
Automated auditing
| Tool | Use | Notes |
|---|---|---|
| axe DevTools (Deque) | Browser extension, editor and CI integrations | Widely used axe-core engine; free and paid versions |
| WAVE (WebAIM) | Visual analysis of errors in the page | Free extension |
| Lighthouse | Performance, accessibility, SEO audit | Built into Chrome DevTools |
| pa11y | Command-line and CI/CD testing | Open source |
| Accessibility Insights | Guided semi-manual assessments | Free (Microsoft) |
Manual testing and assistive technologies
- Contrast: WebAIM Contrast Checker, Colour Contrast Analyser.
- Screen readers: NVDA (Windows, free), VoiceOver (macOS, iOS), TalkBack (Android), JAWS.
- Structure: HeadingsMap and Web Developer extensions to check headings, landmarks and order.
- Keyboard: no tool needed: unplug the mouse.
Recommended method
- Scan each template with axe or WAVE.
- Check by keyboard alone, then with a screen reader.
- Check contrast, 200% zoom and reflow.
- Add the six WCAG 2.2 criteria, almost all manual.
- Have real users test.
Frequently asked questions
Does a Lighthouse score of 100 mean an accessible site?
No. Lighthouse runs only a subset of automatable rules; a perfect score is not RGAA or WCAG compliance.
Which screen reader should I start with?
NVDA on Windows (free) or VoiceOver on Mac and iPhone, already built in.