Web accessibility scanner
- Tests one page against .
- Runs the and engines.
- Adds for defects those engines miss.
- Marks each finding on a screenshot of the page.
- Gives each fix, plus the guard: what it can break.
Our checks
Checks we wrote for defects a rules engine cannot see, because nothing on the page is broken: the needed markup or behavior is missing. Examples: a dialog that opens without moving keyboard focus into it, a page behind a dialog that the keyboard can still reach, an age gate that is not marked as a dialog, and a layer that only a mouse can close.
WCAG 2.2 A and AA
The Web Content Accessibility Guidelines, version 2.2, published by the W3C (World Wide Web Consortium). Each success criterion has a level: A, AA or AAA. The scan tests the 55 criteria at Level A and AA.
axe-core
An open-source rules engine from Deque Systems that tests a page for accessibility failures. Google Lighthouse runs it for its accessibility score.
IBM Equal Access
IBM's open-source accessibility rules engine. It reports some failures axe does not, and axe reports some it does not, so the scan runs both.
General notes
| No. | Note |
|---|---|
| 1 | Before checking the page, the scan answers age gates (screens that ask visitors to confirm their age before they can use the site) and closes cookie banners and popups. If one of these overlays still covers the page afterward, the report says so and gives no score. |
| 2 | The scan opens every <details> element (a section that expands when clicked) before the checks run, so it also tests the content inside them. |
| 3 | Automated checks find some of the WCAG failures on a page. In a study by Deque, the company that makes axe-core, axe found 57% of the issues its auditors logged, counted by volume. The Checks page lists the tests a person does by hand, including screen reader, voice control and task tests. |
| 4 | The report is a list of findings. It is not a certificate of compliance with the ADA (Americans with Disabilities Act), WCAG or any other law or standard. |
Questions and answers
Answers about how the scan works, what the results mean, how accurate the scanner is, screen readers, and what the law says about websites that are not accessible. The numbers come from the running scanner and its published benchmark, a test on W3C example pages. The legal answers link their sources and are not legal advice. The glossary explains every term.
No question matches this search.
Scan in progress
Multi-page scan
| No. | Page | Status | Score | Failures | Report |
|---|
Failures across the scanned pages
A failure found on every page usually comes from a part the pages share, such as the header, the footer or a page template. One fix there repairs every page.
| Failure | WCAG criterion | Pages | Instances |
|---|
Pages are scanned one after another. You can open a report while its page is still being scanned; findings appear as they are found. The results stay on the server for 1 hour.