artifactExperience & interface

Data Table

A data table organizes related records into rows and columns so users can scan, compare, sort, filter, and act on structured information.

Download Markdown (.md)

01What it means

A data table expresses relationships between cell values and row or column headers. A simple static table is different from an interactive grid: grids introduce application-like focus and arrow-key behavior. Sorting, selection, editing, and row actions should be added only when the task requires them.[1][2]

02Why it matters

Tables make repeated attributes comparable and support dense operational work. Clear semantics, alignment, responsive strategy, and interaction rules prevent density from becoming ambiguity or an inaccessible custom spreadsheet.

03When to use it

Use a table when users compare values across records or dimensions. Use cards, lists, or summaries when each item has irregular content or comparison is unimportant. Use a grid only for genuinely interactive, cell-oriented workflows.

04How it works

  1. Identify the comparison task and include only columns needed for recognition, decisions, or action.
  2. Provide a caption or surrounding heading and programmatically associate headers with data cells.
  3. Align and format values consistently, keeping units and missing-value meanings explicit.
  4. Add sorting, filtering, selection, and row actions with visible states and predictable keyboard behavior.
  5. Choose a responsive approach—scroll, prioritization, or alternate view—without destroying data relationships.

05A practical example

Example

A subscription dashboard lists customers by plan, renewal date, status, and recurring revenue. Currency values align by magnitude, headers control sorting and announce direction, filters persist in the URL, and horizontal scrolling preserves the account-name column at high zoom.

06Where it breaks

Wide tables are difficult on small screens and at high zoom. Excessive columns, sticky regions, virtualization, and custom grid behavior can harm performance and accessibility. Tables summarize structured values but rarely explain causes behind them.

Common mistakes

  • Using visual spacing instead of table semantics for tabular relationships.
  • Turning a simple table into an ARIA grid without needing cell-level interaction.
  • Hiding important columns on small screens with no alternative.
  • Using icons or blanks without explaining status or missing data.

07Sources

  1. Tables TutorialW3C Web Accessibility Initiative · Accessibility tutorialTables Tutorial
  2. TableGOV.UK Design System · Institutional design systemTable
View saved topics

Start typing to search titles, definitions, categories, and frameworks.