artifactExperience & interface

Summary List

A summary list presents related key–value facts for review, often with actions that let users change individual values.

Download Markdown (.md)

01What it means

A summary list is a structured display of terms or labels paired with their values, commonly implemented as a description list. It is suited to record details and review screens; unlike a data table, it does not primarily compare repeated rows across shared columns.[1][2]

02Why it matters

Key–value presentation makes account, case, and submission details easy to scan without forcing them into a misleading table. When paired with precise actions, it also helps users verify and amend information before a consequential step.

03When to use it

Use a summary list for related facts about one object or one completed section. Use a data table for comparison across many records, ordinary lists for unpaired items, and editable fields when the main task is direct data entry rather than review.

04How it works

  1. Group facts that describe the same object or decision and give the group a meaningful heading when needed.
  2. Write concise keys and display values in a consistent, human-readable format.
  3. Use semantic term-and-description markup so the relationships survive visual changes.
  4. Add row or group actions only when users can act on the associated information.
  5. Give repeated actions hidden or visible context, such as “Change delivery address,” rather than an ambiguous “Change.”

05A practical example

Example

Before submitting a business registration, a review page groups company details, directors, and contact information into summary lists. Each Change link includes the affected value in its accessible name and returns the user to the relevant step.

06Where it breaks

Long values and many rows can become difficult to scan, particularly on narrow screens. Summary lists are poor for comparing multiple objects and can create action-heavy layouts when every fact is independently editable.

Common mistakes

  • Using a summary list for tabular comparisons or a sequence of tasks.
  • Presenting labels and values with generic containers that lose their semantic relationship.
  • Repeating ambiguous action labels without identifying what each action changes.
  • Mixing unrelated facts in one unstructured block.

07Sources

  1. Summary listGOV.UK Design System · Institutional design systemSummary list
  2. The Description List elementMDN Web Docs · Technical documentationThe Description List element
View saved topics

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