Skip to main content
UMDDesign System

Heroes

Stacked Hero

The Stacked Hero is a dynamic, messaging-focused page topper. An image is optional.

Facts and Rankings headline, greek text, Learn more button stacked over photo of students in front of red stairway

Variations

Home page
The home page option uses larger title text and an image that goes edge to edge on the browser window.

Landing page

The landing page option contains a simple text stack and image that fits within the site content width.

Open in a new window

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

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 more

Disclaimer: 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.

Title

Use a clear and concise title that describes the pathway content WCAG 2.4.6: Headings and Labels

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 Alternatives

  • Do 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

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)

Tagline

20 characters (40 max)

Layout

The Stacked Hero at minimum contains a title, with an optional wide image.

Guidelines

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