|
|
|
|
|
Headings
Guideline
Headings and labels describe topic or purpose.
Intent
The intent of this regulation is to help users understand what information is contained in Web pages and how that information is organized. When headings are clear and descriptive, users can find the information they seek more easily, and they can understand the relationships between different parts of the content more easily. Descriptive labels help users identify specific components within the content.
Labels and headings do not need to be lengthy. A word, or even a single character, may suffice if it provides an appropriate cue to finding and navigating content.
Finding Applicable Components
- Visually identify where headings are used on the page, through formatting or use of white space, boxes or other visual separators.
Inspecting and Using Components
- Check that any visual headings are also marked as headings, , etc, by inspecting the visual heading with the browser developer tools.
- Ensure that the proper heading level order is correct. For example, There is at least (1) heading before an heading in the document structure.
- Ensure that the heading properly describes its associated content.
Section 508/WCAG 2.0 Failure Conditions
- Visually apparent headings are not programmatically identified.
- Fails 1194.31(a): Use without vision.
- Fails 1194.31(b): Use with low vision.
- Fails 1.3.1 Info and Relationships
- Programmatically identified heading levels do not match the visual outline level.
- Fails 1194.31(a): Use without vision.
- Fails 1194.31(b): Use with low vision.
- Fails 1.3.1 Info and Relationships.
- Headings do not correctly identify their associated content
- Fails 2.4.6 Headings and Labels.
Reporting Test Results
- Any failure in Section 508 Failure Conditions results in: Fails Baseline Requirement #15.
- Visually apparent headings are programmatically identified AND heading levels match the visual outline level then: Passes Baseline Requirement #15.
See Also |