Tip #12: The How – Tables

TLDR;
Tables should be used only for data, not for layout. When used correctly with headers and simple structure, tables improve digital accessibility by helping screen readers and users understand relationships between information. This week, review one table you use and check that it’s structured intentionally. Learn more from NCADEMI's guidance on Tables.

Hello Team,

Welcome back to our Accessibility Tips & Tricks series!
This week, we continue our hands-on work with the NCADEMI Accessibility Basics by focusing on Tables. Tables are powerful tools for organizing data, but they require thoughtful structure to support strong digital accessibility.

Why Tables Matter

Tables communicate relationships between pieces of information. When tables are created properly, screen readers can identify headers and read data in a meaningful way. When tables are not structured well, they can quickly become confusing or unusable.

Tables support users who:

• use screen readers

• rely on clear data relationships

• benefit from well-organized information

• need to compare values or categories

Learn more from NCADEMI’s guidance on Tables.

When Should I Use a Table?

Use tables only when presenting data that needs to be compared or related, such as:

• schedules

• data sets

• charts with rows and columns

• comparisons

Avoid using tables for layout or spacing. If content doesn’t need rows and columns, it likely shouldn’t be a table.

What Makes a Table Accessible?

Accessible tables are simple, intentional, and clearly labeled.

That means:

• Use built-in table tools

• Include column headers (and row headers when needed)

• Keep tables as simple as possible

• Avoid merged or split cells

• Ensure information makes sense when read left to right, top to bottom

Think clarity before complexity.

Common Table Mistakes

Watch for these common issues:

• Tables used only for visual layout

• Missing header rows

• Merged cells that disrupt reading order

• Complex tables with nested information

• Empty cells that may cause confusion

These may look fine visually but can be difficult for assistive technology to interpret.

Your task for this week

1. Open a document or resource that includes a table.

2. Ask: “Is this table being used for data, not layout?”

3. Add or confirm header rows and clear labels.

4. Simplify the table if possible.

5. Bring questions or examples to office hours if you’d like feedback.

Next week, we’ll explore the final NCADEMI Accessibility Basics concept, Text Contrast, and how this impacts readability and digital accessibility for all users.

Thank you for continuing to make digital accessibility part of your everyday practice. Small improvements like these add up in powerful ways.

ESU 10 Accessibility Implementation and Planning Team