Our Methodology
Here's how the scanner works and what it finds. And, just as important, what it can't find on its own.
The Scanning Engine
Our scanner runs on axe-core, the open-source accessibility ruleset most teams already trust. We run its rules against your pages in a headless browser to catch WCAG 2.1 A and AA violations. We don't invent our own rules. We stick to verified, community-tested checks.
The 30–57% Reality
No automated tool can detect 100% of accessibility issues. Industry research shows that automation can catch between 30% and 57% of WCAG violations. We are upfront about this limitation. Our scanner will find missing attributes, contrast failures, and structural errors, but it cannot judge context or semantics.
Manual Testing is Required
For the remaining 43-70% of issues, human verification is essential. You must manually test keyboard navigation, screen reader announcements, and the logical flow of your application. Our platform provides interactive checklists to guide you through this manual review process.
EN 301 549 Annex C Mapping
For European Accessibility Act (EAA) compliance, proving WCAG conformance is done via EN 301 549 Annex C. Our generated accessibility statements automatically map the WCAG results to the corresponding EN 301 549 clauses, fulfilling the legal documentation requirement.
Why the default is WCAG 2.1 AA
The default follows EN 301 549 v3.2.1, the current technical baseline used for EAA web work. WCAG 2.2 adds useful criteria, and the worker can receive 2.2 tags per scan job. We keep the selected version visible so results are not presented under the wrong standard.