Accessibility Techniques for 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.

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 MUST be designated as a true heading (<h1>, <h2>, etc.) in the markup. Required
WCAG 1.3.1
Heading Markup for Headings Only: Text that does not act as a heading visually or structurally MUST NOT be marked as a heading.

WCAG 1.3.1
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