Accessibility Checker
Audit markup against 20 WCAG rules — in your browser, nothing uploaded.
Drop an .html file here
Parsed in this tab — never uploaded
Click to browse, or paste files and links (Ctrl/⌘ + V)
Source scanning only. Rules needing document structure are markedapprox— conditionals and loops can hide the real tree.
- Errors
- 0
- Warnings
- 0
- Notices
- 0
The score weights errors above warnings. Notices report what could not be checked from this markup, so they do not reduce it.
No issues found by the rules that could run. Automated checks catch roughly a third of accessibility problems — test with a keyboard and a screen reader too.
About Accessibility Checker
Paste HTML or drop a file to audit it against 20 WCAG 2.2 rules covering images, forms, headings, ARIA, tables, media and focus order. JSX and Astro templates are scanned at source level; HTML is resolved as a real document. Everything runs in your browser — nothing is uploaded.
Does passing every rule mean my page is accessible?
No. Automated checks find roughly a third of real accessibility problems. They cannot judge whether alt text is meaningful, whether focus order makes sense, or whether an interaction works with a screen reader. Treat a clean result as a floor, not a finish line — test with a keyboard and a screen reader.
Why is contrast often only a notice?
Contrast needs the rendered page. This tool sees a snippet, so it can only compute a ratio where colours are declared inline and the background is resolvable. Anything set by a stylesheet, a CSS variable, or a partially transparent layer is reported as unchecked rather than guessed at.
What does the "approx" badge mean?
In JSX and Astro mode, rules that need document structure — heading order, duplicate ids, ARIA validity, table headers, live regions — are inferred from source order. Conditionals, .map() loops and spread props can hide the real tree, so these findings can be wrong in both directions. Findings without the badge were resolved exactly.
What does it not check?
Cross-file references, external stylesheets and computed layout, focus-trap behaviour at runtime, and what a screen reader actually announces. Single-file analysis cannot reach any of those.
Is my markup uploaded anywhere?
No. Parsing and analysis run entirely in your browser. Nothing leaves your machine, and there is no backend to send it to.
Related: WCAG Contrast Checker · Semantic HTML
Keywords: accessibility checker, WCAG audit online, ARIA validator, HTML a11y check, screen reader audit, no upload accessibility tool