Notice: 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/20)

Voice Control support level: not applicable

On this page

About this feature

Age of results

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

Failing and partial results are between 10 months ago and 10 months ago.

Expectations

What are expectations?

Screen Reader support by expectation

ExpectationJAWSNarratorNVDAOrcaTalkBackVoiceOver (iOS)VoiceOver (macOS)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
MUST convey its role, level, and namepartial (1/2)supportedpartial (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)supportedsupportedsupportedsupportedpartial (1/2)supportedsupported

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, 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 these expectations for different types of assistive technologies:

  • Screen Readers: MUST
  • Voice Control: NA

Examples of assistive technologies support this expectation:

  • 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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML and ARIA headings testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
HTML basic details/summary test with a heading in the summarynonesupportednonesupportedsupportedsupportednonenonesupportednone

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 these expectations 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)
ChromeIEFirefoxEdgeChromeFirefoxFirefoxChromeSafariSafari
HTML and ARIA headings testsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupportedsupported
HTML basic details/summary test with a heading in the summarynonenonenonesupportedsupportedsupportedsupportednonesupportedsupported