Published September 1, 2026.
Tables can make comparisons easier, but only when readers can understand them on the device they use. This review checks meaning, layout, and interaction before a data-heavy article is released.
Confirm a table is appropriate
Use a table for relationships across repeated fields, not merely to decorate a list. Give columns concise, descriptive headers and keep each cell focused on one comparable idea.
Test narrow layouts
Inspect the rendered page at common mobile widths and with increased text size. Content must not become clipped or overlap. If horizontal scrolling is necessary, keep it within the table region and preserve a clear reading order.
| Check | Question | | --- | --- | | Headers | Can each cell be related to a heading? | | Width | Is all content reachable without page-level overflow? | | Contrast | Are borders and text distinguishable? | | Keyboard | Can interactive content be reached and understood? | | Alternative | Does surrounding prose explain the conclusion? |
Review the article around it
Introduce what the table compares and summarize the decision it supports. Do not require visual pattern recognition as the only way to understand a critical point.
Use the rendered-page QA routine for the full release and consult the W3C’s table concepts guidance.
Frequently asked questions
Should every table become cards on mobile?
No. Cards can obscure column relationships. Choose the pattern that preserves the information structure and test it with real content.
Are screenshots acceptable substitutes?
Not for essential tabular information. Semantic text remains searchable, selectable, adaptable, and more accessible.
