Skip to Main Content
It looks like you're using Internet Explorer 11 or older. This website works best with modern browsers such as the latest versions of Chrome, Firefox, Safari, and Edge. If you continue with this browser, you may see unexpected results.
Accessibility Information on Tables
Creating a properly structured table helps a blind, low-vision and/or screen reader user make sense of a table by reading out the heading titles and then cell content.
Why is making tables accessible important?
- Tables without structural markup to differentiate and properly link between header and data cells, create accessibility barriers.
- Tables used for layout are frowned upon because unless they are designed correctly they are not considered accessible; many accessibility advocates consider using tables for layout bad practice.
- Accessible tables allows users to perceive, operate understand, access in a robust manner, POUR principles.
How to create accessible tables:
- Make sure your tables have header rows and/or header columns.
- Avoid spanned rows and columns in data tables, especially as headers. Many screen readers cannot properly read these correctly.
- Make sure your header row or header column cells are NOT blank.
- It is okay to have blank data cells, just not a blank header cell.
- Tables without table headings are not accessible.
- Always use the simplest table configuration possible.
- After you’ve created headers, you need to associate the data cells with the appropriate headers .The scope attribute identifies whether a table header is a column header or a row header. <th scope=”col”>Name</th> or <th scope=”row”>Max</th>
- Data tables very often have brief descriptive text before or after the table that indicates the content of that table. This text should be associated to its respective table using the <caption> element. The <caption> element must be the first thing after the opening <table> tag.
LibGuides Table Instructions
- Do not create lists or tables manually, use the built in formatting.
Add a caption to your table.
- A table caption identifies the overall topic of a table and is useful in most situations. Captions help users to find a table and understand what it’s about and decide if they want to read it.
Add a summary to complex tables provides orientation or navigation hints in complex tables.
- A summary conveys information about the organization of the data in a table and helps users navigate it. For example, if a table has an unusual structure, information about what content can be found in which row or column can be provided to the user. A summary is usually only needed for complex tables.
If both caption and summary are provided for one table, the summary should not duplicate information present in the caption.