U.S. Web Design System team 2026 U.S. Web Design System (USWDS)

Card (U.S. Web Design System)

The U.S. Web Design System’s card component page: when to use cards, when to choose something else, usability and accessibility guidance, and layout variants.

License: Public domain / CC0 — U.S. federal government work, the same basis as Icon (U.S. Web Design System) and Design Tokens (U.S. Web Design System).

Key points

  • When to use: collections of related content, such as articles or sections of a website.
  • When to consider something else:
    • tabular data: a card isn’t a substitute for a table row;
    • simple calls to action: use a button;
    • standalone content: consider an aside;
    • sequential, continuous text: cards should be self-contained and modular, so if readers are meant to go from card to card, use a list or body text with headings.
  • Usability:
    • Make cards actionable: each card summarizes more detailed information and should link out to it.
    • Don’t use the card component only for decoration or as a generic bordered box.
    • Don’t repeat images or content common to most cards in a collection, which makes cards harder to tell apart.
    • Size images to work at any card size.
    • Use simple styling, with no skeuomorphic folds, bent edges, or paper texture.
  • Accessibility: use a ul for a card group and an li for each card, so screen readers can count the items and jump between them. Set heading levels to fit the page outline. Keep the media element after the header in the markup, and use CSS rather than markup order to display it first.
  • Layout: a card group works as a wrappable grid row, with each card as a grid column. Cards in a row stretch to the same height by default.
  • Variants: flag (horizontal) layout, header-first, media on the right, and inset or “exdent” media and body elements. The component was tested against 14 WCAG 2.1 AA-based checks.

Cited In

Patterns

Created Updated