How do I tell if a table is data or layout?

If it exists to align visual content and contains no meaningful relationships, it should be handled as a presentational layout. If it represents data with rows/columns, it needs proper headers and associations.

Do all data tables need a summary?

Not always. Summaries are especially helpful when a table is dense, complex, or hard to understand via linear navigation (especially when headers don’t fully explain the structure).

What should we validate with a screen reader?

Confirm that when you navigate cell by cell, the screen reader gives enough context (row and column meaning). The user should understand what each value represents without guessing.

Accessible tables RGAA checklist

Tables often become barriers when headers and associations are missing, or when a dense layout is presented as “data”. This checklist helps you make table content understandable for screen reader users (and for everyone).

1) Start with the right mental model

Data table: represents relationships between rows and columns (needs real structure).
Layout table: exists for visual alignment only (should not be interpreted as data).

2) Give the table a meaningful title or caption

Add a caption or clear table title when the purpose isn’t obvious.
Avoid generic “Table 1” titles. Explain what the table is about.

3) Make headers reusable and correctly associated

Your goal: when a user moves from one cell to the next, they should always understand the meaning of the row and the column.

Ensure row/column headers are present and consistent.
For complex structures, validate that header associations work as expected.
Don’t rely on “visual headers only”. Screen readers need semantic context.

4) Add a summary when the table is complex

If the table is dense, provide a short summary that explains the axes/relationships.
Highlight what a reader should understand before exploring individual cells.
Prefer clarity over completeness: the summary should reduce confusion, not duplicate the entire table.

5) Validate with a real navigation scenario

Test with a screen reader and keyboard navigation on a representative page.
Check comprehension: can you interpret values without guessing context?
Revalidate after responsive or component changes (structure should stay coherent).

Quick checklist

The table has a caption/title that explains its purpose.
Row/column headers exist for data tables.
Header-to-cell associations are correct for complex tables.
A summary is present when the table is dense or difficult to linearize.
Layout tables are not treated as meaningful data.
You validated the experience using a screen reader.

Next step: connect your validation notes to your compliance workflow with RGAA checklist before publishing.