a11y teacher edition W3C WCAG 2.2 & WCAG 3.0 draft reference
Plain English Accessibility Hub

Translating W3C Standards for Designers, Developers, QA & Product teams

โš ๏ธ W3C Working Draft Notice

WCAG 3.0 is an active W3C Working Draft in development by the AGWG. Requirements, assertions, the conformance model and reporting tiers are still being developed and may change. The latest published draft is the 10 September 2026 Working Draft; this site follows the editorsโ€™ draft, which also includes exploratory provisions.

developing Core requirement

Bidirectional Navigation

Group: input-operation • Guideline: keyboard-interface-input

Summary in Plain English

The keyboard interface can always move on to the next interactive element and back to the previous one.

Why It Matters

One-way navigation means a mistake can only be corrected by starting the page over, which for a keyboard-only user can mean dozens of keystrokes.

Scope: When This Applies

The draft's own conditions, quoted from guidelines/groups/input-operation/keyboard-interface-input/bidirectional-navigation.md.

Notes in the draft

Although keyboard navigation is required to be bidirectional, it is not required that it be symmetrical, even though this is usually recommended practice.

Examples from the Draft

Worked examples the W3C editors wrote into the provision itself, not examples invented here.

Tabbing through menus, hitting space to open a menu, tabbing off the end of the menu lands you on the next menu. A shift+tab may go back to the last item in the previous menu (symmetrical) or to the last menu (not symmetrical but also does not fail this requirement).