What to Look For (Everyone)

  • Is the table showing real data?
  • Does the first row label columns?
  • Would it make sense if read out loud?

Examples of “real dataâ€

  • schedules
  • comparisons
  • lists with multiple columns
  • anything where rows and columns represent relationships

NOT real data:

  • lining up text in columns
  • placing images next to paragraphs
  • spacing content
  • creating visual layouts
  • If the table is just making things look neat, it’s not real data.

That is a layout table — and layout tables should not be used.

Why This Matters

Screen readers read tables cell by cell. Without headers, data becomes confusing.

How to Fix It (Editors)

  • Use tables only for data.
  • Include header rows.
  • Avoid merged cells.
  • Do not use tables for layout.

Do / Don’t

DO

  • Keep tables simple.

¶Ù°¿±·â€™T

  • Use tables for positioning content such as text and images.

If You Must Use Merged Cells

Sometimes merged cells feel unavoidable (for example, grouping semesters or categories).

If that happens:

  • Keep merging to an absolute minimum.
  • Make sure headers still clearly describe every column.
  • Avoid merging data cells whenever possible.
  • Add explanatory text above the table to explain structure.

WCAG Reference