--- title: Standard Pathway date: 2023-12-17T12:33:00-08:00 author: Zaida Jocson canonical_url: "https://designsystem.umd.edu/components/standard-pathway" section: Components --- # Standard Pathway The Standard Pathway is a visually interesting way to section content on a page and link to deeper content. It offers an equal balance of text and a visual. This component features an option for statistics. Showcases important content and can lead users to deeper pages in a site. An option featuring statistics is available ## Dos - Use to feature content in a visual way - Alternate between left and right image options - Use to provide context to statistics - When using multiple on the same page, keep the image aspect rations similar ## Don'ts - Don’t use with large amounts of text (3+ paragraphs) - Don’t use with low-resolution or low-quality images - Don't use upload different image sizes when being used i groups ## Variations [View component playground: Standard Pathway](https://playground.designsystem.umd.edu/?path=/story/components-pathways-standard-pathway--left-image) ## 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 If the text area is significantly off balance on desktop, consider using the Sticky Image version of the pathway. Recommended character limits | Subtitle/Tagline | 20 characters (40 max) | | Title | 40 characters (80 max) | | Text Block | 350 characters (700 max) | | Stat | 3 characters (5 max) | | Caption or Credit | 20 characters (30 max) | Recommended image dimensions | Image | 800px × 700px* | ## Layout Standard version can stack and have images on the left or right. There is a dark and light version with an optional pattern background. Title and text block are optional, but one of the two is required. For a similar layout to use with events, see Event Pathway. [View Figma design: Standard Pathway](https://www.figma.com/design/YqgNlOMETaJbcI67sv8HUp/Downloadable-Components-File?node-id=50988-31619&t=5t8ACjg3RXDhYhZm-1) ## Animation The pathway 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.