The auto-rotating product, the camera that swoops in on load, the parts that animate into place: they demo beautifully and they make a real slice of your users feel ill. Vestibular disorders are common, and the browser already tells you who is affected. Most 3D sites never ask.
The one query
const reduce = window.matchMedia('(prefers-reduced-motion: reduce)')
The user set this at the OS level. It is not a guess about them, it is a stated preference. In a configurator, honoring it means:
-
No auto-rotate. Turn off
controls.autoRotate. Let them spin the model themselves, when they choose. - No camera fly-in. Cut to the framed view instead of animating to it.
- Calmer transitions. Swap option changes instantly or with a short fade instead of parts sliding across the scene.
if (reduce.matches) {
controls.autoRotate = false
camera.position.copy(finalCameraPos) // no tween
settings.animateOptionChanges = false
}
React to changes, do not just read once
People toggle the setting, and some toggle it specifically because your page is making them queasy. Listen, do not only read at load:
reduce.addEventListener('change', (e) => applyMotionPreference(e.matches))
The product still works
The point is not to strip the configurator. It is to keep the function, choose, see, price, and drop the motion that is decoration. The user who needs reduced motion still gets to configure the product, just without the scene moving on its own. That is the whole bar, and clearing it is a few lines.
I learned to build this in after watching demos that looked impressive to me and uncomfortable to the person I was showing them to. Now it is a default on everything the studio ships, configurators included.
I am Dominik Groński / GroDev, a studio in Poznan, Poland building custom 3D configurators and Laravel back-ends for manufacturers.
Top comments (1)
Good point that reduced motion doesn't mean removing the configurator, just the motion nobody asked for.
One detail I'd add: user-driven rotation isn't always calm either. With OrbitControls and damping on, a quick drag keeps the model spinning for a while after the person lets go, which can feel a lot like auto-rotate. Under
reduceI'd either turnenableDampingoff or raise the damping factor so it settles fast.And the UI around the canvas usually has its own transitions (option panels sliding, price ticking up), so a matching
@media (prefers-reduced-motion: reduce)block in the CSS is worth doing at the same time, otherwise the scene is calm and everything next to it is still moving.