Our Methodology
Transparency is the foundation of our tool. Here is exactly how our scanner works, what it can find, and—most importantly—what it cannot find on its own.
The Scanning Engine
Our scanner is built on top of axe-core, the industry-leading open-source accessibility ruleset. We run these rules against your pages using a headless browser to detect violations of WCAG 2.1 A and AA success criteria. We do not invent proprietary 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.