How accessible is your website?Start free check
WCAG 2.4.6Level AAOperable

Headings and Labels: Describe Topic or Purpose

Also called: Descriptive headings, Descriptive labels, WCAG 2.4.6

Definition

Headings and Labels is WCAG success criterion 2.4.6 (Level AA). Headings and labels describe topic or purpose, so people can tell what a section contains or what a field expects.

Headings and labels are the signposts of a page: a heading tells people what the next section is about, a label tells them what to type into a field. WCAG 2.4.6 asks that both are descriptive. "Section 2" or a field labeled "Info" technically exists, but nobody can tell from it what to expect.

What it means

WCAG 2.4.6 Headings and Labels is a Level AA criterion with one short sentence: headings and labels describe topic or purpose. It does not require you to add headings or labels – if they are there, they have to be clear. Short is fine: W3C notes that a word, or even a single character, may suffice if it is an appropriate cue.

Descriptive headings let people predict what a section contains. That helps people who read slowly, people with limited short-term memory, and screen reader users who jump from heading to heading or pull up a list of all headings. Descriptive labels tell people filling in a form what input is expected.

Criterion What it checks
1.3.1 Info and Relationships Headings and labels are marked up so software can read them
2.4.6 Headings and Labels Their words describe the topic or purpose
3.3.2 Labels or Instructions Fields that need input have a label or instructions at all
4.1.2 Name, Role, Value Controls have an accessible name

Examples

Example
<!-- Unclear: the heading and labels say nothing -->
<h2>Section 2</h2>
<label for="f1">Info</label>
<input id="f1" type="text">

<!-- Descriptive: topic and purpose are clear -->
<h2>Delivery times and shipping costs</h2>
<label for="first-name">First name</label>
<input id="first-name" type="text" autocomplete="given-name">
<label for="last-name">Last name</label>
<input id="last-name" type="text" autocomplete="family-name">

<!-- Icon button: the label describes the purpose -->
<button type="submit" aria-label="Search">
  <svg aria-hidden="true" focusable="false">…</svg>
</button>

The search icon is a W3C example: a magnifying glass with the label "search" describes its purpose. For more on naming controls see accessible name and form labels.

Do

Write headings that name the topic ("Opening hours in Vienna"), keep them unique on the page, put the key word first, and label fields with what to enter ("Email address", "Date of birth").

Don't

Use vague headings like "Welcome", "More" or "Section 1", repeat the same heading for different sections, or label fields with "Field 1", "Text" or only a placeholder.

How to check headings and labels

    Questions

    Does WCAG 2.4.6 require every page to have headings?

    No. W3C states that the criterion does not require headings or labels. It only applies when headings or labels are present: then they must describe topic or purpose. Other criteria, such as 1.3.1, cover marking up content that looks like a heading.

    How long should a heading be?

    As long as needed to be clear, and usually short. W3C notes that a single word, or even a single character, can be enough if it gives an appropriate cue – for example "Prices" above a price table.

    Is a placeholder a descriptive label?

    A placeholder disappears as soon as someone types, so it is a weak label. Use a visible label element; a placeholder can add an example of the format.

    What is the difference between 2.4.6 and 3.3.2?

    3.3.2 Labels or Instructions (Level A) asks that input fields have a label or instructions at all. 2.4.6 Headings and Labels (Level AA) asks that those labels, and all headings, are descriptive.

    • Heading Structure: Build a Clear Page Outline

      Heading structure is the outline a page forms through its h1 to h6 elements. Each heading marks the start of a section, and its level shows where that section sits in the hierarchy.

      Read definition: Heading Structure: Build a Clear Page Outline
    • Form Labels: Clear Labels and Instructions

      Form labels are the visible texts that name what a form field expects, such as “Email address”. WCAG 3.3.2 requires labels or instructions wherever content asks for user input, including formats and required fields.

      Read definition: Form Labels: Clear Labels and Instructions
    • Accessible Name: What It Is and How It Is Computed

      The accessible name is the text that browsers pass to assistive technology to identify an element – for example the words a screen reader announces for a button, link or form field. WCAG 4.1.2 requires a programmatically determinable name for every user interface component.

      Read definition: Accessible Name: What It Is and How It Is Computed
    • Info and Relationships: Structure in the Code

      Info and Relationships is WCAG success criterion 1.3.1: information, structure and relationships conveyed through presentation can be programmatically determined or are available in text.

      Read definition: Info and Relationships: Structure in the Code

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done