7 · 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 just for data. The order of content within the table and the use of row and column headers is important.
Outcomes and Scores
This test has 5 possible outcomes.
| Outcome | Score |
|---|---|
| Tables have correct semantics for headers and present data in the correct order. They can be easily navigated with a screen reader. Table captions and summaries are provided. | 100% |
| Data tables have some semantics linking cells to headers in rows and columns. Navigation with a screen reader possible with effort. Table captions and summaries are provided. | 67% |
| Some data tables, if used, have no headers for rows or columns. Incomplete table captions or summaries. | 33% |
| Page layout is built using tables and access is poor. Data tables do not have semantic headers, captions or summaries. | 0% |
| Not applicable | N/A |
Disabilities
The results of this test are taken into account when calculating accessibility scores for the following disability.
Techniques
The following technique may come in handy when running this test.
References
This test aims to cover the following section of best practice.
| Document | Section | Heading | |
|---|---|---|---|
| WCAG 2.1 | 1.3.1 | Info and Relationships | More Info |