Embedded Files
Accessible tables use a simple structure with designated header rows and clear labels to organize data. Properly marked-up tables allow screen readers to convey the relationship between headers and data cells, making the information understandable.
Use the table tools to set header rows, avoid merged or split cells, and include a descriptive caption if needed. For example, a gradebook table should have a header row labeled "Student Name, Assignment 1, Assignment 2, Final Grade" so that screen readers announce each column with its label.
The following practical steps include information that is specific to tables. Other items must also be reviewed and addressed including: color contrast ratio, descriptive link text, accessible fonts, and so on.
Guidance to Improve Tables:
Guidance to Improve Tables:
Use Tables for Data, Not Layout
Use Tables for Data, Not Layout
Only use tables when presenting actual data (e.g., schedules, comparisons, statistics).
Do not use tables as a way to control layout or spacing in documents or pages.
WCAG Alignment
1.3.1 Info and Relationships (A): Tables must accurately represent data relationships and not be misused for layout.
Recommended Actions:
Replace layout tables with proper formatting tools.
If possible, restructure content so that tables are not necessary.
Identify Header Rows and Columns
Identify Header Rows and Columns
Mark header rows (and columns if needed) so screen readers can announce them with the data cells.
Ensure it is easy to understand which headers apply to which data points.
WCAG Alignment
1.3.1 Info and Relationships (A): Table headers and data relationships must be programmatically determinable.
Recommended Actions:
Run accessibility checkers such as YuJa Panorama or Grackle to identify tables where headers are needed.
In Word/Google Docs: Select the top row → Right-click → Table Properties → check “Header Row and "First Column" as necessary.
In Excel: Use the “Header Row” option under Table Design.
Keep Tables Simple
Keep Tables Simple
Use simple tables whenever possible (one header row, no merged cells).
Avoid nested tables or complex structures that screen readers cannot easily interpret.
WCAG Alignment
1.3.2 Meaningful Sequence (A): Tables must present information in a meaningful and logical reading order.
Recommended Actions:
Remove merged or split cells and reorganize the data into separate rows/columns instead.
Break large, complex tables into smaller ones if needed.
Provide Captions or Summaries When Helpful
Provide Captions or Summaries When Helpful
Add a short caption or descriptive title above the table to explain its purpose.
For tables with large amounts of information, use surrounding text to summarize key takeaways so students don’t have to interpret the data alone.
WCAG Alignment
1.3.1 Info and Relationships (A): Captions and summaries help clarify relationships and meaning of data.
Recommended Actions:
Add a caption above the table to indicate what it is about.
If the table is long, provide a short written summary so students don’t have to interpret all information on their own.
In spreadsheets, ensure that workbook tabs have descriptive names.
Resources:
Resources:
Page updated
Report abuse