--- title: Logo Hero date: 2023-12-17T12:29:00-08:00 author: Josh Magness canonical_url: "https://designsystem.umd.edu/components/logo-hero" section: Components --- # Logo Hero The Logo Hero displays an organization-specific logo (that is not the site logo) in order to highlight a partnership or subgroup.  A large logo presentation for prominent pages ## Dos - Use on home, landing, and interior pages - Use background color appropriate for the logo graphic (reversed logo should be on a dark background) ## Don'ts - Don’t use large amounts of text ## Variations [View component playground: Logo Hero](https://playground.designsystem.umd.edu/?path=/story/components-heroes-logo-hero--light) ## 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 **Logo** Provide effective alt text of the logo 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 **Title** Use a clear and concise title that describes the page 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) | | Text Block | 120 characters (200 max) | ## Layout The Logo Hero contains a logo. It may contain a title. Following are the minimum and maximum usage options. [View Figma design: Hero - Logo](https://www.figma.com/file/YqgNlOMETaJbcI67sv8HUp/Downloadable-Components-File?type=design&node-id=25916%3A2251&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 Aspect ratio is enforced, logo, title, text, call to action are centeredBackground color options include black (for reversed logos) and white.