Free tool · WCAG 1.3.1 / 2.4.6

Does your heading outline make sense read aloud?

Screen-reader users navigate by headings, like a table of contents read aloud. Enter your page headings in order — level and text — and this checker runs 8 plain-English checks, then builds a corrected outline that fixes skipped levels without changing your words or your order.

Runs entirely in your browser. The headings you enter are never uploaded, stored or tracked. This checker reviews the outline you paste — it cannot crawl your site or judge whether a heading matches the section under it.

Try an example:
—

Add your headings in page order and the score updates as you type. 90–100 is a clean outline, 60–89 needs a fix listed below, under 60 means the outline is working against the visitor.

Corrected outline

—

Levels only are corrected: a heading that skipped a level is pulled up to the next available level, and extra H1s are demoted to H2. Your wording and order are never changed — if a heading text itself is generic or empty, fix that in the rows above.

How to read the result

The rule is simple: headings form one outline. One H1 states the page topic, H2s are its main sections, H3s sit inside an H2, and you may always jump back up — but never skip a level going down. Pick levels by structure and style the size with CSS, never the other way round. Our ADA website compliance checklist puts headings in context with the other first-line checks.

The outline mistakes that fail most often

  • Two H1s. A template H1 plus a hero H1 leaves the outline with two starting points.
  • Skipped levels. H2 straight to H4, usually because the H4 looked the right size.
  • Generic labels. “Welcome”, “Introduction” and “More” tell a listener nothing when read out of context in a headings list.
  • Bold text acting as a heading. It looks like a section title but never appears in the outline at all.

What this checker cannot do

  • It cannot crawl your site — it only sees the outline you enter here.
  • It cannot tell whether a heading honestly describes the section under it.
  • It cannot test reading order, focus order or how a screen reader announces your page.
  • A passing score is not a certification of compliance with the ADA, WCAG or Section 508.

Get every provable barrier found for you

The Full Report scans your site against WCAG 2.2 AA and returns a dated PDF: every barrier found, ranked by severity, each tied to its WCAG rule with a plain-English fix. $15 one-time. The Watch Plan ($18/month) re-checks monthly so template changes do not quietly break your outline again.

One-time payment · No recurring charges · 30-day refund policy · Full refund if the report fails to generate

Questions

Why does heading order matter for accessibility?

Screen-reader users navigate by jumping from heading to heading, the way a sighted visitor scans a table of contents. Skipped levels make the listener wonder whether a section is missing. Heading order is covered by WCAG 1.3.1 and 2.4.6.

Can a page have more than one H1?

HTML allows it, but one H1 stating the page topic is the clearest structure for a typical small-business page. Keep the page title as the H1 and demote later top-level headings to H2.

What is a skipped heading level?

Going deeper by more than one level at a time — H2 straight to H4. Moving back up any number of levels is fine. Fix a skip by renumbering the deeper heading, not by adding empty headings.

Should headings be chosen for how they look?

No. Pick the level by structure, then style it with CSS. Choosing an H4 only because it looks smaller breaks the outline even when the page looks fine.

If my outline passes here, is my website accessible?

Not necessarily. Contrast, form labels, keyboard traps and alt text can still block people. This checker reviews one outline and cannot certify compliance with the ADA, WCAG or Section 508.

Is this heading checker really free?

Yes. No account, no email form, no limit. It runs entirely in your browser: the headings you enter never leave your device.