Heading Structure Checker
See your heading outline and where it breaks.
Paste a complete page or a fragment and run the checks automation can honestly settle: declared language, page title, image alt text, form labels, heading structure, link text, iframe titles, zoom restrictions, and more. Failures are defects automation can prove; anything that needs human judgement is labelled Review, and checks that do not apply are never counted as passes. Your HTML is parsed on your device and never rendered or uploaded.
Parsed on your device with a specification HTML parser. It is never rendered, never executed, and never uploaded — hostile markup is safe to paste.
Results will appear here. Paste HTML and run the check — or load a sample to see how it reports.
Every verdict names the WCAG 2.2 criterion it tested. “Review” means automation found something a human must judge — it is never dressed up as a pass or a fail.
The paste is parsed with a specification HTML parser (the same class of parser browsers use), so the checks run on the document a browser would build — including its error recovery for malformed markup. Document-level checks (language, title, viewport) run only when the paste is a complete page; paste a fragment and they are reported as not applicable rather than guessed at. The image, heading, label, and button checks are the same engines as the dedicated tools, so results agree wherever they overlap.
| Criterion | Name | Level |
|---|---|---|
| 3.1.1 | Language of Page | A |
| 2.4.2 | Page Titled | A |
| 1.1.1 | Non-text Content | A |
| 1.3.1 | Info and Relationships | A |
| 2.4.6 | Headings and Labels | AA |
| 4.1.2 | Name, Role, Value | A |
| 3.3.2 | Labels or Instructions | A |
| 2.4.4 | Link Purpose (In Context) | A |
| 1.4.4 | Resize Text | AA |
| 1.4.10 | Reflow | AA |
| 2.4.3 | Focus Order | A |
| 1.4.2 | Audio Control | A |
Most of accessibility, honestly: keyboard operation, visible focus, colour contrast (use the Contrast Checker), reading order as experienced, error recovery in real forms, motion and timing, and whether any text — alt, label, or heading — actually makes sense. A clean report here means the mechanical ground is clear. It is not a conformance verdict, and this tool will never call it one.
Yes. The paste is parsed into an inert data tree by a specification parser on your device. It is never inserted into this page, never rendered, and scripts or event handlers inside it cannot run — the parser stage of this site was proven against a hostile-fixture suite before these tools were built on it.
Because automation genuinely cannot settle them. An empty alt attribute is correct for a decorative image and wrong for an informative one; a table without headers is fine if it is layout and a barrier if it holds data. Dressing those up as passes or failures would be lying with confidence, so they are marked for a human.
No. These are the checks a machine can run on markup alone — a subset of a subset. Conformance needs the full criteria set, manual testing, and assistive technology. The WCAG Checklist covers the manual side.
See your heading outline and where it breaks.
Audit image alt attributes in depth.
How these automated checks fit into a complete audit.
All ten tools are listed on the homepage.