Headings and Labels ensures that users can understand what a page or interface is about and how its parts are organised by reading the headings and labels provided.
When headings and labels are clear and descriptive, users can quickly determine where they are, what information a section contains, and what action a control performs. When they are vague or misleading, users must explore by trial and error, which increases confusion and effort.
WCAG Success Criterion
2.4.6 Headings and Labels (Level AA)
Headings and labels describe the topic or purpose.
Why This Matters
Many users rely on headings and labels to orient themselves and decide where to go next.
If headings or labels are unclear:
- Users may misunderstand what a section contains
- Users may skip relevant content
- Users may enter incorrect information in forms
- Navigation becomes slower and more error-prone
This is especially important for users with cognitive disabilities, low vision, or limited short-term memory, as well as users who navigate using screen readers or screen magnifiers.
Screen reader users often navigate pages by pulling up a list of headings or jumping between headings. Vague headings like “Details” or “More” provide little or no useful information in these contexts.
Who This Helps
This criterion primarily supports:
- Users with cognitive or learning disabilities
- Users with low vision who scan content visually
- Screen reader users who navigate by headings or labels
- Keyboard users who move between form fields and controls
- Users who benefit from predictable, well-structured content
What “Descriptive” Means
This criterion does not require headings or labels to be long or detailed.
A heading or label is considered descriptive if it:
- Clearly indicates the topic or purpose
- Matches what the content or control actually does
- Helps users decide whether to continue reading or interacting
Even a single word can be sufficient if it provides a clear cue in context.
Examples of descriptive vs vague text
- Descriptive: Shipping address
- Vague: Details
- Descriptive: Search
- Vague: Go
Headings
Headings describe sections of content.
Content functions as a heading when it introduces or groups content, even if it is not marked up using a heading element.
Clear headings allow users to:
- Predict what information a section contains
- Skim or scan a page efficiently
- Jump directly to relevant sections using assistive technology
This criterion does not require that headings exist. It requires that if content functions as a heading, it must accurately describe the section.
Correct semantic markup and heading hierarchy are evaluated separately under 1.3.1 Info and Relationships. A page can pass this criterion while failing 1.3.1, and vice versa.
Labels
Labels describe interactive controls.
This includes labels for:
- Form inputs
- Buttons
- Links
- Toggles and switches
- Icon-only controls
Descriptive labels help users understand:
- What information is expected
- What action will occur
- Whether the control is relevant to their task
Labels are often text, but images can also act as labels if their meaning is widely understood in context.
For example:
- A magnifying glass icon next to a search field, with a programmatic label of “Search”
- An icon-only button with a clear and accurate accessible name
Placeholder text alone is not a reliable label. Placeholder text disappears as users type and cannot be used to recheck instructions or field purpose. This criterion evaluates clarity and accuracy, not whether an accessible name exists. Accessible naming is covered separately under 4.1.2 Name, Role, Value.
Important Distinctions
This success criterion:
- Does not require headings or labels to exist
- Does require that existing headings or labels be clear and accurate
- Does not require correct semantic markup
- Does not evaluate whether labels are programmatically associated
A label may be visually clear and still fail other criteria if it is not programmatically associated with its control or exposed to assistive technologies.
Related criteria include:
- 1.3.1 Info and Relationships
- 3.3.2 Labels or Instructions
- 4.1.2 Name, Role, Value
Common Failure Patterns
Failures often occur when:
- Headings are generic or decorative
- Labels use ambiguous terms like “Info” or “Click here”
- Form fields rely only on placeholder text
- Icons are used as labels without a clear meaning
- Headings do not match the content that follows
These failures can exist even when markup is technically correct.
Examples
Passing example
- A guide uses section headings such as:
- How to Write Well
- Cut Out Unnecessary Words
- Edit for Clarity
Each heading accurately reflects the content in the section.
- A form asks for a user’s name using two fields labelled:
- First name
- Last name
Each label clearly describes the expected input.
Failing example
A section titled More Information contains pricing details, return policies, and delivery times. The heading does not describe the topic or purpose of the content.
Rule Description
When headings or labels are present, they must describe the topic or purpose of the content or control they identify. Vague, misleading, or generic headings and labels fail this criterion.
The Algorithm
- Identify headings and labels on the page
- Determine what content or controls they describe
- Ask whether the text clearly communicates its purpose
- If users must guess or explore to understand:
- The criterion fails
- If the purpose is clear from the text alone:
- The criterion passes
How to Test This
- Scan the page visually using only headings
- Navigate headings using a screen reader
- Tab through form fields and interactive controls
- Read labels without interacting further
- Ask whether each heading or label accurately sets expectations
Wrapping Up
Headings and Labels (Level AA) are about clarity, not quantity. Users should not have to explore content or controls to understand what they are for. When headings and labels clearly describe the topic and purpose, users can orient themselves quickly, avoid unnecessary errors or guesswork, and move through content efficiently.
Clear wording makes content easier to scan, understand, and operate across different navigation methods.
