Tables

Access barriers
Guidelines for overcoming access barriers
Activity

Tables can be useful when presenting information in a succinct and easy-to-read format. They can also assist in the layout of a document.

Tables should be used for presenting tabular data. Tables should be avoided for layout purposes, if possible. Layout should be achieved through the use of CSS and <div> elements.

The following site has good information on how to avoid tables in layout http://glish.com/css.

Access barriers

• By default a screen reader reads all the text in the first cell of row one, the second cell, the third, and so on until it runs out of cells. Then, it reads the first cell of row two, the second, etc. You will need to consider this when creating both layout and data tables.

Back to top

Guidelines for overcoming access barriers

1. Identify row and column headers for simple data tables. A simple table has one row of headings or one column of headings, or both. TABLES EXAMPLE 1
2. For a complex data table, use mark-up to associate data cells and header cells. TABLES EXAMPLE 2
3. Consider breaking complex tables into simple tables.
4. Provide a summary and a caption for tables. TABLE EXAMPLE 4
5. Try not to use tables for layout. W3C recommends the use of CSS for layout. If you do use a table for layout, include a null summary attribute, for example <table summary="">.
6. Use tables for layout only if they make sense when linearised. If they don't make sense provide an alternative equivalent. TABLES EXAMPLE 6
7. Provide abbreviations for header labels. TABLES EXAMPLE 7

Back to top

Activity

If tables are part of your website, use the checklist below to assess any accessibility barriers that may be present. If you have ticked 'no' for any item, go to the Guidelines for how to overcome this barrier.

Using tables

---

1. Row and column headers for data tables are identified.

   Yes No N/A

   ---

2. Mark-up is used to associate data cells and header cells for complex data tables.

   Yes No N/A

   ---

3. Complex tables have been broken down to simple tables where appropriate.

   Yes No N/A

   ---

4. A summary and a caption for tables are provided.

   Yes No N/A

   ---

5. Tables are only used for layout where necessary.

   Yes No N/A

   ---

6. Tables are used only when they make sense when linearised.

   Yes No N/A

   ---

7. Abbreviations are provided for header labels.

   Yes No N/A

Back to top