Notice: This is a work in progress. Please submit feedback or suggestions.

heading role (aria)

Screen reader support level: supported

Voice Control support level: not applicable

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 4 months ago to a year 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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
MUST convey its role and namesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST convey its default level as 2 if aria-level is missingsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
MUST provide shortcuts to jump to headingssupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

Voice Control support by expectation

ExpectationDragon Naturally SpeakingVoice Access (Android)Voice Control (iOS)Voice Control (MacOS)Windows Speech Recognition
ChromeChromeSafariSafariChrome
Not applicable

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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML and ARIA headings testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
ARIA heading role with no aria-level attributesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
ARIA heading role with no aria-level attributesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported

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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML and ARIA headings testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
ARIA heading role with no aria-level attributesupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported