WCAG 2.4.6 Headings and Labels
WCAG 2.4.6 Headings and Labels explained: headings and form labels must describe the topic or purpose. What fails, how to test, and who it helps.
Table of contents
WCAG 2.4.6 Headings and Labels is a Level AA success criterion, from WCAG 2.0. This page is part of the WCAG 2.2 success criteria guide. It explains the rule in plain English, who it helps, what passing and failing code look like, and how to test it by hand and with AccessBell, a website accessibility monitoring tool. AccessBell is not an overlay.
What WCAG 2.4.6 Headings and Labels requires
Headings and labels describe topic or purpose.
That sentence is the heart of the criterion. The exceptions and notes are in the WCAG 2.2 Recommendation and the Understanding document for 2.4.6 Headings and Labels.
What WCAG 2.4.6 means in plain English
WCAG 2.4.6 Headings and Labels is short because the bar is “does this name say what is here?” A heading of “Section 2” or “Welcome” fails when it does not describe the section. A label of “Field” or “Click here” fails when it does not say what the person should enter or do.
This criterion assumes the heading or label exists. Missing headings are a problem for 1.3.1 Info and Relationships, which asks for structure in the code. A label that is missing entirely is 3.3.2 Labels or Instructions and, for the accessible name, 4.1.2 Name, Role, Value. 2.4.6 is the quality of the words once the heading or label is there.
Who WCAG 2.4.6 helps
People who navigate by headings with a screen reader, people with cognitive disabilities who scan a page by its headings, and anyone using a form who needs to know what a field is for before they type. Vague labels also hurt people using voice control, because the spoken name is the label.
Pass and fail examples
<section>
<h2>Section 2</h2>
<label for="f1">Field</label>
<input id="f1" name="f1" required>
</section> <section>
<h2>Shipping address</h2>
<label for="zip">ZIP code</label>
<input id="zip" name="zip" autocomplete="postal-code" required>
</section> How to test WCAG 2.4.6
- Open the page’s heading list (the Headings feature in a screen reader, or the document outline in browser devtools). Read each heading with the section hidden. If you cannot predict the section, rewrite the heading.
- Read every form label and button out of context. “Email address” passes. “Required” or “Click here” does not.
- Check that two fields that collect different things do not share one vague label such as “Name” twice, unless the heading above them makes the group clear and each field is still specific (First name, Last name).
Testing WCAG 2.4.6 with AccessBell
A website accessibility monitoring tool can flag a missing label or an empty heading. It cannot judge whether the words “Welcome” describe the section. AccessBell lists 2.4.6 for a person to review when automation cannot score the wording.
Check your site for this with a free scan of one public page. AccessBell is a website accessibility monitoring tool, not an overlay.
Common failures on Shopify, WordPress, Wix and Squarespace
These are patterns in how the builders work. They are not counts from AccessBell scans. Where a platform hosts the screen, a merchant may not be able to change it, and an unscanned page is not a pass.
Shopify
Theme sections ship with headings such as “Featured collection” or “More” that do not name the products. Collection and product templates are the place to rewrite them. Form labels in the theme (search, newsletter) often say only “Email”. Scan the theme with the Shopify checker and read the headings yourself.
WordPress
The block editor will let a heading say anything, including “Heading”. Contact-form plugins label fields from the placeholder or from “Your field”. Rename both the visible label and the heading in the editor, then check the page with the WordPress checker.
Wix
Text can be styled to look like a heading without being one, which is 1.3.1, and a real heading can still say nothing useful, which is 2.4.6. The Wix checklist covers heading structure. The wizard does not grade whether the words describe the section. Use the Wix checker for the code, and read the labels.
Squarespace
Squarespace’s inclusive design guidance says to use real headings in order. The Squarespace checklist maps that to 1.3.1 and page titles to 2.4.2. 2.4.6 is the next check: the heading text itself has to name the section, not just be an H2. Rewrite “Welcome” and “Read more” in the text toolbar.
Level and conformance
Level AA, in WCAG since 2.0, under Navigable. It applies to headings and to labels on controls. It does not require a heading on every section. That stronger rule is 2.4.10 Section Headings, which is Level AAA. Descriptive link text is 2.4.4 Link Purpose (In Context), Level A.
Conforming at Level AA means meeting every Level A and Level AA criterion that applies, not only the ones labeled AA. See the WCAG 2.2 conformance requirements. This page explains the technical rule. It is not a legal opinion. Read the disclaimer.
Related WCAG criteria
- 1.3.1 Info and Relationships (Level A, WCAG 2.0)
- 3.3.2 Labels or Instructions (Level A, WCAG 2.0)
- 2.4.2 Page Titled (Level A, WCAG 2.0)
- 2.4.4 Link Purpose (In Context) (Level A, WCAG 2.0)
Every criterion is listed in the WCAG 2.2 success criteria guide.
Frequently Asked Questions
What level is WCAG 2.4.6 Headings and Labels?
Level AA. It has been in WCAG since 2.0. A WCAG 2.2 Level AA target includes it.
Does every section need a heading under 2.4.6?
No. 2.4.6 says that headings and labels which are present describe the topic or purpose. Requiring headings for every section is 2.4.10 Section Headings, Level AAA.
Is placeholder text a label for 2.4.6?
No. A placeholder is not a label. The visible label has to name the field, and it has to stay visible while someone types. A missing label is also a failure of 3.3.2 Labels or Instructions.
Sources
- W3C: Understanding 2.4.6 Headings and Labels (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.