---
title: Person Card
date: 2023-12-17T12:34:00-08:00
author: Josh Magness
canonical_url: "https://designsystem.umd.edu/components/standard-people-card"
section: Components
---
# Person Card

The Person Card displays contact information for an individual. 
Shows contact information for a single person. Use in multiples for a group of people.
## Dos
- Name and title required
- Use abbreviations for titles or department information if content becomes crowded
- Use in multiples for a group of people
## Variations

[View component playground: Person Card](https://playground.designsystem.umd.edu/?path=/story/components-people-and-experts-person-card--vertical-light&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:**
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. WCAG 1.1: Text AlternativesExample of alt text for Standard People Card: Portrait of Michael John SmithDo 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

**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): View profile of Michael John SmithExample of generic text (avoid): View 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

List and card options are available depending on display needs. Card allows you to include a photo, name, job title, department name, pronouns, phone number, email address, and link to a detailed profile or bio page. Contact table versions are more limited, but may still include job titles and other information as well as contact information.

[View Figma design: Card - People](https://www.figma.com/file/YqgNlOMETaJbcI67sv8HUp/Downloadable-Components-File?type=design&node-id=171%3A52176&mode=design&t=Qxa1kHugTmM46Uy8-1)

## Guidelines

Names should link to the same URL as the Call to Action if there is one.