---
title: Grid Hero
date: 2025-09-10T11:51:00-07:00
author: Jiayu Kang
canonical_url: "https://designsystem.umd.edu/components/grid-hero"
section: Components
---
# Grid Hero

An image-led, interactive, and compelling page header. It requires one featured image or video plus eight supporting images.
An image-led, interactive, and compelling page header. 
## Dos
- Use high-resolution landscape-style images (or video) for featured image area
- Use only when you have 8 additional images 
- Balance images by content. Don&#039;t put all images with faces at the top right and images with buildings at the bottom right
- Be mindful of the orientation of images and match to orientation in the layout
## Don'ts
- Don’t use low-resolution or low-quality images
- Don’t use large amounts of text
## Variations

[View component playground: Grid Hero](https://playground.designsystem.umd.edu/?path=/story/components-heroes-animation-grid--dark-theme)

## Accessibility

### Built in accessibility

**Keyboard Accessible**
Users are able to use the keyboard to navigate through focusable content 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**
The 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 consistently including line height, font style, weight, spacing and color of text. WCAG 1.4.12: Text Spacing 

**Video**
A pause button is added for users when a video is used. WCAG 2.2.2: Pause, Stop, Hide

### Requirements for use

**Image**
Provide effective alt text of the image that is concise and relevant. Avoid phrases like “image of” since screen readers often already announce the type of element. WCAG 1.1: Text AlternativesDo not use an image to present text. True text should be used whenever possible, as it supports translation, is searchable, and is easier to maintain and customize. WCAG 1.4.5: Images of Text

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

**Body Text**
Write body text in clear and simple language. WCAG: 3.1.5: Reading Level Use descriptive link text for inline-links. WCAG 2.4.4: Link Purpose (In Context) 

**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.

**Video**
If you are using a video, ensure that it does not flash more than 3 times per second. Avoid large, flashing images that are bright with significant contrast between flashes. WCAG 2.3: Seizures and Physical Reactions

## Content

Recommended character limits
| Title* | 40 characters (80 max) | 
| Text Block | 200 characters (400 max) | 
Recommended media dimensions
| Featured Image/Video Dimensions | 1980px × 1080px | 
| Additional Image Dimensions | 854px × 480px | 
| Max File Size | 15MB | 
## Layout

[View Figma design: Grid Hero - Anatomy](https://www.figma.com/design/YqgNlOMETaJbcI67sv8HUp/Downloadable-Components-File?node-id=100490-6116&t=t5B65o7AbtkVDM9f-1)

## Guidelines

Always test image dimensions and display order on both desktop and mobile devices, as layout and scaling may change across breakpoints.The 8 additional images will be uploaded column by column. Start with the left column from top to bottom, then the middle column from top to bottom, and finally the right.

