Interactive iframe with role=presentation and negative tabindex and no accessible name Screen reader compatibility

HTML
Dec 12, 2023

Expected Result: works in a screen reader

Actual Result: causes problems in 13 screen reader / browser combinations

Tests if role=presentation with tabindex=-1 affects accessibility tree. Tabindex makes the iframe click focusable which should trigger presentational role conflict .

Code used for this test:


		<iframe src='1234.html' width='400' height='100' role='presentation' tabindex='-1'> </iframe>
	

Reliability Trend

This graph shows reliability over time for this code in NVDA, JAWS and Voiceover. Other screen readers don't have enough historical data yet to plot trends.

100%80%60%40%20%0%2015201620172018201920202021202250%202353%

Change History

Last updated: December 12, 2023

  • Bad NVDA with Chrome Causes problems in NVDA 2023.3
  • Bad NVDA with FF Causes problems in NVDA 2023.3
  • Bad JAWS with Chrome Causes problems in JAWS 2023.2311.34
  • Bad JAWS with FF Causes problems in JAWS 2023.2311.34
  • Bad VoiceOver macOS Causes problems in VoiceOver macOS 13.6
  • Good VoiceOver iOS OK in VoiceOver iOS 16.6
Screen readerBrowserModeNotesWhat the user hears
OK NVDA 2023.3Chrome 120 Reading Example target grouping, this is a link, example hyperlink, in the target page.
Fail NVDA 2023.3Chrome 120 Tabbing Skips over focusable link in iframe
OK NVDA 2023.3FF 115 Reading role=presentation makes frame seamless Frame, this is a link, example hyperlink, in the target page.
Fail NVDA 2023.3FF 115 Tabbing Skips over focusable link in iframe
OK NVDA 2023.3Edge 120 Reading Reads as group role instead of frame role, and reads title element of iframe document Example target grouping, this is a link, example hyperlink, in the target page
Fail NVDA 2023.3Edge 120 Tabbing Skips over focusable link in iframe
OK NVDA 2022.2Chrome 118 Reading Example target grouping, this is a link, example hyperlink, in the target page.
Fail NVDA 2022.2Chrome 118 Tabbing Skips over focusable link in iframe
OK NVDA 2022.2FF 102 Reading role=presentation makes frame seamless This is a link, example hyperlink, in the target page.
Fail NVDA 2022.2FF 102 Tabbing Skips over focusable link in iframe
OK NVDA 2022.2Edge 120 Reading Reads as group role instead of frame role, and reads title element of iframe document Example target grouping, this is a link, example hyperlink, in the target page
Fail NVDA 2022.2Edge 120 Tabbing Skips over focusable link in iframe
OK JAWS 2023.2311.34Chrome 120 Reading Group start, example target. This is an. Link, example hyperlink. In the target page.
Fail JAWS 2023.2311.34Chrome 120 Tabbing Skips over focusable link in iframe
OK JAWS 2023.2311.34FF 115 Reading role=presentation makes frame seamless This is an. Link, example hyperlink. In the target page.
Fail JAWS 2023.2311.34FF 115 Tabbing Skips over focusable link in iframe
OK JAWS 2023.2311.34Edge 120 Reading Group start, example target. This is an. Link, example hyperlink. In the target page.
Fail JAWS 2023.2311.34Edge 120 Tabbing Skips over focusable link in iframe
OK JAWS 2022.2207.25Chrome 118 Reading Group start, example target. This is an. Link, example hyperlink. In the target page.
Fail JAWS 2022.2207.25Chrome 118 Tabbing Skips over focusable link in iframe
OK JAWS 2022.2207.25FF 102 Reading role=presentation makes frame seamless This is an. Link, example hyperlink. In the target page.
Fail JAWS 2022.2207.25FF 102 Tabbing Skips over focusable link in iframe
OK JAWS 2022.2207.25Edge 120 Reading Group start, example target. This is an. Link, example hyperlink. In the target page.
Fail JAWS 2022.2207.25Edge 120 Tabbing Skips over focusable link in iframe
OK VoiceOver macOS 13.6Safari 16.6 Reading role=presentation makes frame seamless This is an. Example hyperlink, link. In the target page.
Fail VoiceOver macOS 13.6Safari 16.6 Tabbing Skips over focusable link in iframe
OK VoiceOver iOS 16.6Safari iOS 16.6Touch This is an. Example hyperlink, link. In the target page.

Test notes

All tests were carried out with screen reader factory settings. JAWS in particular has a wide variety of settings controlling exactly what gets spoken.

Screen readers allow users to interact in different modes, and can produce very different results in each mode. The modes used in these tests are:

  • Reading Content read using the “read next” command in a screen reader
  • Tabbing Content read using the “tab” key in a screen reader
  • Heading Content read using the “next heading” key in a screen reader
  • Touch Content read when touching an area of screen on a mobile device

In the “What the user hears” column:

  • Commas represent short pauses in screen reader voicing
  • Full Stops represent places where voicing stops, and the “read next” or “tab” or “next heading” command is pressed again
  • Ellipsis … represent a long pause in voicing
  • (Brackets) represent voicing that requires a keystroke to hear