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.
8 success criteria found for Operable principle 2.5 Input Modalities category
Level Level A, WCAG principle: Operable
Assigned to the following themes: GESTURES
Actions that rely on gestures (like swiping or pinching) must also be possible using a single tap, click, or button.
Level Level A, WCAG principle: Operable
Assigned to the following themes: GESTURES
Actions must not trigger on press or touch down. They must only trigger on release (like mouse-up or finger lift).
Level Level A, WCAG principle: Operable
Assigned to the following themes: CODE AND LABELS FORMS
The visible text of a button, link, or form field must also be part of its accessible (programmatic) name.
Level Level A, WCAG principle: Operable
Assigned to the following themes: GESTURES
If an action can be triggered by motion (like shaking or tilting the device), it must also:
Level Level AA, WCAG principle: Operable
Assigned to the following themes: GESTURES
Actions that require dragging (like reordering) must also be possible using buttons or another method that does not require dragging.
Level Level AA, WCAG principle: Operable
Assigned to the following themes: GESTURES
Targets must be at least 24×24px, unless they are:
Level Level AAA, WCAG principle: Operable
Assigned to the following themes: GESTURES
Targets for touch or mouse must be at least 44×44px, unless they are:
Level Level AAA, WCAG principle: Operable
Assigned to the following themes: GESTURES KEYBOARD
It must be possible to switch between input types (mouse, keyboard, touch, voice) without losing access to any functionality.