Card (VA.gov Design System)
The U.S. Department of Veterans Affairs’ VA.gov Design System card component: a flexible container for short, related pieces of personalized information, with guidance on when to use it, alternatives, calls to action, variants, and things that look like cards but aren’t.
License: Public domain — U.S. federal government work (17 U.S.C. § 105), the same basis as Autosave (VA.gov Design System) and Form Confirmation and Keep a Record of Submitted Information (VA.gov Design System). Inferred from VA.gov being an executive-branch federal agency site; the page carries no explicit public-domain statement.
Key points
- Purpose: a snapshot of information in one digestible chunk, with the option to navigate to more detail. People should be able to scan a sequence of cards and act on the most relevant ones.
- When to use: in collections of identical or similar, uniformly styled items, and to frame a specific call to action or decision.
- When to consider something else:
- a structured status card (Card - Status);
- enrolled benefits or tools (Service list item);
- a single highlight of the page’s most important information (Summary box, used once and never stacked);
- content inserted in response to a user action (an Alert);
- a section of a form: a card is not a fieldset, and a fieldset shouldn’t look like one;
- large data: a card is not a table row;
- navigation: a card is not a button or link, and shouldn’t be used as a large tap target.
- Search results: use with caution. With low data density, drop the card container and use rows. With high density, add pagination, search, and filters.
- Calls to action:
- Make cards actionable.
- Use an action link for a task (“Continue your application”), in its secondary variation within a collection and its primary variation only for the page’s main call to action.
- Use an active link for more detail, a default link for supporting information, and a download link for files.
- Use the same link style for the same action across a collection, with no more than 3 calls to action per card.
- Variants: default (white), with background (gray, no longer preferred), with drop shadow (for emphasis at the top of a page or section, or as the primary card in a series, and not mixed with the gray variant), and with icon (to tell card types apart, e.g. in-person vs. remote appointments).
- Not a card: link containers used as large mobile tap targets, list-and-loop form containers, and radio or checkbox tiles look like cards but follow their own components’ rules.
- Content: keep headers and text short enough to read at a glance. Avoid dynamic content in the middle of a sentence so the card can be translated.
- Accessibility: set the heading level to fit the page outline, mark up a group as a
ulwith anliper card, and let Tab move focus to the call to action within the card.