Buyer’s guide
Website Accessibility Testing Tools: The Practical Stack
No single tool covers WCAG. Here’s how to assemble a real testing stack — automated, manual, and monitoring — without falling for one-click “compliance”.
There are dozens of accessibility testing tools, and the honest truth is you need more than one — because no single tool covers WCAG completely. This guide breaks the landscape into the categories that matter, what each is good (and bad) at, and how to assemble a practical testing stack without falling for the “one-click compliance” myth.
The 30–50% rule
Automated tools reliably detect roughly 30–50% of WCAG issues — the machine-checkable ones. The rest require human judgment. Any tool claiming to find or fix “100%” automatically is misleading you (and it’s what got accessiBe a $1M FTC fine).
Automated vs. manual: what each catches
| Automated catches | Only humans catch |
|---|---|
| Missing alt attributes | Whether alt text is meaningful |
| Low color contrast | Logical reading & focus order |
| Missing form labels | Whether keyboard interactions make sense |
| Empty links/buttons | Whether captions are accurate |
| Missing lang, duplicate IDs | Whether the experience actually works with a screen reader |
So a real testing process is: automated scan to clear the bulk fast, then manual testing for the rest.
Automated scanners & engines
The widely used open-source engine is axe-core, which powers many tools (and our own scanner). Google’s Lighthouse includes an accessibility audit based on axe. These are excellent for catching machine-detectable issues quickly and integrating into CI.
- Best for: fast, repeatable detection of the automatable ~30–50%.
- Watch out for: a clean score is necessary, not sufficient — it doesn’t mean compliant.
Browser extensions
Tools like axe DevTools and WAVE overlay results on the page you’re viewing, which is great for spot-checking a single page during development. Handy and free, but manual and page-by-page — not a substitute for site-wide coverage.
Point tools (contrast, alt, headings, links)
Focused tools verify one thing well. We built a free set you can use right now, no signup:
- Color Contrast Checker — exact AA/AAA ratios.
- Alt Text Checker — audit image alt in pasted HTML.
- Heading Structure Checker — outline and validate headings.
- Link Text Auditor — flag vague/empty links.
- Tap Target Size Checker — WCAG 2.5.8.
Screen readers (manual testing)
The most important manual test is using your site the way disabled users do. The major screen readers are NVDA (free, Windows), VoiceOver (built into macOS/iOS), JAWS (Windows, paid), and TalkBack (Android). Combine with keyboard-only navigation and 200% zoom for a strong manual pass.
Monitoring: the piece most teams miss
Here’s the gap almost every tool list ignores: accessibility regresses. You fix issues today, then a developer ships a new component next sprint and reintroduces them. One-off testing tools take a snapshot; they don’t tell you when something breaks again. Continuous monitoring re-scans on a schedule, alerts you to new violations, and keeps a dated audit trail — which is exactly the evidence of due diligence that matters if you’re ever challenged. That’s the category avp.io is built for.
How to choose
- Start free. Run an automated scan and use the point tools to fix the obvious issues.
- Add manual testing with a keyboard and a screen reader for the half automation can’t see.
- Add monitoring so fixes stay fixed and you have a record.
- Avoid overlays. A widget that promises instant compliance is not a testing tool — it’s a liability. Here’s why.