Home
Bookmarks
Leagues
LEARN
Courses
Career Paths
Assessments
Tutorials
Arcade
Glossary
GROW
Certifications
Log in
Glossary
Log inSign up
Courses/Accessible Interface Foundations/Keyboard paths and visible focus/
Exercise #7

Composite Widgets: Arrow Keys vs Tab Key

In modern web applications, not every interactive item should be reached via the Tab key.

The W3C WAI-ARIA Authoring Practices Guide (APG) defines the Composite Widget Pattern:

  • Tab Key: Moves focus into and out of the widget container.
  • Arrow Keys (Left/Right/Up/Down): Navigate between items within the widget.

Examples of Composite Widgets:

  • Tab Lists (role="tablist"): Tab key focuses the active tab; Left/Right arrow keys switch between tabs.
  • Radio Groups (<fieldset> with radio buttons): Tab key enters the group; Up/Down arrow keys select options.
  • Dropdown Menus (role="menu"): Tab key exits the menu; Up/Down arrow keys move between menu items.

This pattern prevents a tablist with 15 tabs from cluttering the global tab order.

Topics

Sequential Focus Navigation & DOM Order
The Crime of 'outline: none'
The Three Tabindex Rules: 0, -1, and Never > 0
Skip Links: Bypassing Blocks (WCAG 2.4.1)
Modal Dialogues: The Sacred Focus Trap
Escape Key Dismissal: WCAG 1.4.13 & 2.1.2
Composite Widgets: Arrow Keys vs Tab Key
Single-Page App (SPA) Route Transitions
Target Size & Spacing (WCAG 2.5.5 / 2.5.8)
Master Challenge: Auditing a Broken Modal Dialogue

From lesson

2

Keyboard paths and visible focus

Level 1 · Accessible interaction basics

Top contributors

Community contribution details will appear here once real learner activity is available.

Share