Skip to main content Home
About About the Design SystemRoadmap
Get started OverviewDesignersDevelopers
Foundations OverviewColorGridIconographyInteractionsSpacingTypography
Tokens Overview Global colorbox shadowTypographyborderopacityspacelengthIconBreakpointsMedia Queries
Elements All elements Accordion Alert Announcement Audio player Avatar Back to top Badge Blockquote Breadcrumb Button Card Chip Code block Call to action Dialog Disclosure Footer Health index Icon Jump links Navigation (primary) Navigation (secondary) Pagination PopoverPlanned Progress stepsPlanned Site status Skip link Spinner Statistic Subnavigation Surface Switch Table Tabs Tag Tile Timestamp Tooltip Video embed
Theming OverviewColor PalettesCustomizingDevelopers
Patterns All PatternsCardTabsFilterFormLinkLink with iconLogo wallSearch barSkip navigationSticky bannerSticky cardTileVideo thumbnail
Personalization All Personalization PatternsAnnouncement
Accessibility FundamentalsAccessibility toolsAssistive technologiesCI/CDContentContributorsDesignDevelopmentManual testingResourcesScreen readers
Design/code status Release notes Get support

Jump links

OverviewStyleGuidelinesCodeAccessibilityDemos
ImplementationKeyboard interactionsFocus orderTouch targetsARIA Authoring Practices Guide (APG)Web Content Accessibility GuidelinesImplementationKeyboard interactionsFocus orderTouch targetsARIA Authoring Practices Guide (APG)Web Content Accessibility Guidelines

Implementation

  • Provide a unique and descriptive accessible name to the jump links element
  • Ensure each jump link has descriptive text that says what section a user will jump to if they select it

To make jump links responsive, they must be composed inside of a disclosure for mobile viewports.

  • Provide a unique and descriptive accessible name to the disclosure if it is expandable
    • If the disclosure uses an icon as its trigger, be sure to provide an accessible name for the icon
  • Ensure the disclosure has an aria-expanded attribute that matches its expanded state
    • If users implement <rh-disclosure> or a <details>/<summary> element, aria-expanded is not necessary

Keyboard interactions

Each individual jump link can be navigated with a keyboard. However, focus moving to a jump link does not mean it has been selected.

Four sets of jump links. Each jump link shows a blue focus ring around each link with arrows pointing in the appropriate focus order direction.
Key Result
Tab
  • Moves focus to the top jump or the next jump link
  • Focus can move to the disclosure trigger button
  • Focus can move outside to an interactive element
Shift+Tab
  • Moves focus to the previous jump or the first jump link
  • Focus can move to the disclosure trigger button
  • Focus can move outside to an interactive element
Enter
  • Scrolls the user to their desired section
  • Expands or collapses a parent nested jump link

Focus order

Focus moves through jump links first and then other elements from top to bottom or left to right.

Five jump links with content on the right. Focus moves 1-5 through the five jump links then move into the content on the right.

Touch targets

Each individual jump link and the disclosure trigger button are large enough to be selected easily.

Four sets of jump links with semitransparent red dots overtop of each jump link representing the centermost touch target of each link.

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.

Edit this page on GitHub
© 2021-2025 Red Hat, Inc. Deploys by Netlify