About Accessibility Auditor

Check HTML for common accessibility issues (ARIA, alt text, headings). Part of the DevTools Surf developer suite. Browse more tools in the Web / Frontend collection.

Use Cases

• Frontend developers auditing components before pull requests
• QA teams running accessibility checks as part of test suites
• Designers validating that HTML matches accessible design specs
• Compliance officers verifying WCAG conformance for legal requirements

Tips

• Check all images for meaningful alt text descriptions
• Verify heading levels follow a logical h1-h6 hierarchy
• Ensure ARIA roles match their interactive element behavior

Fun Facts

• The Web Content Accessibility Guidelines (WCAG) 1.0 were published by the W3C in 1999 — WCAG 2.0 followed in 2008, and WCAG 2.2 was released in October 2023.
• An estimated 1.3 billion people worldwide experience significant disability — the WebAIM Million study found that 96.3% of home pages had detectable WCAG 2 failures in 2023.
• Section 508 of the US Rehabilitation Act was amended in 2017 to adopt WCAG 2.0 AA as the federal standard, making accessibility a legal requirement for government websites.

FAQ

What does it check?

Common accessibility issues: missing alt text, heading order (skipped levels), ARIA misuse, form label associations, color contrast, keyboard-only focus.

Is this a complete audit?

No — automated tools catch 30-40% of accessibility issues. The other 60% needs manual review (screen reader testing, keyboard-only navigation, cognitive load).

What about WCAG levels?

Output references WCAG 2.2 success criteria. Each issue links to the specific criterion (1.1.1 for alt text, 2.4.6 for headings, etc.).

Does it check against live sites?

Paste HTML — the tool analyzes static markup. For live-site auditing use axe DevTools, Lighthouse, or WAVE browser extensions.