Reduced Motion

Reduced Motion Overview

Reduced Motion is a building block you will reach for often in design systems. It keeps related logic together and makes your intent obvious to reviewers and future maintainers.

When you learn reduced motion properly, you avoid the guesswork that leads to bugs and rework. The example below shows the shape you will use in most real design systems projects.

<button
  type="button"
  aria-expanded="false"
  aria-controls="menu"
>
  Options
</button>
<ul id="menu" role="menu" hidden>
  <li role="menuitem" tabindex="-1">Edit</li>
</ul>

Accessible components pair correct roles and ARIA state with full keyboard support.

Reduced Motion Example

/* Tokens flow into components, which flow into products */
:root { --color-brand-500: #2563eb; }
.button { background: var(--color-brand-500); }

• Start from a minimal Reduced Motion example and grow it only as needed.
• Keep configuration explicit so Reduced Motion behaves the same in every environment.
• Name things clearly so teammates understand your Reduced Motion at a glance.
• Add tests around Reduced Motion early to lock in expected behaviour.

Design System Cheatsheet

Quick reference for reduced motion within a modern design system.

How Reduced Motion Fits into a Design System

Reduced Motion connects the design decisions in your system to the code teams actually ship. When it is defined once and reused, products stay consistent and updates roll out everywhere.

Accessible components pair correct roles and ARIA state with full keyboard support.

• Define it once as a token or shared component.
• Document intended usage with clear examples.
• Make it themeable and accessible by default.
• Version and release changes so consumers can upgrade safely.

Getting Teams to Adopt Reduced Motion

Adoption is where design systems succeed or stall. Make reduced motion the easiest option: great docs, sensible defaults, and clear migration paths beat mandates every time.

Common Mistakes

• Copying reduced motion snippets without understanding what each line does.
• Skipping error handling and edge cases when wiring up reduced motion.
• Leaving reduced motion untested, so regressions slip into production.
• Over-engineering reduced motion before you actually need the extra flexibility.

Key Takeaways

• Reduced Motion is a core part of working effectively with design systems.
• Start small and keep reduced motion focused on a single responsibility.
• Apply consistent patterns so reduced motion scales across your project.
• Test and document reduced motion to keep it maintainable over time.