WCAG & ADA Compliance Checker
Test any URL against the 20 WCAG 2.1 criteria a machine can read, see which 30 it cannot, and get a manual test plan for the forms, menus and media on your page.
Note: This tool analyses server-rendered HTML. Content loaded via JavaScript (React hydration, SPAs) may not be included. For full JS-rendered audits, use browser tools like Lighthouse or axe DevTools.
20 Success Criteria Checked
| SC | Name | Level | Principle |
|---|---|---|---|
| 1.1.1 | Non-text Content | A | Perceivable |
| 1.3.1 | Info and Relationships | A | Perceivable |
| 1.3.4 | Orientation | AA | Perceivable |
| 1.4.3 | Contrast (Minimum) | AA | Perceivable |
| 1.4.4 | Resize Text | AA | Perceivable |
| 1.4.11 | Non-text Contrast | AA | Perceivable |
| 2.1.1 | Keyboard | A | Operable |
| 2.4.2 | Page Titled | A | Operable |
| 2.4.3 | Focus Order | A | Operable |
| 2.4.4 | Link Purpose (In Context) | A | Operable |
| 2.4.5 | Multiple Ways | AA | Operable |
| 2.4.6 | Headings and Labels | AA | Operable |
| 2.4.7 | Focus Visible | AA | Operable |
| 3.1.1 | Language of Page | A | Understandable |
| 3.1.2 | Language of Parts | AA | Understandable |
| 3.3.1 | Error Identification | A | Understandable |
| 3.3.2 | Labels or Instructions | A | Understandable |
| 4.1.1 | Parsing | A | Robust |
| 4.1.2 | Name, Role, Value | A | Robust |
| 4.1.3 | Status Messages | AA | Robust |
Frequently Asked Questions
Common questions about WCAG and ADA compliance checking, success criteria, and how the per-criterion audit works.
It evaluates your page against 20 of the 50 WCAG 2.1 A and AA success criteria, the standard courts use to assess ADA website compliance. The report lists the other 30 criteria, which need a person to test. Results are grouped across the four POUR principles: Perceivable (6 criteria), Operable (7 criteria), Understandable (4 criteria), and Robust (3 criteria). Each criterion gets a pass, fail, or not-applicable status.
The Accessibility Checker groups results into 13 categories with a weighted 0–100 score, scans up to 5 pages, and builds a manual test plan. This tool reports per individual WCAG success criterion (e.g. 1.1.1, 2.4.4) with pass/fail/NA status, grouped by POUR principles — closer to how auditors evaluate compliance.
Yes, completely free with no sign-up required. The analysis runs in your browser after we fetch the page HTML through our server (to avoid CORS restrictions).
No. This tool analyses the server-rendered HTML. Content loaded dynamically via JavaScript (React hydration, SPAs) won't be included. For full JS rendering, use browser-based tools like Lighthouse or axe DevTools.
WCAG defines three conformance levels. Level A is the minimum — every site should meet it. Level AA is the standard most organisations target and is often legally required. Level AAA is the highest standard, recommended where feasible but not typically required.
The HTML is fetched temporarily to deliver it to your browser and is never stored. All analysis runs locally in your browser. We do not log URLs or results.
Yes, the fetch endpoint allows 10 requests per minute per IP to prevent abuse. For normal usage you will not hit this limit.
Why check WCAG compliance per criterion for ADA?
A single accessibility score can obscure which specific WCAG requirements your site meets and which it misses. Per-criterion reporting gives you the same view an ADA compliance auditor uses. You can see exactly which success criteria pass and which need work, making it easier to prioritize fixes and document your compliance efforts.
The four POUR principles (Perceivable, Operable, Understandable, Robust) organize criteria by the type of barrier they address. This makes it easier to prioritize: a page missing a lang attribute is a different kind of issue than a page with low color contrast ratios. Both matter for WCAG and ADA compliance, but they require different fixes.
This WCAG compliance checker covers 20 criteria that can be evaluated from server-rendered HTML. For a full ADA compliance audit, combine it with our website accessibility checker, manual keyboard testing, screen reader testing, and browser-based tools like axe DevTools.
Ship WCAG-compliant UIs faster
Our starter kits are built to WCAG 2.1 AA from the first commit. Contrast-checked, keyboard-tested, screen-reader verified.
Browse Starter Kits