--- title: Background Hero date: 2023-12-17T12:29:00-08:00 author: Josh Magness canonical_url: "https://designsystem.umd.edu/components/background-hero" section: Components --- # Background Hero The Background Hero tops home and landing pages. It’s a visual hero that requires high-quality photography or video. A splashy, visual option for pages with strong imagery ## Dos - Use high-resolution images (or video) that can be formatted horizontally. Ensure visible content is toward the top-middle of the image so it doesn’t get cut off by the hero gradient and text - Be mindful of the image crop. If using narrow/short content, ensure important image information is not cropped out at standard views - Add vertical spacing to dark themed hero as needed, depending on site spacing. ## Don'ts - Don't use the default hero with a dark component directly below, opt for the dark theme version instead. - Don’t use large amounts of text - Don’t use low-resolution or low-quality images or video ## Variations [View component playground: Background Hero](https://playground.designsystem.umd.edu/?path=/story/components-heroes-background-hero--standard) ## 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 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  ### 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 pathway 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:    This ensures that the link is accessible while maintaining concise visible text. ## Content Recommended character limits | Subtitle/Tagline |  20 characters (40 max) | | Title | 20 characters (40 max)* | | Text Block | 120 characters (200 max) | Recommended media sizes | Large | 1800px × 720px** | | Small | 1800px × 400px** | | Max file size | 15MB | ## Layout Height of hero and title font size are adjusted depending on usage - larger for home pages or landing pages, smaller for interior landing pages. Text may be centered or left aligned. [View Figma design: Default Hero - Anatomy](https://www.figma.com/file/YqgNlOMETaJbcI67sv8HUp/Downloadable-Components-File?type=design&node-id=147%3A25847&mode=design&t=wdHEHNGrlQYphHTA-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 Image/video and background stretch to edge of window. Image aspect ratio of component is enforced.Titles have dynamic sizing