Glossary · Usability & UX

Touch gestures in a 3D viewer

In short

Touch gestures are the finger movements used to work a 3D model on phones and tablets: drag with one finger to rotate, pinch with two to zoom, tap to select. Every gesture should also have a simple alternative.

The usual gestures

GestureEffect in a 3D viewer
One-finger dragrotate the model
Two-finger pinchzoom
Two-finger dragpan (often disabled)
Tapselect a part, open a door, show info
Double tapoften: 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.

Related terms

  • Orbit controls (camera controls)

    Orbit controls are the usual camera controls in a 3D viewer: the camera circles a target point, zooms in and out and pans sideways while "up" stays up.

  • Scroll trapping

    Scroll trapping happens when an embedded 3D model captures mouse-wheel or swipe movements for zoom and rotation, so the page can no longer be scrolled over it. On phones, where the model fills the screen, users get stuck.

  • Onboarding hint

    An onboarding hint is a short overlay that shows, on the first visit, how to use a 3D model – for example "drag to rotate". Good hints are brief, sit where the action happens and disappear as soon as the user acts.

  • Target size (touch target)

    Target size is the clickable or tappable area of a control. WCAG 2.5.8 (Level AA) requires at least 24 × 24 CSS pixels or enough spacing from neighbouring targets. For swatches and plus/minus buttons in a configurator, more room is kinder.

  • WCAG (Web Content Accessibility Guidelines)

    WCAG (Web Content Accessibility Guidelines) are the W3C guidelines for accessible web content. The current version, WCAG 2.2, is published as the W3C Recommendation of 12 December 2024 and assigns its success criteria to levels A, AA and AAA.

Examples to try

Example configurator · fictional product

Washroom cubicle & locker configurator

Plan a washroom or changing room: cubicle row, end cubicle, duct wall, urinals and vanity, or locker banks with benches – with a plan view, a clearance check and a PDF enquiry.

Partitions, guarding & shelving · Dimensions and sizes · Colours · Materials and finishes

Example configurator · fictional product

Canopy & shade structure configurator

Plan a canopy for a school, walkway, entrance or play area: choose the roof type, size, bays, roofing and colour – then move the sun and see how much shade it casts, and when.

Canopies, shelters & street furniture · Dimensions and sizes · Colours · Materials and finishes

More in our guides

Sources

  1. W3C: Understanding Success Criterion 2.5.1 Pointer Gestures
  2. W3C: Understanding Success Criterion 2.5.7 Dragging Movements
  3. MDN Web Docs: touch-action
  4. W3C: Understanding Success Criterion 2.5.8 Target Size (Minimum)

← All terms in the glossary