Skip to main content Red Hat Design System logo Contribute on Github

Call to action

Overview Style Guidelines Code Demos Accessibility

Keyboard interactions

Users should have the ability to navigate to and interact with calls to action using their keyboard.

Image of three groups with different variants showing focus indicators and tab key labels
Key Result
Tab Moves focus to the next call to action or interactive element
Shift+Tab Moves focus to the previous call to action or interactive element
Enter Activates a link
Enter Hides or reveals a panel below a Brick variant

Focus order

A logical focus order helps keyboard users operate our websites. Elements need to receive focus in an order that preserves meaning, therefore the focus order should make sense and not jump around randomly. For grouped calls to action, the focus order is from left to right and top to bottom.

Image of groups of three variants with numbers one through three moving from left to right and top to bottom

Touch targets

Grouped calls to action are adequately spaced for optimal touch targets.

Image of groups of variants with touch targets on top of each

Screen reader guidelines

Calls to action should communicate the following to users:

  • Their intended purpose or function
  • The toggle state when a panel is hidden or visible
  • An instruction that a panel will open

ARIA Authoring Practices Guide (APG)

Learn to use the accessibility semantics defined by the Accessible Rich Internet Application (ARIA) specification to create accessible web experiences.

View APG resources

Web Content Accessibility Guidelines

Understanding documents provide detailed explanations for Web Content Accessibility Guidelines (WCAG) guidelines and success criteria.

© 2021-2024 Red Hat, Inc. Deploys by Netlify