Technologies that support Accessible Rich Internet Applications (WAI-ARIA).
This technique relates to Success Criterion 1.3.1: Info and Relationships (Sufficient).
The purpose of this technique is to provide a way for Assistive Technologies (AT) to identify a piece of content as a heading. Applying role="heading" to an element causes an AT (like a screen reader) to treat it as though it were a heading.
If there is more than one heading on the page and the heading hierarchy is defined
visual presentation, the
aria-level attribute should be used to indicate the hierarchical level of
When possible, use native heading mark-up directly. For example, it is preferable
h1 rather than using <div role="heading" aria-level="1">. However, the use of the
heading role, instead of heading mark-up, may be necessary. For example, when retrofitting
a legacy site where scripts depend on the existing element hierarchy.
The use of the
heading role and nesting levels is discussed in WAI-ARIA Authoring Practices 1.1.
Example 1: Simple headings
This example demonstrates how to implement simple headings using role="heading" when retrofitting a legacy site where scripts depend on the existing element hierarchy or the level is unknown. For example, web content which is syndicated from various sources may be constructed without knowledge of what the final presentation will be.
<div role="heading">Global News items</div> ... a list of global news with editorial comment.... <div role="heading">Local News items</div> ... a list of local news, with editorial comment ...
Example 2: Additional heading levels
This example demonstrates how to implement a level 7 heading using role="heading"
aria-level attribute. Since HTML only supports headings through level 6, there is no native
element to provide these semantics.
... <h5>Fruit Trees</h5> ... <h6>Apples</h6> <p>Apples grow on trees in areas known as orchards...</p> ... <div role="heading" aria-level="7">Jonagold/div> <p>Jonagold is a cross between the Golden Delicious and Jonathan varieties...</p>
Resources are for information purposes only, no endorsement implied.
- Examine each element with the attribute role="heading".
- Determine whether the content of the element is appropriate as a heading.
- If the element has an
aria-levelattribute, determine whether the value is the appropriate hierarchical level.
- #2 and #3 are true.