Free VPAT readiness check
Enter up to three public pages of your product. We load each one in a real browser, run axe-core (a widely used open-source accessibility checker), and lay the results out against the 56 WCAG 2.x Level A and AA rows of the VPAT® 2.5 WCAG edition. Free, no email needed, results on this page.
Read this first: a scan is not a VPAT
Automated checks find only part of the accessibility problems on a page. When the UK Government Digital Service built a page with 143 known barriers, the best single tool's errors and warnings caught 37% of them (41% counting its prompts to check by hand), and 29% were missed by every tool they tried (GDS, 2017). Deque, which makes axe-core, found that its automated tests covered 57% of the issues by count in over 2,000 of its own audits (Deque, 2021). Many WCAG criteria have no automated test at all.
So "no automated problems found" does not mean a row is met, and this result is not a report procurement will accept. In our paid report a person tests the product by keyboard and with a screen reader and reviews every row.
Your results
This is a scan, not an Accessibility Conformance Report.
Automated checks catch only part of the problems (see the sources above), so "no automated problems found" does not mean a row is met. Procurement teams won't accept a scan as an ACR. In the full report a person tests every row by keyboard and with a screen reader.
Pages checked
Key
- Problems found The scan found failures for this criterion. Counts are failing elements, across all pages checked.
- No automated problems found The automated checks for this criterion found nothing. They cover only part of what it asks, so a person still has to check it.
- Needs a person to check This check runs no automated test for this criterion. For most of these, no automated test can decide it.
| Criteria | Scan result | What the scan found |
|---|
What the check does
- Loads each page in a headless Chrome browser on Cloudflare, at desktop size (1280 pixels wide), and waits for it to finish loading (up to 20 seconds).
- Runs axe-core's WCAG 2.0, 2.1 and 2.2 Level A and AA rules on the page. Content inside frames isn't checked.
- Sorts every result into the VPAT row for the WCAG success criterion the rule tests. One rule can count toward more than one row.
It checks the pages as they looked at that moment, to a visitor who isn't signed in. If a page shows a cookie banner, a login wall or a bot check, that is what gets checked.
What it can't tell you
Whether your product can be used with a keyboard alone, whether a screen reader announces things in a way that makes sense, whether error messages help, whether videos have accurate captions, and most of the other criteria. Those need a person. That is also why a scan can't be turned into honest VPAT answers ("Supports", "Partially Supports" and so on), and why we don't show any.
If you want to fill in the VPAT yourself, start from our VPAT template guide and free blank form. If you want it done, see how our VPAT audit works: 1,490 USD for the WCAG edition, delivered in 5 business days.
What we keep
Nothing about the pages you check: not the addresses, the page content or the results. They are shown to you and then discarded. To stop the tool being misused we keep a one-way hashed code made from your IP address (not the address itself) and how many checks it has run that day; a cleanup job deletes these after the day ends (UTC). We also keep a daily total of checks run and pages checked, with nothing about who ran them. The spam check is Cloudflare Turnstile. More on our privacy page.
Limits
Up to three pages per check and five checks per visitor per day. The tool runs on a small daily allowance, so on a busy day it may ask you to come back tomorrow.