How to check heading structure—and interpret the result
By Grow Wild, the team maintaining What Is ADA · Updated October 19, 2026
A heading outline is a useful starting point for reviewing a page. It shows the levels you supplied, but it cannot tell whether a heading accurately describes the content below it, whether the live page exposes the same structure, or whether the page meets WCAG.
Start with the rendered page
- Open the page and identify its actual heading elements in browser developer tools or an accessibility inspection tool. A large, bold paragraph may look like a heading without being marked up as one.
- Copy each heading’s level and text in document order. Use one line per heading, such as
h2 Our services. For HTML with attributes or nested elements, use this plain-text format. Simple HTML input is a convenience, not a full HTML parser; entities are kept as typed. - Run the check. Resolve every unrecognized line first: omitted input can make an outline look more consistent than the page really is.
- Review flagged relationships against the page. Then read the headings without the surrounding paragraphs: do they describe the sections clearly?
- After a change, inspect the rendered structure again and test relevant navigation with assistive technology. Record the page, date, browser, tool and result rather than treating the outline result as certification.
What we found in our own heading validator
During our October 19, 2026 maintenance review of this tool, we tested its earlier parser with small, synthetic inputs. Two HTML headings on one line produced only one recognized heading. A heading with mismatched opening and closing tags was accepted. Nested markup was omitted. These were limitations in our tool’s input handling, not evidence that a client’s website failed WCAG.
We changed the parser to accept only the documented line formats, require matching simple HTML tags, and identify unrecognized lines by number. Unsupported HTML now needs conversion to the plain-text outline format; it is not silently treated as a complete page scan. The examples below reproduce those cases and show the corrected behavior.
| Sample input | Earlier behavior | Current behavior |
|---|---|---|
<h1>Store</h1><h2>Products</h2> | One heading recognized; the second was missed. | Line 1 unrecognized. Put each heading on its own line. |
<h2>Products</h3> | Accepted as H2 despite mismatched tags. | Line 1 unrecognized. Correct the tags or use plain text. |
<h2><span>Products</span></h2> | No heading recognized. | Still unsupported, now identified by line number. Use h2 Products. |
Download all nine test inputs and expected results (JSON). The same examples are used in our automated regression checks. They verify parsing and observations, not screen-reader usability or WCAG conformance.
What the observations mean
- A jump from H1 to H3
- Check whether a subsection is missing its parent section. Prefer a clear nested structure where it reflects the content. Do not add an empty H2 just to remove a warning.
- A return from H3 to H2
- This can correctly close a subsection and start the next major section. Our example with Store → Products → Summer → Contact produces no level-jump observation.
- More than one H1
- Review the page’s main topic and organization. One clear page-level heading is a useful convention. The count alone is not a WCAG failure verdict.
- No observations
- The recognized levels did not trigger these two checks. An outline such as H1 “Page,” H2 “More,” H3 “Other” produces no observations, yet those labels still need a content review. Missing headings, hidden content and visual-only headings also need inspection on the actual page.
W3C’s heading tutorial explains nesting, returning to higher-level sections, and consistent headings in fixed page regions. Use that context when reviewing a flattened outline.
See the completed keyboard journey through this tool, including malformed input, correction and result focus. The completed NVDA screen-reader test adds captured speech and the route through error recovery.
How this relates to WCAG
WCAG 1.3.1, Info and Relationships (Level A) concerns whether structure and relationships conveyed through presentation can be determined programmatically or are available in text. Comparing the visual sections with the actual markup is part of that review.
WCAG 2.4.6, Headings and Labels (Level AA) concerns how well headings and labels describe their topic or purpose. A level-counting tool cannot judge that meaning for you.
This tool does not inspect a URL, rendered visibility, ARIA heading roles, accessible names, embedded documents, keyboard behavior or assistive-technology output. It makes no claim of complete WCAG or legal compliance.
Use the WCAG quick reference to find a criterion by level and topic. Continue with the selected WCAG checks or return to the accessibility tools directory. Keep observations, fixes and retest evidence together so another reviewer can reproduce the work.