Appropriate use of Tables
The layout of the contents of a web page can be set in tables but this can mean that a screen reader user has to listen to what comes first as the software reads across the page from left to right. It may not read down individual columns before crossing to the next row so it is best to keep tables very simple or just for data. The order of content within the table and the use of row and column headers is important. (W3C WCAG 2.0 1.3 and W3C WCAG 2.0 3.2).
Testing Techniques
These techniques may be used to perform the test.
Method
Quick Overview: Web Developer Toolbar - outline tables then manual assessment.
Criteria for this Test
 |
Page layout is built using tables and access is poor |
|---|---|
 |
Data tables, if used, have no headings. Layout tables do not impact on screen reader. |
 |
Data tables incorrect layout. Navigation with a screen reader possible with effort. |
 |
Page layout does not use tables and/or headered tables are used to present data. |
