WCAG 2.4.6 Headings and Labels: How to Write Descriptive Headings

What This Criterion Requires

WCAG 2.4.6 requires that headings and labels describe the topic or purpose of the content they introduce. This does not mandate that headings and labels exist on every page, but when they are present, they must be descriptive and meaningful rather than vague or generic. Headings should clearly describe the content of the section they introduce, allowing users to scan the page structure and navigate directly to relevant sections. Form labels should clearly describe what information is expected in each input field. Generic headings like 'Section 1' or 'Information' fail this criterion because they do not help users understand or locate content. Similarly, form labels like 'Field 1' or 'Enter data' provide insufficient guidance. Well-written headings and labels reduce cognitive load for all users, improve navigation efficiency for screen reader users, and contribute to better SEO by providing search engines with clear content signals.

Why It Matters

Headings and labels serve as signposts that help users understand and navigate content. Screen reader users rely heavily on headings to build a mental model of the page structure and jump directly to sections of interest. Sighted users scan headings visually to locate content quickly. When headings are vague or generic, both groups waste time trying to determine what each section contains. For forms, unclear labels lead to input errors and user frustration. People with cognitive disabilities benefit especially from clear, descriptive headings and labels because processing abstract or ambiguous text requires more cognitive effort. Voice control users need descriptive labels because they speak the visible label to interact with form controls. Descriptive headings also directly benefit SEO, as search engines use heading content to understand page topics and rank content relevance. Writing good headings and labels costs nothing technically but requires thoughtful content strategy. This is often a content problem, not a code problem, making it essential for content authors and designers to understand the requirement.

Common Failures and How to Fix Them

<h2>Overview</h2>
<p>Our company has served over 10,000 clients since 2010...</p>

<h2>Details</h2>
<p>We offer three pricing tiers: Basic, Pro, and Enterprise...</p>

<h2>More Information</h2>
<p>Contact our sales team to schedule a demo...</p>

<h2>About Our Company</h2>
<p>Our company has served over 10,000 clients since 2010...</p>

<h2>Pricing Plans</h2>
<p>We offer three pricing tiers: Basic, Pro, and Enterprise...</p>

<h2>Schedule a Sales Demo</h2>
<p>Contact our sales team to schedule a demo...</p>

<label for="field1">Input 1:</label>
<input type="text" id="field1">

<label for="field2">Input 2:</label>
<input type="text" id="field2">

<label for="full-name">Full name (first and last):</label>
<input type="text" id="full-name" autocomplete="name">

<label for="email">Email address:</label>
<input type="email" id="email" autocomplete="email">

How to Test

1. Review all headings on the page (use the HeadingsMap browser extension or screen reader heading navigation) and verify each one clearly describes the section it introduces.
2. Check that each form label clearly communicates what information is expected, including format requirements where applicable (e.g., 'Date of birth (MM/DD/YYYY)').
3. Look for duplicate headings on the same page and ensure they are differentiated or refactored to be unique and descriptive.
4. Ask someone unfamiliar with the content to navigate by headings only and assess whether they can understand the page structure without reading the body text.

CMS-Specific Guidance

This criterion commonly causes issues on these platforms:

• Wordpress Accessibility Checklist
• Shopify Accessibility Checklist
• Squarespace Accessibility Checklist

Further Reading

• Accessible Forms Guide
• Wcag Explained Plain English
• Accessibility Seo Benefits

Related WCAG Criteria

• WCAG 1.3.1
• WCAG 2.4.4
• WCAG 3.3.2
• WCAG 2.5.3