guideline: Input Modalities
Support input methods beyond a keyboard and mouse.
2.5.1 Pointer Gestures
Actions that rely on gestures (like swiping or pinching) must also be possible using a single tap, click, or button.
2.5.2 Pointer Cancellation
Actions must not trigger on press or touch down. They must only trigger on release (like mouse-up or finger lift).
2.5.3 Label in Name
The visible text of a button, link, or form field must also be part of its accessible (programmatic) name.
2.5.4 Motion Actuation
If an action can be triggered by motion (like shaking or tilting the device), it must also work without motion, and be possible to turn off motion-based input.
2.5.5 Target Size (Enhanced)
Targets for touch or mouse must be at least 44×44px, unless they are part of a sentence or block of text, near another target with the same function that meets the size, or in a context where size can’t be increased.
2.5.6 Concurrent Input Mechanisms
It must be possible to switch between input types (mouse, keyboard, touch, voice) without losing access to any functionality.
2.5.7 Dragging Movements
Actions that require dragging (like reordering) must also be possible using buttons or another method that does not require dragging.
2.5.8 Target Size (Minimum)
Targets must be at least 24×24px, unless they are part of a sentence or block of text, surrounded by enough space, or near another target with the same function that meets the size.
