An accessibility checker that audits markup against WCAG 2.2 and tells you which success criterion each finding maps to. It checks colour contrast, image alternatives, heading structure, form labels and focus order, and separates the issues that genuinely block users from the ones that are merely untidy.
No signupRuns in your browserNothing uploaded
Accessibility CheckerLive
This tool is built for a wider screen — scroll sideways inside the frame, or turn your device.
How to use it
Four steps to a result
Paste in your markup
Drop in the HTML for a page or a component. Auditing a single component is often more useful than a whole page, because the findings stay actionable.
Run the audit
Every check runs at once and results are grouped by severity, so blocking failures sit above advisory warnings instead of being buried in a flat list.
Read the mapped criterion
Each finding names the WCAG 2.2 success criterion it violates and its level (A, AA or AAA), which is what an auditor or a VPAT will ask you for.
Fix and re-run
Apply the suggested fix, paste the updated markup and run again. Working down from the blocking issues is usually the fastest route to a clean pass.
Questions
Frequently asked questions
Automated tooling reliably catches contrast failures, missing alt attributes, unlabelled form controls, skipped heading levels, missing language attributes and duplicate IDs. These are the mechanical failures, and they are worth eliminating first because they are unambiguous.
No, and any tool that claims otherwise is overselling. Automated checks catch roughly a third of WCAG criteria. Whether alt text is meaningful, whether focus order is logical, and whether an interaction works with a screen reader all require a human. Treat a clean automated report as the floor, not the finish line.
WCAG 2.2 level AA requires 4.5:1 for normal text and 3:1 for large text (18pt, or 14pt bold) and for meaningful non-text elements such as icons and input borders. Level AAA raises normal text to 7:1. The checker reports the measured ratio, not just a pass or fail.
WCAG 2.2 added nine success criteria, notably Focus Not Obscured, Dragging Movements, Target Size (Minimum) at 24 by 24 CSS pixels, Consistent Help and Accessible Authentication. The last one matters if your login relies on solving a puzzle or transcribing a code.
No. The audit runs entirely in your browser, so you can safely check markup from an internal admin tool or an unreleased page without it leaving your machine.
Keep going
More free tools
Every one runs in your browser, with no account and nothing uploaded.