TAP TAP GO
Use explicit labels
Give the table a descriptive title, clear column headings and units. Avoid merged cells that make relationships difficult to follow. Keep totals and subtotals distinguishable through wording as well as colour. Explain abbreviations near the table. If a table is too wide for its viewing context, split it by meaningful sections rather than shrinking every label until it becomes unreadable.
Provide an interpretation route
Add a short sentence explaining the main comparison and the limits of the data. For complex visual information, W3C’s image guidance points toward providing the underlying information in text. A chart image should not be the only place a critical number appears. Test whether someone can explain the table’s purpose without your narration. Revise any structure that requires a long verbal rescue during a meeting.
Put the guide to work
Repeat the column headings when a table continues across pages. A reader viewing one page in isolation should still understand the numbers. Keep the scenario names and units identical so splitting the layout improves readability without introducing a new comparison problem.
Hypothetical example
A scenario table uses green and blue columns without explaining the cases. The editor adds descriptive headings, assumptions and a short reading note. Readers can compare the scenarios accurately even when the page is printed in black and white.
Make it practical.
Use this checklist as you read. Checks are not stored.References & further reading
W3C WAI — Image text alternative decision tree ↗Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
