Skip to content
Dev Ring Technologies
Let’s talk
Back to blog

Data tables: prepare clear reading on mobile

A table can look tidy on a computer and become difficult to understand on a phone: a column disappears, a unit is missing, or a value can no longer be linked to its header. This method helps you prepare the content with your team and check the result. It concerns data tables; it is neither a complete accessibility audit nor a description of a client project.

1. Start with the comparison the reader needs

In our fictional example, a training centre publishes its workshops: name, day, duration and location. The question is straightforward: which workshop takes place on Thursday, and where? Write two or three questions like this before designing the table. Keep an approved source against which to check the answers, without including unnecessary personal data.

W3C distinguishes data tables from tables used for layout. A real data table expresses relationships between rows and columns; visual alignment alone does not convey those relationships to assistive technology. If you are presenting only three independent steps, a list may be more suitable. Choose the format according to the intended reading task.

Source : W3C WAI — Tables Concepts

2. Give values context before styling them

Prepare a precise title, short labels and the necessary units. In our example, “Duration (minutes)” is more useful than “Number”. Define what empty cells mean too: information not provided, not applicable, or a zero value. Do not replace missing information with zero without the content owner’s approval.

An associated caption helps identify a table; a description of its structure can help when it is complex. W3C presents these as useful according to need, without saying they are mandatory in every WCAG case. In your handover, specify the title, period covered and reading notes separately so the team can place them appropriately.

Source : W3C WAI — Caption & Summary

3. Make headers explicit and simplify groupings

Ask the team to distinguish header cells from data cells in the HTML. For a simple table with two axes, W3C shows th headers with scope="col" or scope="row". Bold text does not replace this association. Choose a value in the middle of the table and check which row and column it belongs to.

Multi-level tables may need explicit associations using id and headers. Before retaining merged cells and repeated groupings, ask whether several simpler tables would support the same comparisons. Hand over the groupings that are actually needed; the right solution depends on the data structure, rather than just the number of columns.

Source : W3C WAI — Tables with Two Headers · Source : W3C WAI — Tables with Multi-Level Headers

4. Keep the table readable on a small screen

Presentation may change on mobile, but relationships between headers and values must remain available. If the table becomes a set of cards, every value needs its label and context. If horizontal scrolling is chosen, check that the last column can be reached, nothing is clipped, and the reader understands how to continue.

The WCAG Reflow criterion provides an exception for parts whose meaning requires two dimensions, including some data tables. This does not exempt cell content from reflow or justify making the whole page overflow. Check a narrow width and enlargement with the team; avoid shrinking all text merely to fit the table.

Source : W3C WAI — Tables: Tips and Tricks · Source : W3C — Understanding SC 1.4.10: Reflow

5. Repeat a question using different reading methods

Repeat the original question on a computer and then a phone. In our example, find the location of Thursday’s workshop and check its duration against the approved source. Read the first and last rows too. If the table contains links or controls, check keyboard access without sending a form or changing real data.

Then have someone familiar with a screen reader check the associations. Record the browser, tool and headers announced around a selected cell. The Tab key alone does not test table relationships: ordinary text cells do not all need to become tab stops. A visual screenshot does not prove these associations either.

Source : W3C WAI APG — Table Pattern

6. Validate languages and hand over usable evidence

Compare each translation against the same source: labels, units, dates and notes. In Arabic, check right-to-left reading order as well as numbers and Latin terms in context. Changing language must not attach a value to a different workshop. Repeat the original question instead of checking only that words have been translated.

For each discrepancy, retain the address, language, version, device, affected cell, expected result and observation. After correction, repeat the question on that new version and retain the remaining limitations. This focused acceptance check helps assess a delivery; it does not certify the whole website’s compliance or measure an SEO result.

Data table acceptance worksheet

Data table acceptance worksheet
CheckResult to observeEvidence to keep
Useful questionAn achievable comparisonQuestion and approved answer
ContextClear units and empty-cell meaningsSource and reading rule
HeadersValue linked to the correct row and columnCell and checked associations
Small screenEvery value remains accessibleWidth and reading journey
Assisted readingRelevant headers announcedBrowser, tool and observation
TranslationsSame answer in every languageVersion and remaining discrepancies

Frequently asked questions

Can the table be replaced with an image?

An image alone does not provide the structural relationships of an HTML table. For published data that readers need to compare, provide a structured, readable version; an illustration can accompany it without becoming the only way to access the values.

Should columns be removed on a phone?

Start with the reader’s question. If a column is needed to answer it, it must remain accessible with its label. A more compact presentation or several tables can be considered without silently removing useful information.

Is an automated check enough?

It can help identify certain technical problems. It does not decide whether units are correct, an empty cell is ambiguous, or the requested comparison remains understandable. Keep a human check of the content and the relevant reading methods.

Prepare your next table

Choose an existing table, write a specific question and prepare an approved source. Have the same answer checked on a computer, on a phone and in the published languages, then record discrepancies before accepting delivery.

Sources and scope

Primary W3C guides consulted on November 6, 2026. The tutorials and Understanding document explain practices and criteria; they do not replace a complete evaluation. The training centre, questions and worksheet are fictional editorial suggestions. No client result or certification is claimed.