Cards are containers for displaying relevant and actionable information on a single topic. A card serves as a single, contained unit and is independent of surrounding content. It cannot be nested within cards and cannot divide into multiple cards.
Some quick example text to build on the card title and make up the bulk of the card's content.
- You need to group information in a digestible form.
- You need to offer a short entry point that is linked to more detailed content or a complex task.
- Lay out single or multiple sets of related information in the same region of the page. Cards may include an image, a text summary, chips, and actions. Cards typically have similar widths, but heights should accommodate varying content.
Don’t use when
- You need to show unrelated content types or actions in a single container.
- You need to show content in multiple columns.
- You need to display content in a table format.
- Grouping a large set of related information.
A Card may contain any of the following elements (with the minimum of one), but they are all optional:
- Card Container (with 1px border, 2px radius, 16px padding, and hover state with Level 3 shadow ) required
- Image (top of card, no padding) optional
- Title optional
- Subtitle optional
- Card Text optional
- Button optional
- Chips optional
- Lists optional
- Card dimensions are based on its content and the container in which it resides.
- Apply custom heights and width to meet product requirements.
|Do keep cards consistent for easy scanning.||Don't organize content in different ways when grouped together.|
- Cards should only contain a single action, which is tied to a UI component within the action element or to the whole card (using a card as a link).
- Keep labels one to three words long, if possible, to avoid wrapping.
- Keep titles one to five words long, if possible, to avoid wrapping. Use title case and capitalize prepositions of four letters or more.
- Use full sentences with punctuation, no longer than 40 words if possible.
- Do not include multiple paragraphs.
- Keep metadata one to five words long to avoid wrapping.
- Cards should use an underlying
articleelement to maintain usability for some screen reader users.
- Make sure all interactive elements within cards are part of a tab sequence.
- Avoid keyboard traps when adding components to cards. For example, the user focuses on an element within a card, but is unable to tab to the next focusable element.
- Although the card element passes accessibility testing, content authors need to ensure the content within the card is accessible. For example, if you add an image to the card you need to include alternative text to pass accessibility testing.
|11/23/2020||1.0.0||Shadow depth identified for hover state. Padding adjusted to fit the grid.||E. Bohn, E. Gunther, L. Cook|