---
title: Overlay Hero
date: 2023-12-17T12:29:00-08:00
author: Josh Magness
canonical_url: "https://designsystem.umd.edu/components/overlay-hero"
section: Components
---
# Overlay Hero

The Overlay Hero offers a dramatic, dynamic hero style. It uses a subtle layered angles pattern in the background.
A dynamic, dramatic style suited for pages focused on innovation and technology
## Dos
- Use high-resolution images that can be formatted horizontally
- Use on home pages
## Don'ts
- Don’t use large amounts of text
- Don’t use low-resolution or low-quality images
## Variations

[View component playground: Overlay Hero](https://playground.designsystem.umd.edu/?path=/story/components-heroes-overlay-hero--standard)

## Accessibility

### Built in accessibility

**Keyboard Accessible**
Users are able to use the keyboard to navigate through focusable content. 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. The hero overlay has an image tint overlaying the image to maintain this contrast ratio. WCAG 1.4.3: Contrast (minimum)

**Responsive Design**
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

**Hero Overlay with 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 Maryland Example 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

Font size in title can vary depending on the amount of copy needed.Recommended character limits
| Subtitle/Tagline | 16 characters (32 max) | 
| Title* | 30 characters (45 max) | 
| Text Block | 120 characters  (400 max) | 
Recommended media size
| Image/Video dimensions | 1400px × 700px** | 
| Max file size | 15MB | 
## Layout

[View Figma design: Hero - Dark Layer](https://www.figma.com/file/YqgNlOMETaJbcI67sv8HUp/Downloadable-Components-File?type=design&node-id=148%3A26756&mode=design&t=P21nxkNUofHOgeBu-1)

## Animation

The hero should support animated GIFs as an option for images or graphics. A pause button should be displayed and functional when an animated GIF is used.

## Guidelines

Background pattern and color can extend at the bottom to allow for content layeringImage or video (right) and background pattern (left) stretch to edge of windowImage aspect ratio is enforcedText lockup is aligned vertically to the bottom of the image, with 72px of padding (desktop - wide view)