Heading Structure Checker
See your page outline with levels, skips and empty headings.
Home / Guides
Sighted readers scan a page by its headings: big text, bold text, the shape of the argument. Screen reader users do exactly the same thing — through the heading list their software builds from your markup. In WebAIM's recurring screen reader user surveys, navigating by headings is consistently the most-used way of finding information on a long page. If your headings are styled paragraphs, or your levels jump around, that table of contents is broken even when the page looks fine.
SC 1.3.1 Info and Relationships (Level A) requires that structure conveyed visually is available programmatically — a heading must be a real heading element (<h1> to <h6>), not a bold paragraph, so software can find it. SC 2.4.6 Headings and Labels (Level AA) requires that headings describe their topic or purpose. Between them they cover the whole job: be a heading, and say something true.
Heading levels describe how sections nest. A subsection of an h2 section is an h3; when that topic ends, the next main section returns to h2. Two rules follow:
h2 followed by an h4 tells a screen reader user that a section exists between them, and they will waste time looking for it.h3 looks too big, style it with CSS. Choosing h2 because it "looks right" corrupts the outline for every non-visual reader.One honest nuance: WCAG does not literally require a single h1 per page, and it does not fail a page for level order alone in every reading. The one-h1-as-page-title pattern and unbroken nesting are nonetheless the conventions assistive technology and its users are built around — follow them, and treat deviations as review items, not style choices.
A heading list read aloud, out of context, should still map the page. "Pricing and plans" works anywhere; "More information" works nowhere. Front-load the distinguishing words, because heading lists are often read as a rapid scan. And keep headings honest: a heading that promises a topic the section does not cover fails SC 2.4.6 in spirit even when a checker cannot catch it.
See your page outline with levels, skips and empty headings.
Heading findings inside a full page audit.
WCAG facts in this guide follow the official W3C WCAG 2.2 Recommendation and its Understanding documents; any other fact is attributed to its source in the text. Facts checked November 16, 2026. Direct links to the sources are in the references below.