Layout table with role presentation Screen reader compatibility

Last updated: September 5, 2016

Expected Result: works in a screen reader

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

This test shows what happens when non-tabular data is presented in a layout table with role=presentation.

Related tests: Data table with role presentation

Code used for this test:


        <table role='presentation'>
          <tbody>
            <tr>
              <td><strong>Example</strong></td>
              <td><strong>Navigation</strong></td>
            </tr>
            <tr>
              <td>Links</td>
              <td>Content</td>
            </tr>
          </tbody>
        </table>
    

Change History

Last updated: September 5, 2016

Screen readerBrowserModeNotesWhat the user hears
OK NVDA 2016.2FF48 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK NVDA 2016.2IE11 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK NVDA 2015.2FF41 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK NVDA 2015.2IE11 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK NVDA 2014.1FF31 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK NVDA 2014.1IE11 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK JAWS 17.0.2619FF48 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK JAWS 17.0.2619IE11 ReadingTable treated as layout table - not announced as table. Speak Example, navigation, links, content.
OK JAWS 16.0.4350FF41 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK JAWS 16.0.4350IE11 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK JAWS 15.0.9023FF31 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK JAWS 15.0.9023IE11 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK JAWS 14.0.9002FF31 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK JAWS 14.0.9002IE11 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK WindowEyes 9.2IE11 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
Fail WindowEyes 8.4IE11 ReadingPresentation role ignored - treated as data table Speak Table one start, two rows, two columns. Example. Navigation. Links. Content.
OK VoiceOver OSX 10.11Safari 9.1.2 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK VoiceOver OSX 10.10Safari 8.0.4 ReadingTable treated as layout table - not announced as table. Speak Example. Navigation. Links. Content.
OK VoiceOver iOS 9.1Safari iOS 9.1 ReadingTable treated as layout table - not announced as table. Speak Example, navigation. Links, content.
OK VoiceOver iOS 8.4Safari iOS 8.4 ReadingTable treated as layout table - not announced as table. Speak Example, navigation. Links, content.
OK VoiceOver iOS 7.1Safari iOS 7.1 ReadingTable treated as layout table - not announced as table. Speak Example, navigation. Links, content.
OK Dolphin SR 15.05IE11 ReadingTable treated as layout table - not announced as table. Speak Normal, example. Navigation. Links. Content.
Fail SaToGo 3.6.22.0IE11 ReadingPresentation role ignored - treated as data table Speak Entering table, example. Navigation. Links. Content. Leaving table.

SortSite rules: AccWcag1-5.1.1

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: