- Level
- AA
- Since
- WCAG 2.0
2.4.6 Headings and Labels
The headings and labels a page has must say what the section is about or what the control is for.
/ What it requires
Headings and labels are the signposts of a page. This criterion asks that, where they exist, they describe the topic of the section they introduce or the purpose of the component they identify. A heading that reads "More" or a field labelled "Value" points nowhere. Clear signposts help everyone who skims, and they matter most to people who read slowly, people with limited short-term memory, and screen reader users who pull up a list of headings or jump from one to the next, hearing each heading without the text around it.
The criterion does not require headings or labels. Whether a form has labels at all is 3.3.2, whether headings and labels are marked up and tied to their elements is 1.3.1, and the accessible name of a control is 4.1.2. This one asks only that the headings and labels present are clear and accurate. They can be short: W3C says a word, or even a single character, can be enough if it gives the right cue, and an icon can act as a label when its use in that context is widely understood, such as a magnifying glass beside a search field. A page can be marked up perfectly and still fail here because its headings say nothing.
/ How pages fail it
- Every section of a services page has the heading "Learn more" or "Overview", so a list of headings reads as the same two phrases over and over.
- A checkout has two fields labelled "Address", one for billing and one for delivery, and nothing in either label says which is which.
- A placeholder heading from a template, such as "Section title", went live above real content.
- The buttons in each row of a table read "Go" and "Submit", with no word for what they do to the row.
- After a redesign the heading "Pricing" sits above a block of customer quotes, while the prices moved to another section.
/ How to check it yourself
- Open the outline of headings with a free browser extension such as HeadingsMap, or the list of headings in a screen reader (in NVDA, Insert+F7). Read the headings alone and check that each one tells you what its section holds.
- Compare each heading with the content below it. A heading left over from a template or an earlier layout fails even when it is well written.
- Read every visible form label on its own and ask whether it says what to enter. Look hardest at pairs that could be confused, such as two address fields or two date fields.
- Check buttons and icon controls. Their visible text or symbol should say what will happen, and an icon used as the only label should be one people widely recognise in that place.
- Where the same heading repeats on a page, such as "Specifications" under several products, check that the surrounding structure makes each one distinct.
/ How to fix it
- Rewrite each heading to name its topic and put the distinguishing word first: "Flood preparation" and "Fire preparation" rather than "Preparation for floods" and "Preparation for fires".
- Make each label say exactly what goes in the field: "Billing address" and "Delivery address", "Date of birth" rather than "Date".
- Name buttons after what they do, such as "Delete invoice" or "Download report", rather than "Go" or "Submit".
- Give an icon-only control a text alternative that states its purpose, such as aria-label="Search" on the button with the magnifying glass, and keep icon-only labels for symbols people widely understand.
- Review headings each time content is moved or a template is reused, and search the build for placeholder text such as "Lorem ipsum" or "Section title" before publishing.
/ What our scanner checks
No automated check in our scan decides this criterion, because whether a heading describes its section is a matter of reading. Related faults are filed elsewhere: a skipped heading level and a missing h1 under 1.3.1, a field with no label under 1.3.1, a control with no accessible name under 4.1.2. The HTML_CodeSniffer sniff for 2.4.6 raises only a notice, which the scan drops. A person reads the headings and labels in a manual audit.
/ Who fails it, in our own measurements
The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Does WCAG 2.4.6 require every page to have headings?
No. The criterion applies to the headings and labels that are there and asks that they describe topic or purpose. Text that looks like a heading but is not marked up as one fails 1.3.1 Info and Relationships, not 2.4.6. Using headings to organise content is required by 2.4.10 Section Headings, which is level AAA.
What is the difference between 2.4.6 and 3.3.2?
3.3.2 Labels or Instructions asks whether labels or instructions are there when content asks for input. 2.4.6 asks whether the labels and headings that are there clearly say what they identify. Fields labelled "Field 1" and "Field 2" have labels, so the form meets 3.3.2, and it fails 2.4.6 because the labels describe nothing.
How long should a heading or label be?
As short as it can be while still describing. W3C notes that a word, or even a single character, can be enough if it gives the right cue. Put the distinguishing word first, so that people scanning a list of headings find it quickly, and leave the detail to the content below.
