Free heading structure checker for any web page
A page's URL in, its heading outline and landmarks out, with what is wrong in them.
Check a page's headings and landmarks
Example A made-up clinic's treatments page. Enter yours to check it.
3 things to review
6 headings, 5 landmarks and a skip link.
Heading outline
-
H1 Our treatments
-
H2 Check-ups and cleaning
-
H4 What to bring Skips a level
-
-
H2 No text
-
H3 Prices
-
-
H2 Opening hours
-
Landmarks
- Banner
- Navigation “Main”
- Main
- Complementary “Opening hours”
- Content info
Skip link “Skip to content” Target missing
| Problem | Element |
|---|---|
| Skip link target does not exist Skip link points to "#content" but no element with that id or name exists on the page, so it goes nowhere. | <a class="skip-link" href="#content"> |
| Heading level skipped h4 follows h2, skipping h3. Heading levels should not skip. | <h4>What to bring</h4> |
| Empty heading found h2 element has no text content. | <h2></h2> |
What this check looks for
The tool above checks for these things on the page you give it.
- Skipped heading levels
- Jumps such as h2 straight to h4 that break the outline screen reader users navigate by.
- Empty or missing headings
- Heading tags with no text, and pages with no h1.
- Missing or ambiguous main landmark
- Pages without a main region, or with two main regions and no names to tell them apart.
- No way to skip navigation
- A skip link that points at nothing, or navigation with no skip link, main landmark or heading to jump to.
The fix, in HTML
Content is wrapped in plain divs and the page title is styled text, so screen reader users can't jump to the content or scan the page.
<!-- Broken: no landmarks, heading is just bold text -->
<div class="content">
<div class="title">Our treatments</div>
</div>
<!-- Fixed: a main landmark and a real heading -->
<a class="skip-link" href="#main">Skip to content</a>
<main id="main">
<h1>Our treatments</h1>
</main>
WCAG criteria
Findings from this check name one of these criteria. How much of each the audit can decide on its own:
| Criterion | Level | Automation |
|---|---|---|
| 1.3.1 Info and Relationships Headings, lists, tables, labels and landmarks in the markup are checked. Structure shown only visually needs a person. | A | Partly automated |
| 2.4.1 Bypass Blocks | A | Partly automated |
| 2.4.6 Headings and Labels | AA | Partly automated |
What still needs a person
No automated tool can confirm these. AccessGuard marks related findings as Review, so nobody mistakes them for a pass.
- Whether heading text describes the section it introduces (WCAG 2.4.6). Automated checks find a broken outline; only a person can judge the words.
- Text that looks like a heading but isn't marked up as one.
- Whether landmarks are labelled well when a page has several of the same kind.
Questions
Is it a failure to skip heading levels?
Skipping a level is a common sign that the structure doesn't match the visual design, and it confuses people who navigate by headings. AccessGuard reports it so you can decide whether the outline needs fixing.
Does every page need one h1?
WCAG doesn't require exactly one, but a single h1 that names the page is the clearest pattern for screen reader users and search engines.
Do I need a skip link if I use landmarks?
Landmarks help screen reader users, but keyboard users without a screen reader can't jump to them. A visible skip link helps both groups.
Related checks and guides
-
Checks
ARIA checkerA page's URL in, every ARIA problem out, with the element and what is wrong with it.
-
Link text checker
Finds links with no accessible name, vague text like "click here", and links that open new windows without warning.
-
Keyboard and focus checker
Finds controls people can't reach by keyboard, controls a keyboard reaches but nobody can see, focus styles that were removed, and focused elements hidden behind sticky headers.
-
Guides
What Is WCAG? A Plain-English Guide to 2.0, 2.1 and 2.2WCAG can feel overwhelming. This guide breaks the Web Content Accessibility Guidelines into plain English: conformance levels A, AA and AAA, the four core principles, and what you actually need to meet.
-
Accessibility Audit Checklist: Step-by-Step WCAG 2.2 Guide
A complete guide to finding accessibility issues on your website, from free automated scanning tools to manual keyboard and screen reader testing. Covers WCAG 2.1 and 2.2.
-
Agent Ready Website: What AI Browser Agents Need to Read
Browser agents read the same names, roles and labels as screen readers, so the WCAG fixes that help people also stop agents getting stuck.
-
Heading Structure Accessibility: Fix H1s, Skips and Landmarks
What a missing h1 or a skipped heading level really costs, which findings WCAG requires you to fix, and the markup that fixes them.
-
How to Test With a Screen Reader: A 20 Minute Website Pass
The smallest screen reader routine that finds real bugs: one reader, a handful of keys and a pass of about 20 minutes per page template.
-
Accessible Forms: WCAG Inputs, Labels, and Errors
Missing labels, broken error handling, and inaccessible inputs block real users from completing forms. Learn how to fix common WCAG form violations with practical code examples.
-
Keyboard Navigation Accessibility: A Complete WCAG Guide
Many people navigate the web without a mouse. Learn how to build keyboard-accessible websites with proper focus management, tab order, skip links, and visible focus indicators.
Every check, not only headings and landmarks
The free audit runs this check and every other one. Results in about a minute.