Why a hint at all
A 3D model often looks like a picture. Many visitors do not realise they can turn it, or do not know how to zoom. A hint closes that gap – as long as it stays small.
A hint, not a tutorial
The Nielsen Norman Group concludes that tutorials interrupt users, do not necessarily improve task performance and are quickly forgotten; contextual help avoids these pitfalls but needs unintrusive ways to activate it [1]. For a configurator that means no multi-page introduction, just one sentence on the model.
Rules for good hints
| Rule | In practice |
|---|---|
| Short | one sentence, one verb: "Drag to rotate" |
| In place | directly over the 3D area, not at the top of the page |
| Self-dismissing | on the first rotation or after a few seconds |
| Device-aware | "drag" works for mouse and finger; the zoom hint matches the device |
| Calm | no looping animation; motion is dropped under reduced motion |
Under WCAG, moving content that starts automatically and lasts more than five seconds needs a way to pause, stop or hide it [2]. A calm, non-animated hint that disappears after a few seconds avoids the issue altogether.
Example from the library
The chemical store example shows "Drag to rotate · "Load" starts the forklift". The hint disappears on the first rotation or after seven seconds. Example configurator, fictional product.
What a hint cannot fix
If users still fail, the problem usually lies deeper: controls that are too small, a model that blocks page scrolling (see scroll trapping), or no alternative to the gesture (see touch gestures).