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.

h1, h2, h3, h4, h5, and h6 elements (html)

Screen Reader support level: partial (15/22)

On this page

About this feature

Age of results

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

Caution

Failing or partial results may be out of date. The oldest result is from 3 years ago. Consider running the associated tests and contributing results.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
MUST convey its role, level, and namepartial (1/2)partial (1/2)partial (1/2)partial (1/2)supportedsupportedsupportedpartial (1/2)partial (1/2)supportedpartial (1/2)
SHOULD provide shortcuts to jump to headingspartial (1/2)partial (1/2)partial (1/2)supportedsupportedsupportedsupportedsupportedpartial (1/2)supportedsupported

Expectation: convey its role, level, and name

Rationale:

The user needs to know that the element describes the following content, the level of the heading in the document outline, 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, level, and name'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML and ARIA headings test (level 6 and below)supportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
HTML basic details/summary test with a heading in the summarynonenonenonenonesupportedsupportedsupportednonenonesupportednone

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: SHOULD
  • Voice Control: NA
Screen Reader support for 'SHOULD provide shortcuts to jump to headings'
TestJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeEdgeFirefoxEdgeChromeEdgeFirefoxFirefoxChromeSafariSafari
HTML and ARIA headings test (level 6 and below)supportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
HTML basic details/summary test with a heading in the summarynonenonenonesupportedsupportedsupportedsupportedsupportednonesupportedsupported
TestLast update
HTML and ARIA headings test (level 6 and below)2021-08-07
HTML basic details/summary test with a heading in the summary2022-05-27

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