Headings
Topic | Technique | WCAG AA Requirement |
---|---|---|
Headings to Bypass Blocks of Content | Bypass blocks: Screen readers allow users to navigate by headings, so headings are an effective way to bypass blocks of content, as required by WCAG 2.4.1. Note: Headings are not absolutely required by WCAG to pass 2.4.1, but are highly recommended, along with landmarks and skip links. |
Required WCAG 2.4.1 |
Meaningful Text | Accurate, informative section labels: Headings MUST be accurate and informative, as labels for the sections of text they describe. | Required WCAG 1.3.1 WCAG 2.4.6 |
Brevity: Heading text SHOULD be concise and relatively brief. | best practice | |
Heading Markup | Use real headings: Text that acts as a heading visually or structurally SHOULD be designated as a true heading (<h1> , <h2> , etc.) in the markup. |
best practice |
Heading Markup for Headings Only: Text that does not act as a heading visually or structurally SHOULD NOT be marked as a heading. |
best practice | |
Outline/Hierarchy of Content | Content outline: Headings SHOULD convey a clear and accurate structural outline of the sections of content of a web page. |
best practice |
Consecutive levels: Headings SHOULD NOT skip hierarchical levels. | best practice | |
First heading in the main content: The beginning of the main content SHOULD start with <h1> . |
best practice | |
One <h1> : Most web pages SHOULD have only one <h1> . |
best practice |