Data table with role=table
Screen reader compatibility
ARIA HTML
Dec 12, 2023
Expected Result: works in a screen reader
Actual Result: causes problems in 1 screen reader / browser combinations
This test checks that applying role=table overrides layout table heuristics.
Code used for this test:
<table role='table'>
<tbody>
<tr>
<td>This is some text</td>
</tr>
</tbody>
</table>
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.
Change History
Last updated: December 12, 2023
NVDA with Chrome Stable - OK from NVDA 2022.2 to NVDA 2023.3
NVDA with FF Stable - OK from NVDA 2022.2 to NVDA 2023.3
JAWS with Chrome Stable - OK from JAWS 2022.2207.25 to JAWS 2023.2311.34
JAWS with FF Stable - OK from JAWS 2022.2207.25 to JAWS 2023.2311.34
VoiceOver macOS OK in VoiceOver macOS 13.6
VoiceOver iOS Better - caused problems in VoiceOver iOS 15.6, but now OK in VoiceOver iOS 16.6
Screen reader | Browser | Mode | Notes | What the user hears |
---|---|---|---|---|
![]() | Chrome 120 | Reading | Table with 1 rows and 1 columns. Row 1, columns 1, this is some text. | |
![]() | FF 115 | Reading | Table with 1 rows and 1 columns. Row 1, columns 1, this is some text. | |
![]() | Edge 120 | Reading | Table with 1 rows and 1 columns. Row 1, columns 1, this is some text. | |
![]() | Chrome 105 | Reading | Table with 1 rows and 1 columns. Row 1, columns 1, this is some text. | |
![]() | FF 102 | Reading | Table with 1 rows and 1 columns. Row 1, columns 1, this is some text. | |
![]() | Edge 105 | Reading | Table with 1 rows and 1 columns. Row 1, columns 1, this is some text. | |
![]() | Chrome 120 | Reading | Table with 1 columns and 1 rows. This is some text. | |
![]() | FF 115 | Reading | Table with 1 columns and 1 rows. This is some text. | |
![]() | Edge 120 | Reading | Table with 1 columns and 1 rows. This is some text. | |
![]() | Chrome 105 | Reading | Table with 1 columns and 1 rows. This is some text. | |
![]() | FF 102 | Reading | Table with 1 columns and 1 rows. This is some text. | |
![]() | Edge 105 | Reading | Table with 1 columns and 1 rows. This is some text. | |
![]() | Safari 16.6 | Reading | Table, 1 column, 1 row. This is some text, column 1 of 1. | |
![]() | Safari iOS 16.6 | Reading | Treated as a data table. | This is some text. Table start, end. |
![]() | Safari iOS 15.6 | Reading | Role ignored, treated as a layout table. | This is some text. |
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