Important: This website does not attempt to establish a standard for how assistive technologies must behave. Read the FAQ for more information. Additionally, this is a work in progress. Please submit feedback or suggestions.

heading role (aria)

Screen Reader support level: supported

On this page

About this feature

A heading for a section of the page.

Age of results

Results across all tests for this feature range from a year ago to 5 years ago. Detailed dates and version information can be found in associated tests.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
MUST convey its role and namesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey its default level as 2 if aria-level is missingsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST provide shortcuts to jump to headingssupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Expectation: convey its role and name

Rationale:

The user needs to know that the element describes the following content and the name of the heading.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • When applied to a heading, the heading might be announced as something like "<name> heading level <level>"
Screen Reader support for 'MUST convey its role and name'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML and ARIA headings test (level 6 and below)supportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
ARIA heading role with no aria-level attributesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
ARIA headings greater than level 6supportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Expectation: convey its default level as 2 if aria-level is missing

Rationale:

The user needs to know the level of the heading if aria-level is missing.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples:

  • When applied to a heading, the heading might be announced as something like "<name> heading level <level>"
Screen Reader support for 'MUST convey its default level as 2 if aria-level is missing'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
ARIA heading role with no aria-level attributesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Expectation: provide shortcuts to jump to headings

Rationale:

Headings provide an outline of the page and users need to be able to quickly navigate to different sections of the page.

Strength of this expectation for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA
Screen Reader support for 'MUST provide shortcuts to jump to headings'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML and ARIA headings test (level 6 and below)supportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
ARIA heading role with no aria-level attributesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
ARIA headings greater than level 6supportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
TestLast update
HTML and ARIA headings test (level 6 and below)2021-08-07
ARIA heading role with no aria-level attribute2021-07-28
ARIA headings greater than level 62024-01-31

Is something not right?

We use our GitHub repository to manage our issue tracking. Please provide as much information as you can for issues, and please leave the id in the issue title intact.

Create an issue for this feature