Card

Anatomy

1. Card Container: This rectangular container is the fundamental part of this component. It is styled with Canvas Tokens to ensure the background color, corner radius, depth, and outline stroke are coherent as a basis with cards within workday. This can be used as the basis for creating more tailored card types.
2. Title (Optional): The title explained
3. Paragraph (Optional): The Paragraph explained

Usage Guidance

• Cards hold a variety of content types, such as a combination of text, icons, imagery and actions related to a single topic.
• Check out the Card Framework Figma library created for the UI Platform framework for design guidance on how to layout and style your cards.
• Cards should be easy to digest, providing relevant information and available actions.
• Text and visual elements should be placed in a way that clearly indicates hierarchy.
• Cards should be placed inside a layout grid to help with alignment and sizing.
• Most cards are created and maintained by specific product teams. The Canvas card is a generic container which you can leverage when creating new cards. Check out the Canvas Kit card container to see what’s available in Canvas now.
• Need to create your own custom card for your product? Check out our Customizing Canvas section for guidance on creating new components in keeping with Canvas.

When to Use

• Use Cards when you need to group information in a digestible form.
• Use Cards when you need to offer a short entry point that is linked to more detailed content or a complex task.
• Use Cards to lay out single or multiple sets of related information in the same region of the page. Cards may include an image, a text summary, pills, and actions. Cards typically have similar widths, but heights should accommodate varying content.

When to Use Something Else

• When you need to show unrelated content types or actions in a single container.
• When you need to show content in multiple columns.
• When you need to display content in a table format.

Examples

Basic Example

Card includes a container Card component and the following subcomponents: Card.Body and Card.Heading.

Depth

Card extends from Box so it supports all of Box's style props. This includes depth, which changes the Card's perceived "height" above the page surface by adjusting its box shadow. Card has a default depth of 1.

Here's an example of a Card with a increased depth of 2.

Padding

Set the padding prop of the Card (again, supported via Box) to adjust its padding. Card has a default padding of l.

Here's an example of a Card with a reduced padding of xs.

Component API

<Card role="dialog" aria-labelledby="card-heading">
  <Card.Heading id="card-heading">Card Title</Card.Heading>
  <Card.Body>Card Contents</Card.Body>
</Card>

Accessibility Guidelines

Keyboard Interaction

Any interactive elements in the Card must have a focus indicator that is highly visible against the background and against the non-focused state. Refer to Accessible Colors for more information.

Cards must support the following keyboard interactions:

• Tab: Focuses interactive elements included in the card (e.g. buttons, links, inputs, selects, etc.)

Screen Reader Interaction

Cards must communicate the following to users:

• The title (heading) of a Card represents the beginning of the content in a card.
• Calls to action in a Card are uniquely distinguishable from other cards on the screen.

Design Annotations Needed

• Decide heading level for the Card title in context of the page. Read more about meaningful page structure for more information.
• Write accessible name for icon-only button variants. Read more about non-text content.
• Write unique accessible names for generic call to action buttons.
• Write text alternatives for images and illustrations, unless they are for decorative purposes only.

Implementation Markup Needed

• Cards must begin with a heading element <h2> - <h6>.
• When using multiple cards together in a group, use <ul> and <li> elements to build card containers as list items in an unordered list.
• An aria-label string is required for icon-only buttons and accessible tooltips can show the icon's name for everyone.
• Images, illustrations, and icons that may be considered decorative or redundant can be hidden from screen readers by setting a null alt=”” attribute for <img> elements.
• [Included in component] Decorative <svg> icons are hidden from assistive technology with role=”presentation” and focusable=”false”.

Content Guidelines

• When writing content for Cards, refer to our Content Style Guide