Interface Core C · Industry convention

Card

A card is a clearly bounded group that shows one subject, its details, and related actions.

Try an example
You might call it content cardtile

Try an example

Card
Pattern 04

Card

A card is a clearly bounded group that shows one subject, its details, and related actions.

A real example

A project card shows a picture, title, update time, owner, and more-actions menu.

Main parts

  1. 01Trigger or task context
  2. 02Primary control surface
  3. 03Feedback, focus, and dismissal

Use it when

Use cards when each item must be easy to scan or reorder.

Do not use it when

Never put every section in a floating box when those sections do not need grouping.

Name used in code

<article> / Card

Before you ship

Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.

Request you can copy

Outcome: Use Card to solve this user need without losing the current context. User context: A project card shows a picture, title, update time, owner, and more-actions menu. Recommended pattern: Card. Why it fits: Use cards when each item must be easy to scan or reorder. Do not use it when: Never put every section in a floating box when those sections do not need grouping. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.

Check this request

Review the current use of Card. Definition: A card is a clearly bounded group that shows one subject, its details, and related actions. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

C
How official is this term?

Industry convention

People often use this term at work. The listed sources may support practice or limitations. They do not define every part of the term.

No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks.

Scope
Design-system component convention
Document status
stable
Checked on
2026-07-30

Evidence sources & scope

Authority source · Google · stable Material Design Components Scope: Material component vocabulary Role here: Helpful background, not a definition Source covers: canonical name, definition, interaction, keyboard behavior, accessibility

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.