How the scan works
Enter a URL and we load it in a real headless Chromium browser, then run axe-core — the open-source accessibility engine used inside many professional tools — against WCAG 2.1 Level A and AA rules. You get an automated readiness score, a breakdown by severity, and the specific elements that triggered each issue.
What the score means (and doesn't)
The score is a quick read on machine-detectable issues, weighted by severity. A high score means the obvious, automatable problems are mostly handled — it does not mean your site is ADA compliant. We're deliberate about this because the gap is where lawsuits live: automated tools catch roughly 30–40% of WCAG issues. The rest — keyboard operability, meaningful alt text, focus management, screen-reader logic — require a human.
That's the honest pitch behind every tool here. Use the scan to fix the easy 40% yourself, then bring in a manual audit for the part that actually determines whether your site holds up. If you've already had an overlay widget installed, this scan will often show you it didn't fix the underlying code.
Common issues this scan surfaces
- Color contrast — verify and fix in the contrast checker.
- Missing alt text — audit images in the alt text checker.
- Unlabeled form fields — see the accessible forms guide.
- Missing document language, page titles, and landmarks — structural basics that scanners reliably catch.
- ARIA misuse — the most misused tool in accessibility.