---
title: Statistics Cards
date: 2023-12-17T12:39:00-08:00
author: Josh Magness
canonical_url: "https://designsystem.umd.edu/components/stat-cards"
section: Components
---
# Statistics Cards

Statistics Cards are a large, visual way to showcase numerical facts. They tend to be grouped together for thematic storytelling. 
A large, visual way to show statistics
## Dos
- Use in groups of 2 or more
## Don'ts
- Don’t use with long amounts of text in the statistic or text description
## Variations

[View component playground: Statistics Cards](https://playground.designsystem.umd.edu/?path=/story/components-stats-stat-cards--default)

## Accessibility

### Built in accessibility

**Keyboard Accessible**
Users are able to use the keyboard to navigate through focusable content including a linked image, headline with a link, and call to action link, using the ‘Tab’ key to navigate/focus and ‘Enter’ or ‘Spacebar’ to activate.WCAG 2.1.1: Keyboard This navigation is done in sequential and logical order. WCAG 2.4.3: Focus Order

**Hover and Focus State**
Actionable items each have distinctive styling on hover/focus to provide a visual cue to the user that the element is focused and there is an action that can be taken. WCAG 1.4.13: Content on hover or focus

**Color Contrast**
A contrast ratio of at least 4:5:1 between text and background color is ensured to enhance readability WCAG 1.4.3: Contrast (minimum)

**Responsive**
The component scales in relation to the to the screen size to prevent truncating content and reflows properly when zoomed up to 200% without horizontal scrolling WCAG 1.4.10: Reflow

**Consistent**
Styles are applied to the card consistently including line height, font style, weight, spacing and color of text. The heights of cards are maintained consistently when cards are grouped together in a row. This provides balance and allows for greater readability. WCAG 1.4.12: Text Spacing 

### Requirements for use

**Title**
Use a clear and concise title that describes the card content WCAG 2.4.6: Headings and Labels

**Link**
Use effective text to describe what the link is and where it is taking the user. This should be clear, descriptive text that conveys the link content succinctly and the purpose and destination of the link. WCAG 2.4.9: Link Purpose (Link Only)Example of effective text (preferred): Learn more about Innovate MarylandExample of generic text (avoid): Learn moreDisclaimer: If the visible link text is not sufficiently descriptive, you can use an aria-label attribute to provide additional context for screen reader users. The aria-label should clearly describe the link's purpose and destination.If the visible text is not necessary for screen readers (e.g., it's redundant or less descriptive), consider using aria-hidden="true" on the visible text element. This ensures that screen readers will prioritize the aria-label.Example with aria-label and aria-hidden:<a href="https://example.com/innovate-maryland" aria-label="Learn more about Innovate Maryland"> 
  <span aria-hidden="true">Learn more</span> 
</a> This ensures that the link is accessible while maintaining concise visible text.

## Content

Recommended character limits
| Statistic | 3 characters (4 max)* | 
| Subtext  | 80 characters (160 max) | 
| Source  | 60 characters (120 max) | 
## Layout

[View Figma design: Card - Stat](https://www.figma.com/design/YqgNlOMETaJbcI67sv8HUp/Downloadable-Components-File?node-id=190-71547&t=gn85RMgBCcgyXxfU-1)