Card
Cards are flexible-size container that display content and actions on a single topic. They can display featured information, related content, or navigational choices.
On this page
Use Cases
User should be able to:
- Focus on all buttons (the main button and the nested actions icon button)
- View clear label and instructions
- Navigate and interact with the component
- Should be able to receive appropriate feedback based on input type documented under interactive style
Interaction and Style
Relevant WCAG Requirements
Info and Relationships
Ensure information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. This means use proper HTML elements to structure your content, so it makes sense when read by assistive technology.
WCAG 2.1 Understanding 1.3.1Keyboard
Ensure all functionality of the content is operable through a keyboard interface. This allows users who can't use a mouse or touchscreen to navigate and use your content.
WCAG 2.1 Understanding 2.1.1Name, Role, Value
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
WCAG 2.1 Understanding 4.1.2
Keyboard Navigation
| Key | Action |
|---|---|
| Tab | Focuses actionable elements inside the card. |
| Enter/Spacebar | Activates focused actionable element. |
Questions?
Connect with the DLS Team on Slack or by email.
Resources
Check out additional resources.