Motion Guidelines Added to Major Design Systems to Support Neurodiverse Users

Design · 5 min read

Recent updates to several popular design systems standardize motion into tokenized primitives: motion.duration, motion.easing, motion.intent (emphasis/transition/feedback), and motion.sensitivity. Components consume these tokens so a single user setting can map to gentle transitions for one product and immediate changes for another, ensuring consistency without sacrificing brand motion language.

The guidance emphasizes respect for user preference signals from the OS (like prefers-reduced-motion) and provides recommended fallbacks for browsers and platforms that don't support those signals. Crucially, systems recommend strategic choices: avoid motion during critical tasks, prefer transform-based animations that are GPU-friendly, and ensure motion does not convey essential information without a non-animated alternative.

Designers and accessibility researchers contributing to the updates also published micro-patterns for onboarding, such as an in-app “preview and choose” flow that allows neurodiverse users to test motion intensity before committing to a preference. Adoption is growing because tokenized motion lets product teams offer personalization without sprawling component forks.