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
Example shows optimum level of information: image, title, and email address.
- Accommodates 3 cards in a row or 4 if there is no sidebar on desktop (see below for smaller screen sizes)
- Content padding collapses as screen size goes down but minimum padding of 24px on top and sides
- Image aspect ratio will display wide format but a square or portrait image may be uploaded
- Image is recommended. Placeholder displays if no image is uploaded.
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
Image
Provide effective alt text of the image that is concise and relevant. WCAG 1.1: Text Alternatives
- Example of alt text for Standard People Card: Portrait of Michael John Smith
- 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
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 Smith
- Example of generic text (avoid): View 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.
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.
Guidelines
Names should link to the same URL as the Call to Action if there is one.
