Protocol

Keep the headers attached when the table leaves your screen

Bold text is not a relationship.

About 1 min read

Before you use it

Use when
  • A table is readable visually but confusing with assistive technology or after export.

Keep this limit in mind

  • Complex tables may need a simpler alternative. A correct source document does not guarantee that an export preserves its structure.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Identify the row and column headers that give each value its meaning. Represent those associations semantically in the chosen format, and check the exported result separately. Keep complex headings only when the task genuinely needs them.

Steps

  1. Name what a reader must know to interpret a data cell.
  2. Use appropriate header associations and a useful table description or caption.
  3. Inspect representative cells in the delivered format, including cells under grouped headings.

An example

A status table must preserve both the business unit and reporting period for each value, not merely bold the top row.

Check your result

Can a non-visual reader recover the relevant headers while moving through the table?

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingKeep the headers attached when the table leaves your screen

Evidence and sources
Supports

WAI table guidance uses semantic header and data-cell relationships so table structure is available beyond visual presentation.

Complex tables and exports need format-specific verification; bold text is not a semantic header.

Tables Tutorial · Table structure and header associations.

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details