Comparison
How to choose an accessibility compliance tool (EAA / WCAG)
The criteria that really matter when choosing a compliance tool, and the traps to avoid (including the false 100/100).
Not all accessibility tools are equal. For a compliance goal (EAA, WCAG 2.2 AA, EN 301 549), certain criteria make the difference between real compliance and false reassurance.
The criteria that matter
- Source-level fixes rather than an overlay: the tool must point to the real problem in the code, not hide it.
- A recognised engine: axe-core is the industry standard, aligned with WCAG and the EN 301 549 norm.
- A multi-page audit, not just the homepage: compliance is assessed across the whole site.
- Plain-language explanations: an unreadable report does not get fixed.
- Generation of an accessibility statement, required by the legal framework.
- Continuous monitoring: every update can introduce a regression.
- Data hosted in Europe: consistency with the GDPR.
Require it, avoid it
| Aspect | Require | Avoid |
|---|---|---|
| Method | Source-level fixes | Overlay that hides |
| Scope | Whole site | Homepage only |
| Score | Per page, weakest page | Average that hides a non-compliant page |
| Deliverable | Generated statement | No usable document |
| Follow-up | Regression monitoring | One-off audit, no follow-up |
| Data | EU hosting | Uncontrolled transfer outside the EU |
The false 100/100 trap
A tool that shows a site score by averaging pages can display 100 while a page stays non-compliant. Yet a site is only compliant if all its pages are. Require a score that reflects the weakest page and a clear status per page: a false 100 is dangerous.
Automated does not mean complete
An automated engine quickly detects a significant share of measurable problems, but not everything. Criteria requiring human judgement still need a manual check. A good tool says so clearly rather than promising full automatic compliance.
Sources
- W3C Web Accessibility Initiative, WCAG 2.2 (w3.org/WAI).
- EN 301 549, European standard for accessibility of ICT products and services.
- WebAIM, web accessibility analyses (webaim.org).
Frequently asked questions
Is a single tool enough to be compliant?
A tool covers the baseline, guided fixes, the statement and monitoring. For non-automatable criteria, a human check is still needed.
Why does the scan engine matter?
The engine determines result reliability. axe-core is widely recognised and aligned with WCAG, which reduces false positives.
Related definitions
Read next
Start with a free scan
Get your accessibility score, your priority issues and the missing statement in seconds.
Scan my site