Headings must indicate the topic or purpose of the content in that section of the page, and labels must indicate the purpose of the field they relate to. This ensures people with reading difficulties can understand the purpose of content, and that screen reader users can easily navigate to relevant sections of content on the page.
Accessibility Requirements for 2.4.6 Headings and labels (AA)
- Headings describe the purpose or topic of the content that follows;
- Labels indicate the purpose of the fields they relate to.
Common mistakes for 2.4.6 Headings and labels (AA)
- A heading does not indicate the purpose or topic of the content that follows;
- A label does not indicate the purpose of the field it relates to.
- The following are common mistakes that are considered failures of Success Criterion 2.4.6 by the WCAG Working Group.
FAQs for Headings and labels (AA)
How to use Headings and labels?
Use descriptive headings and subheadings in content where appropriate (a change in topic or purpose)
Use descriptive labels on controls and input fields
Few Tips for Headings and Labels
A single letter of the alphabet can be a good heading
If you regularly produce similar content, keep headings consistent
Make sure headings can be programmatically determined as required by Info and relationship
Why is this important?
Headings and labels that are clear and descriptive help all users quickly understand what information is contained on the webpage, how the page is organized, aid in comprehension, and provide easier navigation.