![Clemson University](../../images/wordmark-univ_wordmark-copur.jpg)
Tables
Tables provide structure for data. That structure is conveyed both visually and by screen readers.
Use tables to organize data, not to create content layouts.
Make sure tables have properly formatted headers for columns or rows. Do not rely solely on the visual style to convey that a header cell is a header cell. Avoid empty cells when possible.
Move table titles and footnotes out of the table structure. For example, avoid merging the top row of cells to put the table title in the first row. Instead, place the table's title above the table or in a table caption. If data in cells need additional clarification (as with an asterisk or when citing the author), the description should go underneath the table as paragraph text and not in a merged row across the bottom of the table.
Adhere to other accessible design concepts for table content: color contrast and reliance, alternative text for images, and link text.
Use a simple table design: a single header for rows and columns, where cells are not merged or split.
A complex table has structural formatting like merged or split cells, irregular or multi-level headers, and multiple data sets in separate sections of a single table. Authoring tools may limit the accessibility of complex tables. For example, in Microsoft Word, it is not possible to apply multiple column headers in a single table. See related techniques for more information.
For lengthy or complex data sets, provide a link to the data source (e.g., an accessible Excel file). And please, never nest a table within a table.
Techniques
Additional Resources
- Tables Tutorial (W3C)
- Understanding Information and Relationships (WCAG 2.1)