What it means
The page's headings skip a level going down, such as an <h1> followed directly by an <h3>, or the page has no headings at all. The examples show where a level was skipped, and the result lists the whole outline.
Why it matters
Screen reader users move through a page by its headings, the way sighted readers skim. Skipped levels make the structure confusing, and a page with no headings can only be read from top to bottom. WCAG 2 success criterion 1.3.1 asks that structure shown visually is also in the markup.
How to fix it
- Give the page one
<h1>for its main topic. - Use
<h2>for its sections and<h3>for parts of a section, without skipping levels on the way down. - Choose heading levels for structure, then style them with CSS to look the way you want.
- Don't use headings just to make text big or bold; use CSS for that.
Check it worked
Run the accessibility check again on the same address. The finding should be gone. Then try the page yourself with only the keyboard, and if you can, with a screen reader such as NVDA or VoiceOver: automated checks find only some problems.