Tables Screen reader compatibility

Last updated: September 5, 2016

Screen reader compatibility for HTML tables, showing how failures and techniques work in specific screen reader / browser combinations.

The results include two types of test:

Note: Screen readers attempt to detect layout tables using heuristics, which vary widely between screen readers. When a layout table is detected, a screen reader linearizes the cells into a series of paragraphs, which prevents the table data being understood as a grid. This causes serious problems when a data table is wrongly identified as a layout table. For example, consider trying to understand the Periodic Table of the Elements as a long series of element names without the columns.

Sometimes works

These tests use conformant HTML or WCAG sufficient techniques and might be expected to work in screen readers. This doesn't always happen.

Screen ReaderNVDAJAWSVoiceOverWin-EyesDolphinSaToGo
BrowserIEFFIEFFMaciOSIEIEIE
Should work. Fails in 1% - 25% Data table with CAPTION and THGoodGoodBetterBetterGoodGoodGoodGood
Should work. Fails in 1% - 25% Data table with SUMMARY and THGoodGoodBetterBetterGoodGoodGoodGood
Should work. Fails in 26% - 50% Data table with TD HEADERS attributeBadGoodBetterBetterBadBadGood
Should work. Fails in 1% - 25% Data table with TH cell headersGoodGoodBetterGoodGoodBetterGoodGoodGood
Should work. Fails in 51% - 75% Data table with TH row/columns headers with SCOPEBadBadGoodGoodBadBadBetter
Should work. Fails in 26% - 50% Data table with role gridBetterGoodBetterBetterBetterBetterGoodGoodBad
Should work. Fails in 51% - 75% Data table with role rowheader headers but no THBadBadGoodGoodBadBadGoodBadGood
Should work. Fails in 1% - 25% Layout table with role presentationGoodGoodGoodGoodGoodGoodBetterGoodBad
Should work. Fails in 1% - 25% Layout table with single cellGoodGoodGoodGoodGoodGoodGoodGoodBad

Expected to fail

These tests use non-conformant HTML or WCAG failures and are expected to fail in screen readers.

Screen ReaderNVDAJAWSVoiceOverWin-EyesDolphinSaToGo
BrowserIEFFIEFFMaciOSIEIEIE
Should fail. Fails in 76% - 100% Data table with CAPTION but no THBadBadBadBadBadBadGoodBadGood
Should fail. Fails in 76% - 100% Data table with SUMMARY but no THBadBadBadBadBadBadGoodBadGood
Should fail. Fails in 51% - 75% Data table with TH row/columns headers without SCOPEBadBadBetterBetterBadBadWorse
Should fail. Fails in 51% - 75% Data table with THEAD, TFOOT but no THBadBadBadBadGoodBetterGoodGoodGood
Should fail. Fails in 76% - 100% Data table with no TH elementsBadBadBadBadBadBadGoodBadGood
Should fail. Fails in 76% - 100% Data table with null SUMMARY but no THBadBadBadBadBadBadGoodBadGood
Should fail. Fails in 51% - 75% Data table with role noteBetterBadBadBadBadBadWorseGoodGood
Should fail. Fails in 76% - 100% Data table with role presentationBadBadBadBadBadBadWorseGoodGood

Key

Tests expected to fail (due to authoring errors) are marked with Expected to Fail.

Test notes

The threshold for inclusion in these results is 5% usage in the most recent WebAIM screen reader survey. Chrome and Android still fall below the 5% threshold.

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:

In the «What the user hears» column: