Accessible Tables
- Michele Bromley
- Alex Patterson
This help article outlines why accessible tables are important to consider when creating content, how content authors should use tables, and where tables may be relevant.
Table accessibility refers to the practice of designing and structuring tables in a way that makes them easily perceivable, understandable, and navigable for all users, including those with disabilities.
Why are Accessible Tables Important?
Tables are a common way to present complex information in an organized manner, making it easier for users to comprehend the content. Accessible tables are particularly important for users who rely on assistive technologies, such as screen readers, as proper table structure enables them to efficiently navigate and understand the information presented. It is critical for the accessibility of your content that any tables within your document are specifically used for data only and are organized with clear table structure using a header row and/or column.
An accessible table allows users with screen reading software to quickly and directly navigate to the information they’re looking for within a table. Likewise, a visually accessible and engaging table allows sighted users to quickly find the information they’re looking for by examining a table’s headings.
How do I create Accessible Tables?
Use Header Rows/Columns
All tables should have one header column, one header row, or both one header column and header row. Whether you choose to implement a header column, row, or both will depend on the situation and the information you’re communicating.
Using a header row
Team Name | Matches Played | Matches Won | Matches Drawn | Matches Lost | Points |
|---|---|---|---|---|---|
Portland | 3 | 2 | 0 | 1 | 6 |
Vancouver | 1 | 1 | 0 | 0 | 3 |
Seattle | 2 | 0 | 0 | 2 | 0 |
Using a header column
Name | Bob Loblaw | Jack Olbermann | Randy Keith |
Age | 21 | 23 | 31 |
Height | 5’7” | 5’6” | 6’6” |
Using a header row and a header column
| Monday | Tuesday | Wednesday | Thursday | Friday |
|---|---|---|---|---|---|
9:00 | Morning email check, coffee | Morning email check, coffee | Morning email check, coffee | Morning email check, coffee | Project work time, coffee |
10:00 | Bi-weekly meeting with Joanne | Department policy review | Bi-weekly meeting with Joanne | Department social | Project work time |
11:00 | Web accessibility webinar | Project work time | Grading papers | Finish grading papers | Project work time |
12:00 | Lunch break | Lunch break | Lunch break | Lunch break | Lunch break |
Avoid Tables for Layout
Tables should only be used as a way to organize and present data; tables should not be used for formatting or design purposes.
Keep Tables Simple
Complex tables with merged cells, nested tables, or multiple levels of headers can be difficult to navigate and understand for users with disabilities. Whenever possible, simplify the table structure and break complex tables into simpler ones.
Where Should I Utilize Tables?
Please reference the following resources to learn how to work with tables in your content:
HTML Content
For faculty and staff: Content and Media at pdx.edu
Non-HTML Content
Adobe Acrobat
Foxit PhantomPDF
Microsoft Office
Google Workspace
University Policy Connection
Accessible use of tables is a critical step in complying with Web Content Accessibility Guidelines (WCAG) 2 per Portland State University’s Digital Accessibility Policy. Please reference the following World Wide Web Consortium help article for more information:
If faculty or staff have any additional questions regarding digital accessibility for public-facing digital resources at PSU, please email help-accessibility@pdx.edu or submit a Digital Accessibility Support ticket.