WCAG Accessibility Checker

Scan any page for common WCAG 2.2 accessibility issues. Highlights affected elements and suggests fixes. Runs 100% locally.

WCAG Accessibility Checker Extension Check any web page against the most common WCAG 2.2 Level A and AA success criteria — directly in your browser, with one click. WHAT IT CHECKS AUTOMATICALLY - Images, SVGs and image maps without text alternatives (1.1.1) - Form controls without labels, and placeholder-only fields (1.3.1, 3.3.2) - Data tables without header cells (1.3.1) - Heading structure problems — missing h1, skipped levels (1.3.1) - Links distinguished by colour alone (1.4.1) - Insufficient text contrast, including large-text rules (1.4.3) - Viewport tags that block pinch-zoom (1.4.4) - Click handlers on divs/spans without keyboard support (2.1.1) - Missing skip links and landmarks (2.4.1) - Missing page titles (2.4.2) - Positive tabindex values that break focus order (2.4.3) - Empty and ambiguous links like "click here" (2.4.4) - aria-labels that don't contain the visible text (2.5.3) - Touch targets smaller than 24×24px — new in WCAG 2.2 (2.5.8) - Missing page language (3.1.1) - Duplicate IDs that break label and ARIA associations - Untitled iframes and focusable elements inside aria-hidden regions (4.1.2) FOR EACH ISSUE YOU GET - The exact WCAG success criterion and conformance level - A plain-language explanation and a concrete fix - References to the relevant W3C techniques - A "Show" button that scrolls to and highlights the element on the page PLUS - A guided list of manual checks that no automated tool can verify (focus visibility, consistent help, captions, and the new WCAG 2.2 criteria) - An indicative accessibility score - One-click "Copy report" for pasting into tickets, emails or audit docs PRIVACY Everything runs locally in your browser. The extension only activates when you click it, only on the tab you're viewing, and sends nothing anywhere. No accounts, no tracking, no data collection. HONEST LIMITATIONS Automated tools can only detect a subset of WCAG issues. A clean scan is a good start, not proof of compliance — the built-in manual checklist tells you what still needs human testing. For formal audits, combine this with screen-reader and keyboard testing. Useful for developers, SEO and marketing teams, content editors, QA testers, and anyone responsible for accessible websites — including European Accessibility Act (EAA) readiness work.