Skip to main content
Seu navegador é antigo demais para exibir este site corretamente. Atualize para a versão mais recente do Chrome, Edge, Firefox ou Safari.
Back to WCAG Database
Level AAWCAG 2.0

2.4.6 Headings and Labels

Headings and labels describe topic or purpose.

Last reviewed: September 9, 2026

Understanding 2.4.6

Screen reader users frequently navigate by pulling up a list of headings or a list of form fields, scanning that list to decide where to go next without reading full content. Descriptive headings and form labels let them make that decision accurately, and they also reduce cognitive load for users with cognitive or learning disabilities who use headings and labels to predict what a section or field is for before engaging with it.

How to Meet It

Write headings that describe the specific content of the section that follows, rather than generic terms that could apply to any page. Write form labels that describe exactly what input is expected, especially when a form has multiple similar fields, distinguishing e.g. 'Shipping Address' from 'Billing Address' rather than labeling both simply 'Address'.

Code Examples

INCORRECT
<h2>Info</h2>
<label for="addr1">Address</label>
<input id="addr1">
<label for="addr2">Address</label>
<input id="addr2">
CORRECT
<h2>Shipping Options</h2>
<label for="addr1">Street Address</label>
<input id="addr1">
<label for="addr2">Apartment or Suite Number</label>
<input id="addr2">

Frequently Asked Questions

Does every heading need to be unique across the whole page?

Not strictly, but headings should be unique enough within their context that a user scanning a list of headings can tell sections apart. Two identical headings like 'Overview' under different product tabs are fine if the surrounding structure (e.g. distinct parent headings) disambiguates them; two identical labels on the same visible form with no distinguishing context is a common real failure.

How is this different from 1.3.1 Info and Relationships, which also covers headings?

1.3.1 is about whether headings and labels are marked up with correct semantics at all (e.g. using an <h2> element or a <label> rather than styled plain text). 2.4.6 assumes the markup is correct and instead judges the quality of the wording: whether the heading or label text actually describes the topic or purpose.

Related Success Criteria

2.4.1 Bypass Blocks2.4.2 Page Titled2.4.3 Focus Order2.4.4 Link Purpose (In Context)

Quick Facts

  • Criterion2.4.6
  • LevelAA
  • IntroducedWCAG 2.0

Automate Compliance

AccessiSight automatically scans and identifies 2.4.6 issues in your codebase.

Try Scanner Free