Accessible Tables: Organize data for everyone

What are accessible tables?

Accessible tables organize data so everyone can understand it, including people using screen readers and other assistive technologies. They use proper structure to show clear relationships between information.

When to use tables

Use tables for:

  • Comparing data across categories
  • Displaying structured information like schedules or contact lists
  • Organizing complex datasets
  • Showing numerical relationships and trends

Don't use tables for:

  • Page layout or positioning content
  • Simple lists (use bullet points instead)
  • Text alignment (use paragraph formatting)

Tables with charts and graphs

When you include charts, always provide the underlying data in a table format. This gives assistive technology users access to the exact information shown visually.

How to create accessible tables

Follow these steps to create accessible tables in any application:

  1. Plan your structure: Choose the simplest layout that presents your data clearly.
  2. Use built-in table tools: Insert tables using your application's Insert → Table feature, not manual formatting.
  3. Add a clear caption: Write a brief description of what the table contains.
  4. Designate header rows: Mark the first row as headers using Table Design options.
  5. Use descriptive headers: Write clear labels like "Total Sales ($)" instead of just "Total".
  6. Keep formatting simple: Avoid merged cells and complex styling that can confuse assistive technologies.

Key reminders:

  • Always designate header rows using Table Design menus
  • Use captions instead of alt text for tables
  • Test navigation with Tab and arrow keys
  • Keep data types consistent within each column

Check your work

Quick accessibility checklist:

  • ✓ Table has a clear caption
  • ✓ Headers are designated and descriptive
  • ✓ Data is organized logically
  • ✓ Reading order makes sense (left-to-right, top-to-bottom)
  • ✓ Table can be navigated with keyboard only

Test questions:

  • Can someone understand the table purpose from the caption alone?
  • Are the headers clear without seeing the data?
  • Does the table make sense when read row by row?

Related WCAG resources

These Web Content Accessibility Guidelines (WCAG) provide additional technical details for accessible tables:

Back to top