---
title: Logo Grid
date: 2023-12-17T12:31:00-08:00
author: Josh Magness
canonical_url: "https://designsystem.umd.edu/components/logo-grid"
section: Components
---
# Logo Grid

The Logo Grid organizes multiple logos into a grid area. It’s useful to display business sponsors for an event or colleges and schools in partnership. 
A collection of logos organized in a grid
## Dos
- Logos can be stacked
- Use the appropriate backgrounds for logos. If logos on white backgrounds are available, use the light background logo grid
## Don'ts
- Don’t use if descriptive text is required for a logo (an optional label is provided for a name only)
## Variations

[View component playground: Logo Grid](https://playground.designsystem.umd.edu/?path=/story/components-logo-grid-logo-grid--logos-grid&singleStory=false)

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

**Optional 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 MarylandExample 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.

## Layout

Show a maximum of 4 logos per row on a home or landing page and a maximum of 3 when width is limited by layout (interior pages). If an uneven number of logos is entered.Logo images may have an optional link.Logos/graphics should maintain size balance in relation to each other.There is no minimum or maximum for numbers of logos.

[View Figma design: Logo Grid](https://www.figma.com/file/YqgNlOMETaJbcI67sv8HUp/Downloadable-Components-File?type=design&node-id=5456%3A231&mode=design&t=NHbFuSlNhg7KQtxx-1)