What level is WCAG 2.4.6?

WCAG 2.4.6 Headings and Labels is a Level AA criterion under the Operable principle.

Level AA Operable

WCAG 2.4.6: Headings and Labels

Headings and labels must describe the topic or purpose of the content they introduce. Clear headings allow users to scan pages and understand structure. Labels help users understand the purpose of form inputs.

What is WCAG 2.4.6 Headings and Labels?

WCAG 2.4.6 Headings and Labels is a Level AA web accessibility success criterion under the Operable principle. Headings and labels must describe the topic or purpose of the content they introduce. Clear headings allow users to scan pages and understand structure. Labels help users understand the purpose of form inputs. Common failures include vague headings like 'overview' or 'details' without context and form labels that do not describe the expected input. Meeting this criterion is essential for accessible, inclusive web design.

How to Test

✓ Read each heading — does it describe the content that follows?
✓ Check that headings do not use vague text like 'Section 1' or 'More Info'
✓ Verify form labels clearly describe what input is expected
✓ Check that section headings in a page create a logical outline
✓ Use a screen reader to navigate by headings and verify the experience

Common Failures

✗ Vague headings like 'Overview' or 'Details' without context
✗ Form labels that do not describe the expected input
✗ Missing headings in content sections
✗ Headings chosen for visual size rather than document structure
✗ Label text that does not match the visual label

✓ Good Example

<h1>Account Settings</h1>
<h2>Personal Information</h2>
<label for="full-name">Full Name</label>
<input id="full-name" type="text">

<h2>Security Settings</h2>
<label for="current-pw">Current Password</label>
<input id="current-pw" type="password">

Each heading describes its section. Labels clearly identify what information the input expects.

✗ Bad Example

<h1>Settings</h1>
<h4>Section 1</h4>
<label for="field1">Field 1</label>
<input id="field1" type="text">

<h2>Section 2</h2>
<label for="field2">Enter value</label>
<input id="field2" type="text">

Headings skip from h1 to h4 (breaking hierarchy) and use generic names. Labels do not describe what information is expected.