WCAG 2.4.6 — Headings and Labels Not Descriptive

Who Is Affected

Screen reader users who navigate by headings, users with cognitive disabilities who need clear signposts to understand content organization, and anyone quickly scanning a page to find specific information.

What This Means

Headings should tell users exactly what content they'll find in that section. Vague headings like "More Information," "Additional Details," "Resources," or "Other" force users to read through entire sections to understand what they contain.

Form labels must clearly identify what information is being requested. A label that says "Name" is unclear — is it asking for a person's name, company name, or project name?

Good headings act like a table of contents, allowing users to jump directly to the section they need without reading everything else first.

Fix: Content Editor

For Page Headings:

1. Review each heading on your page. Ask: "If someone heard only this heading, would they know what content follows?"
2. Replace vague headings with specific ones:
   • "Resources" → "Emergency Contact Phone Numbers"
   • "More Information" → "How to Apply for a Building Permit"
   • "Additional Details" → "Required Documents for Tax Appeals"
3. Use concrete nouns and action words instead of generic terms.
4. Keep headings concise but complete — aim for 2-8 words that capture the main topic.

For Form Labels:

1. Be specific about what type of information you're requesting:
   • "Name" → "Your Full Legal Name"
   • "Address" → "Property Address" or "Mailing Address"
   • "Phone" → "Daytime Phone Number"
2. Include format expectations when helpful:
   • "Date of Birth (MM/DD/YYYY)"
   • "Phone Number (including area code)"

Testing Your Headings:

Read only the headings on your page from top to bottom. Can someone understand the page's structure and find what they need? If not, make them more specific.

Fix: CMS / Theme

If your CMS is automatically generating generic headings:

Joomla:

1. Go to Content → Articles → [Your Article]
2. Check the "Options" tab for auto-generated headings from categories or tags
3. Override generic headings with custom, descriptive ones in the article content

WordPress:

1. Review your theme's heading templates (header.php, archive.php)
2. Replace generic the_title() or category names with more descriptive text where appropriate
3. Use custom fields or page builders to create specific headings rather than relying on auto-generated ones

Standard Reference

WCAG 2.1 Success Criterion 2.4.6 — Headings and Labels, Level AA

Headings and labels describe topic or purpose.

• W3C Understanding SC 2.4.6
• WCAG Technique G130 — Descriptive headings
• WCAG Technique H42 — Using h1-h6 to identify headings
• WCAG Failure F43 — Using structural markup for presentation