Event Card

Users are able to use the keyboard to navigate through the event card using the ‘Tab’ key to navigate/focus and ‘Enter’ or ‘Spacebar’ to activate and focus can be moved away from the component. WCAG 2.1.1: Keyboard; WCAG 2.1.2: No Keyboard Trap This navigation is done in sequential and logical order when there are multiple call to actions grouped together. WCAG 2.4.3: Focus Order

Each actionable element within the event card has distinct styling on hover and focus. This provides a visual cue to the user that the element is focused and an action can be taken. 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 event card is responsive, adapting to various screen sizes to prevent content truncation and ensures proper reflow when zoomed up to 200% without horizontal scrolling WCAG 1.4.10: Reflow

Provide effective alt text of the image that is concise and relevant. If the image is linked, the alt text should be succinct and descriptive of both the image and the linked content. Avoid phrases like “image of” since screen readers often already announce the type of element. WCAG 1.1: Text Alternatives

• 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

Use a clear and concise title that describes the card content content WCAG 2.4.6: Headings and Labels

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) 

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.