WCAG Explorer (beta)

Name: Kindera
Price range: $

This resource is designed for anyone eager to master digital accessibility. Explore WCAG success criteria through clear, easy-to-understand descriptions. We owe a special "hat tip" to Johannes Lehner’s WCAG Card Deck, which served as the inspiration for this project.

We plan to expand this library over time, so please check back regularly for updates.

Filters

Level

Theme

Remove filter

Keyboard

Principles

16 success criteria found for Keyboard theme

Success criterion 2.1.1 Keyboard

Level Level A, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

All functionality must be operable using a keyboard alone, unless the task requires freehand input (e.g. drawing).

Success criterion 2.1.2 No Keyboard Trap

Level Level A, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

It must always be possible to move focus into and out of any component using a keyboard alone (e.g. [tab], [shift]+[tab], [enter], [esc]), without getting stuck.

Success criterion 2.1.4 Character Key Shortcuts [2.1 and 2.2]

Level Level A, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

Keyboard shortcuts should use modifier keys like [ctrl], [cmd], or [alt/option]. If single-key shortcuts are used (e.g. 'S' for save), it must be possible to:

turn them off,
remap them with a modifier key, or
restrict them to when the relevant element is focused

Success criterion 2.4.1 Bypass Blocks

Level Level A, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

It must be possible to skip repeated blocks of content (e.g. navigation, header) and jump directly to the main part of the page.

Success criterion 2.4.3 Focus Order

Level Level A, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

Focus must follow a logical and meaningful order that preserves relationships and matches how the page is naturally read, regardless of layout or language direction.

Success criterion 3.2.1 On Focus

Level Level A, WCAG principle: Understandable

Assigned to the following themes: KEYBOARD

No unexpected changes must happen when an element receives focus (like open a popup, move focus, submit a form).

Success criterion 3.2.2 On Input

Level Level A, WCAG principle: Understandable

Assigned to the following themes: CODE AND LABELS FORMS KEYBOARD

No unexpected changes must happen when a field value changes (like auto-submit, reload, open new page).

Success criterion 4.1.2 Name, Role, Value

Level Level A, WCAG principle: Robust

Assigned to the following themes: CODE AND LABELS FORMS KEYBOARD

Interactive elements must have:

a clear name (what it is),
the correct role (what it does), and
any current value or state,

so that assistive technologies can interpret and interact with them correctly.

Success criterion 1.4.13 Content on Hover or Focus [2.1 and 2.2]

Level Level AA, WCAG principle: Perceivable

Assigned to the following themes: GESTURES KEYBOARD ZOOM AND LEGIBILITY

When additional content appears on hover or keyboard focus (including long press on touch), it must:

stay visible until dismissed or no longer valid,
be dismissible (e.g. using the [esc] key), and
remain visible when hovered or focused.

Success criterion 2.4.11 Focus Not Obscured (Minimum) [2.2 only]

Level Level AA, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

When an element receives focus, it must be at least partially visible.

Success criterion 2.4.7 Focus Visible

Level Level AA, WCAG principle: Operable

Assigned to the following themes: KEYBOARD SENSORY

A visible indicator must show which element is currently focused when navigating with a keyboard.

Success criterion 2.1.3 Keyboard (No Exception)

Level Level AAA, WCAG principle: Operable

Assigned to the following themes: KEYBOARD

All functionality must be operable using a keyboard alone (no exception, not even for tasks involving gestures like drag-and-drop or pointer-based interaction).