Resources · 78

Data tables: preserve meaning on mobile and with screen readers

Structure units, headers, sorting and alternatives so comparisons remain usable.

· 3 min

Empty intelligence archive with dossiers and maps AI-generated editorial illustration

What this guide helps achieve

  • Define the comparison task
  • Associate headers
  • Keep context on small screens
  • Test a real decision

Quick check

  • Should every table become cards?
  • Does a blank cell mean zero?
  • Do th elements guarantee accessibility?

Step-by-step method

  1. 01

    Define the comparison task

    State the reader’s decision and limit columns to that need. Display period, unit and scope. Distinguish zero, unknown and not applicable. Make differing currencies or calculation bases explicit before readers compare rows.

    Deliverable: row and column definitions.

  2. 02

    Associate headers

    Use an actual table for tabular relationships, with a caption and header cells. In simple tables scope identifies row or column header direction. Simplify complex structures first; where complexity remains necessary, check explicit cell associations.

    Deliverable: verified structure and associations.

  3. 03

    Keep context on small screens

    Preserve relationships through horizontal scrolling or an alternative presentation. Cards should repeat useful labels without losing units. Make sorting controls accessible, announce sort state and distinguish raw numbers from formatted strings.

    Deliverable: mobile, keyboard and sorting journey.

  4. 04

    Test a real decision

    Ask readers to compare rows, locate a missing value and change sorting. Check keyboard, zoom and screen-reader use for understandable headers. CSV exports can support reuse but cannot replace accessible reading on the page.

    Deliverable: findings and repaired gaps.

Acceptance case to reproduce

Fictional example: these inputs describe no customer or observed result.

View case inputs
{
    "column_headers": [
        "2025",
        "2026"
    ],
    "row_headers": [
        "A",
        "B"
    ],
    "cell": {
        "row": "B",
        "column": "2026",
        "value": 42
    },
    "layout": "mobile"
}

Expected decision

The value 42 must remain associated with B and 2026 after adapting the table for mobile.

Fictional variations to test

A cell depends on several header levels.

Check explicit cell-to-header associations or simplify the table. Visual grouping alone is insufficient.

Sorting rows changes the context of a value.

Replay reading after each sort order. The cell must retain its row label, column and unit.

The caption is clear, but headers are missing.

Keep the caption for the overall subject and define the headers needed by cells. Test their announcement with assistive technology.

Evidence to retain

  • Sample cell with expected row, column and unit.
  • Header structure before and after sorting.
  • Assistive reading result, device and version.

Additional reference : W3C WAI — Tables with Multi-Level Headers [EN]

Verification procedure

  1. Identify row headers, column headers and units.
  2. Read a cell with keyboard and assistive technology.
  3. Keep its context after mobile adaptation and zoom. For a decisive cell, recover row, column and unit after scrolling; a readable value without its heading can change meaning.

W3C WAI — Tables tutorial

Reusable worksheet

Complete with your authorised observations. These fields are a working template, not observed results.

FieldInformation to record
MeaningTask, unit, period and missing values
StructureCaption, headers and associations
JourneyMobile, zoom, keyboard, screen reader and sorting

Worked example

Illustrative situation

Fictional example: a comparison puts monthly and yearly subscription prices into one Price column.

Decision and expected evidence

Billing periods become explicit, missing values are named and headers are tested while sorting.

Distinguish the mechanisms

MechanismPurposeCheck or limitation
TableCompare row and column relationshipsRetain headers during navigation
CardsRead one entry at a timeRepeat labels and units
ChartShow a trendProvide values and a text explanation too

Management indicators

IndicatorWhat it measuresFirst action
Interpretable valuesCells with understandable context and statusResolve ambiguity before visual embellishment
Completed tasksComparisons completed in tested journeysRecord interpretation errors

Common pitfalls

  • Retain headers during navigation
  • Repeat labels and units
  • Provide values and a text explanation too

Frequently asked questions

Should every table become cards?

No. Choose for the task; comparing rows may be easier in a well-structured table.

Does a blank cell mean zero?

No. Identify unavailable measurement, non-applicability or an observed zero explicitly.

Do th elements guarantee accessibility?

No. Check associations, comprehension, controls and zoom behavior.

Official references

References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.