The usual gestures
| Gesture | Effect in a 3D viewer |
|---|---|
| One-finger drag | rotate the model |
| Two-finger pinch | zoom |
| Two-finger drag | pan (often disabled) |
| Tap | select a part, open a door, show info |
| Double tap | often: reset or zoom in |
What WCAG asks for
- 2.5.1 Pointer Gestures (Level A): anything that uses multipoint or path-based gestures must also work with a single pointer without a path-based gesture, unless the gesture is essential [1]. For zoom that means plus and minus buttons as well.
- 2.5.7 Dragging Movements (Level AA): functions that use dragging need a single-pointer alternative without dragging [2]. For rotation, view buttons work well (front, side, top).
- 2.5.8 Target Size (Minimum) (Level AA): controls should be at least 24 × 24 CSS pixels or have enough spacing [4].
The technical side
The CSS property touch-action sets which touch movements the browser handles itself, such as scrolling or zooming the page [3]. For the 3D area this is a trade-off: if it claims every gesture, the page can no longer be scrolled over it, see scroll trapping.
Example from the library
In the washroom cubicle example we checked touch rotation and pinch zoom in emulated tests across several screen sizes; every control is at least 44 pixels. Example configurator, fictional product.
Tips
- Show the gestures once with an onboarding hint.
- Limit rotation and zoom so nobody ends up under the floor or inside the model.
- Offer a visible "reset view" button.