Where it comes from
3D viewers use the mouse wheel to zoom and swipes to rotate. To do so they call preventDefault() on wheel or touch events so the page does not scroll as well. MDN notes that registering the listener with passive: true may cause the browser to generate non-cancelable wheel events [1]. On touch devices, the CSS property touch-action controls which movements the browser handles itself [2]. With none, every swipe over the model belongs to the model.
Patterns that help
| Pattern | How | Trade-off |
|---|---|---|
| Zoom with a modifier | the wheel scrolls the page; zoom with Ctrl/Cmd or buttons | needs a hint |
| Click to activate | the model reacts only after a click or tap | one extra step |
| Release vertical swipes | touch-action: pan-y: vertical scrolls the page, horizontal turns the model | swipe rotates only about the vertical axis |
| Leave margins | model not full-screen, scroll area beside it | less room for the model |
| Full screen on request | small preview, full screen via a button | extra step |
overscroll-behavior stops a scroll area from dragging the page behind it once it hits its end (scroll chaining), but MDN notes that an iframe is not a scroll container [3]. For embedded configurators the behaviour must be solved inside the iframe itself.
The keyboard too
The same problem exists with the keyboard: WCAG 2.1.2 requires that focus moved into a component with the keyboard can also be moved away with the keyboard; if that takes more than arrow or Tab keys, the method must be explained [4]. A 3D area that uses arrow keys to rotate must not hold on to focus.
How to test
Scroll the page from top to bottom on a real phone without deliberately touching the model. Can you get past it without a detour? Then it is solved. See also door, gate and window configurator implementation on phones and loading.