---
title: "Headings and Labels"
url: "https://www.barrierefreihochzwei.de/en/wcag/2-4-6-headings-and-labels"
language: "en"
description: "WCAG 2.4.6 requires headings and labels to describe their topic or purpose. Learn how to write headings and form labels that genuinely help your users."
published: "2025-01-01T08:00:00+01:00"
updated: "2026-10-15T09:42:00+02:00"
---

# Headings and Labels

Orientation through clear descriptions.

- **Erfolgskriterium:** 2.4.6
- **Prinzip:** Operable
- **Konformitätsstufe:** Level AA
- **Erklärung beim W3C:** [www.w3.org/WAI/WCAG22/Understanding/head...](https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html)

Success criterion 2.4.6

# 2.4.6 Headings and Labels

Level AAOperable

Orientation through clear descriptions.

## 1. What is the goal of this criterion?

Websites are like huge libraries – and without clear signposts it’s easy to get lost in the information jungle. Headings and labels are exactly those signposts: they tell you what to expect in a section or what input a form field needs.

The goal of Success Criterion 2.4.6 is that all headings and labels clearly describe what they’re about. No cryptic “Info” headings or fields labelled “Field 1”, but specific descriptions that everyone understands immediately – with or without assistive technologies.

## 2. What exactly does it require?

Headings and labels must describe their topic or purpose – where they exist. The criterion doesn’t require you to use headings or labels everywhere, only that if you use them, they must be meaningful.

**For headings, this means:**

- They clearly describe what content the section contains.
- They don’t have to be long: a single word or even a single character can be enough if it introduces the content accurately.
- Consistency helps – similar content should be named similarly.

**For labels, this means:**

- Form fields and other controls are described clearly.
- The label reveals what input is expected or what an element does.
- This refers to labels that are presented to everyone. A name that only exists for screen readers isn’t a label in WCAG terms – but it should of course be meaningful too.

Important: this criterion doesn’t check whether headings are marked up correctly (that’s covered by [Info and Relationships](https://www.barrierefreihochzwei.de/en/wcag/1-3-1-info-and-relationships)), nor whether labels exist at all (that’s covered by [Labels or Instructions](https://www.barrierefreihochzwei.de/en/wcag/3-3-2-labels-or-instructions)). It’s about how understandable the text itself is.

## 3. Why does it matter for accessibility?

Imagine navigating a website with a screen reader and hearing, one after another: “Heading Info”, “Heading More”, “Heading Further details”. Completely useless without context, right?

Clear headings and labels improve accessibility because they:

- help **blind people and people with low vision** find their way – especially when jumping from heading to heading,
- help **people with cognitive disabilities** find relevant content faster and reduce the load on memory,
- make content easier to understand for **people with learning disabilities** through predictable, clear structures,
- save **people with limited mobility** effort, because they can go straight to the right section,
- help **everyone** fill out forms correctly and find their way around the website.

And not least: people in stressful situations or short on time also benefit from clear, understandable descriptions.

## 4. How to meet the criterion

Good headings and labels aren’t magic – but they need some attention when writing. Here are some proven tips:

**Writing good headings:**

- Be specific rather than general: “Shipping costs within the UK” instead of just “More information”.
- Use your audience’s language and explain technical terms.
- Stay consistent: if you write “Frequently asked questions” once, don’t switch to “FAQ” later.
- Short is fine – one to three words are often enough, as long as they’re accurate.
- Avoid “Info”, “More” or “Miscellaneous” without further context.

**Designing good labels:**

- Describe what should be entered: “Email address” instead of just “Email”.
- Mark required fields, for example “First name (required)”.
- Explain the format if needed: “Phone number (including area code)”.
- Place labels so they stay visible next to or above the field even when zoomed in.
- Don’t use placeholder text as a substitute for labels – it disappears as soon as you type.
- Label buttons by what they do: “Place order” instead of “OK”.

**Technical implementation:**

- Associate labels with their form fields, for example using `<label for="email">` and `id="email"`.
- Use real heading elements (`<h1>` to `<h6>`) in a logical hierarchy.
- Test your text with screen readers or have it read aloud.
- Check whether headings make sense on their own, for example in a screen reader’s list of headings.

**Tools and resources:**

- Screen readers such as NVDA or JAWS for testing
- Browser extensions that show the heading structure
- Colleagues from other departments as test readers for clarity

If you want to structure every section with a heading, the requirement for that is [Section Headings](https://www.barrierefreihochzwei.de/en/wcag/2-4-10-section-headings) (AAA).

## 5. Why this criterion matters for businesses

Clear headings and labels aren’t just mandatory – they make content and forms noticeably easier to use.

### 1. Better usability

When people immediately understand what they’ll find where and what to enter, they reach their goal faster. In forms especially, clear labels lead to fewer input errors and fewer abandoned submissions.

### 2. Clean structure helps search engines too

Accessibility isn’t a direct ranking factor. But meaningful headings make your content easier for people and machines to understand – which indirectly benefits your SEO as well.

### 3. Less support effort

People who understand what to do contact customer service less often. Clear labels and headings answer questions before they arise.

And finally: 2.4.6 is a Level AA criterion and therefore part of WCAG 2.1 AA, which the harmonised standard EN 301 549 references. Under the European Accessibility Act (EAA), many consumer services such as online shops must meet these requirements; in Germany, the EAA is implemented by the Barrierefreiheitsstärkungsgesetz (BFSG), which has applied since 28 June 2025. This is general information, not legal advice.

## 6. The success criterion in the W3C’s words

> **Success Criterion 2.4.6 Headings and Labels (Level AA)**
> 
> Headings and labels describe topic or purpose.

In short: headings and labels must describe what they’re about or what they’re for.

**Official explanation from the W3C**

The W3C explains every success criterion in depth – with intent, examples and techniques.

[Understanding 2.4.6](https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels.html)

## More criteria from “Operable”

 [  2.1.1 Level A ### Keyboard

When every click can also be a keystroke.

 ](https://www.barrierefreihochzwei.de/en/wcag/2-1-1-keyboard) [  2.1.2 Level A ### No Keyboard Trap

When there’s no way out.

 ](https://www.barrierefreihochzwei.de/en/wcag/2-1-2-no-keyboard-trap) [  2.1.3 Level AAA ### Keyboard (No Exception)

When everything really has to work by keyboard.

 ](https://www.barrierefreihochzwei.de/en/wcag/2-1-3-keyboard-no-exception)
