Accordion

Users can navigate through focusable content using the ‘Tab’ key to navigate/focus and ‘Enter’ or ‘Spacebar’ key can activate and toggle accordion panels, and focus can move away from the component as needed. WCAG 2.1.1: Keyboard; WCAG 2.1.2: No Keyboard Trap This navigation is done in sequential and logical order. Clickable elements within opened accordions integrate into the tab order automatically. WCAG 2.4.3: Focus Order

Screen readers announce the state changes (expanded/collapsed) of the accordion panels, informing users of content visibility changes WCAG 4.1.2: Name, Role, Value

The headline link and call to action link have distinctive styling for both hover and focus states, providing visual cues that the element is interactive. WCAG 1.4.13: Content on hover or focus

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)

 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

Because the title of each accordion panel serves effectively as the label for the accordion button, this title should clearly describe the content that will be revealed when the accordion is expanded. By doing so, the title acts as an accessible name WCAG 4.1.2: Name, Role Value which is announced by screen readers, helping users understand the function of the accordion button and the nature of the content it controls. The title should be concise yet descriptive enough to guide users through navigation and interaction. WCAG 2.4.6: Headings and Labels

Write body text in clear and simple language. Avoid jargon, idioms, or complex language structures. WCAG: 3.1.5: Reading Level Use descriptive link text for any inline links within the accordion. The link text should clearly indicate the destination or action. WCAG 2.4.4: Link Purpose (In Context)

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