---
title: Default Section Intro
date: 2023-12-17T12:37:00-08:00
author: Josh Magness
canonical_url: "https://designsystem.umd.edu/components/default-section-intro"
section: Components
---
# Default Section Intro

The Default Section Intro gives a title and background information for other components. It is center aligned with an optional red line accent. 
The most common Section Intro. Best used with centered or full-width components.
## Dos
- Use for non-visual, short-form content that may link to deeper pages
- Use to provide a title and background information for other components such as Card Grid
## Don'ts
- Don’t use with large amounts of text, especially in headline areas
## Variations

[View component playground: Default Section Intro](https://playground.designsystem.umd.edu/?path=/story/components-section-intro-default-section-intro--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 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**
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 to the component consistently including line height, font style, weight, spacing and color of text. WCAG 1.4.12: Text Spacing

### Requirements for use

**Title**
Use a clear and concise title that describes the section content WCAG 2.4.6: Headings and Labels

**Body Text**
Write body text in clear and simple language. WCAG: 3.1.5: Reading Level 

**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:<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.

## Content

Recommended character limits
| Title | 50 characters (100 max) | 
| Text block | 150 characters (300 max) | 
## Layout

Component contains an optional text block and optional call to action. As this component is centered, it may be used with full width components as well as site content width components. Call to action may use primary or secondary link style.

[View Figma design: Section - Intro](https://www.figma.com/file/YqgNlOMETaJbcI67sv8HUp/Downloadable-Components-File?type=design&node-id=4847%3A6180&mode=design&t=aeA4SlHQ6W7nWBNq-1)