Most accessibility checkers give you a score and a scary list, and then leave you to figure out what any of it means for the law you actually care about.
I wanted one that tells me which criteria fail, which law each one matters for, and what's left to check by hand, so that's what this does.
How It Works
It fetches your page, removes its scripts, embedded frames, and anything else that could run, and renders it in a sandboxed frame in your browser with the page's real styles applied. Then it runs axe-core, the open source engine behind Lighthouse and most commercial accessibility tools, on the result.
Every issue axe finds is tied to its WCAG success criterion, and every criterion is tied to the laws that require it. The criteria a machine can't judge (like whether alt text actually describes the image, or whether a video has captions) come with a plain-English way to test them, and a checkbox so you can work through all of them. Your checkmarks are saved in this browser, per page.
No automated tool can tell you a site is compliant. They catch a lot of the common problems, but some criteria need a person, and that's why the manual checklist is there.
Which Standard Each Law Uses
ADA: the law doesn't name a technical standard. The Department of Justice's 2024 rule for state and local governments adopts WCAG 2.1 AA, and that's what lawsuits and settlements involving businesses usually point to as well.
Section 508: US federal agencies and anyone selling to them. The Revised 508 Standards use WCAG 2.0 Level A and AA.
European Accessibility Act: in force across the EU since June 28, 2025 for many products and services sold to consumers. Its standard, EN 301 549, requires WCAG 2.1 AA for web content.
AODA: Ontario's accessibility law, which requires WCAG 2.0 AA without live captions and prerecorded audio description.
WCAG 2.2 AA is the current version and covers everything the others ask for, so it's the one I'd aim for.
What It Can't Check
Pages built by JavaScript. The checker doesn't run the page's own scripts, for safety, so a single-page app can look nearly empty. You can paste the rendered HTML from your browser's developer tools instead, and it will check that.
Embedded frames, like YouTube videos, maps, and chat widgets, since they're separate pages.
Anything behind a login. Pasting the HTML works for those too.
Frequently Asked Questions
Is my site ADA compliant if this finds no issues?
Not necessarily. No issues from the automated checks means none of the problems a machine can detect, which is a great start. You still need to go through the manual checks, ideally with a keyboard and a screen reader, before you can say a page meets WCAG.
What's the difference between Fails and Needs review?
Fails means axe found an element that definitely breaks the criterion. Needs review means it found something it couldn't judge on its own, like text over a background image where the contrast can't be measured, so a person has to look.
Is my page or data sent anywhere?
The page is fetched by this site's server and then checked entirely in your browser. Your browser loads the page's stylesheets and images to render it, the same as visiting it, but none of its scripts run.