axe-core Engine
Runs the industry-standard axe-core 4.9 engine against all WCAG 2.1/2.2 AA rules and best-practice checks — the same engine used by major enterprise teams.
Scan WCAG 2.1/2.2 AA violations in real-time. Get a 0–100 score, colored DOM overlays, and a full DevTools panel — all inside Chrome.
From a quick popup score to a deep-dive DevTools panel — a11y DevTools covers the full testing workflow.
Runs the industry-standard axe-core 4.9 engine against all WCAG 2.1/2.2 AA rules and best-practice checks — the same engine used by major enterprise teams.
A single actionable score with letter grade A–F, calculated from violation counts weighted by impact level. Track page improvements over time.
Colored overlays paint directly onto the live page — red for critical, orange for serious, yellow for moderate. Hover overlays show remediation tooltips.
A full split-view panel inside Chrome DevTools — violations list, detail view with remediation hints, element picker, and impact filter chips.
Navigate violations with ↑↓ arrow keys, jump to page elements with ← →, and expand detail sections — full zero-mouse workflow.
Download the complete axe-core results as structured JSON for CI pipelines, issue trackers, or formal accessibility audits.
Add a11y DevTools to Chrome from the Web Store. One click, no account needed.
Navigate to any live site or localhost. Works on any HTTP/HTTPS page.
Click the toolbar popup or open DevTools → a11y panel and hit "Run Quick Scan".
Highlighted elements, descriptions, and fix guidance. Rescan instantly to verify.
Every violation is penalized based on how severely it impacts people with disabilities. The score starts at 100 and deducts points per violating node.
| Grade | Score | Interpretation |
|---|---|---|
| A | 90 – 100 | Excellent — production ready |
| B | 75 – 89 | Good — minor fixes needed |
| C | 50 – 74 | Fair — several issues to address |
| D | 25 – 49 | Poor — significant barriers present |
| F | 0 – 24 | Critical — major remediation required |
Comprehensive rule coverage across all applicable guidelines.
Full coverage of perceivable, operable, understandable, and robust success criteria at the AA conformance level.
Includes new 2.2 criteria: focus appearance, dragging movements, target size minimum, and consistent help patterns.
Additional axe-core best-practice rules that improve UX for assistive technology users even when not strictly required by WCAG.
Zero configuration. Everything runs locally — no data is sent to any external server.
Requires Chrome 109+. Works on any HTTP/HTTPS page including localhost.