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

The Split Hero is an image-text split that provides ample space for messaging and imagery and allows for white space.
A large display of balanced text and imagery 
## Dos
- Use high-quality images or video in a square format
- Use on home and high-level landing pages
## Don'ts
- Don’t use large amounts of text
- Don’t use low-resolution or low-quality images
## Variations

[View component playground: Split Hero](https://playground.designsystem.umd.edu/?path=/story/components-heroes-split-hero--right-image)

## 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**
Actionable items 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 

### 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 page 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 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.

## Content

Recommended character limits
| Subtitle/Tagline | 15 characters (40 max) | 
| Title | 25 characters (50 max) | 
| Text Block | 120 characters  (400 max) | 
Recommended media size
| Image/Video dimensions | 1100px × 800px** | 
| Maximum file size | 15MB | 
## Layout

[View Figma design: Hero - Split Image](https://www.figma.com/design/YqgNlOMETaJbcI67sv8HUp/Downloadable-Components-File?node-id=53342-5551&t=ICgG0lAjrKp3b0aN-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

This hero may use a primary or secondary Call to Action style.