
Accessible Motion
- 379 installs
- 68 repo stars
- Updated December 30, 2025
- dylantarre/animation-principles
accessible-motion is a Claude Code UI animation skill that implements vestibular-safe, WCAG-compliant motion with prefers-reduced-motion support for developers building React, Vue, or plain CSS interfaces.
About
accessible-motion is a frontend animation skill from dylantarre/animation-principles that applies Disney's 12 animation principles while ensuring accessibility for users with vestibular disorders, motion sensitivity, and cognitive disabilities. The skill maps each principle to accessible implementations—opacity and color changes instead of squash and stretch, state indication without motion-based anticipation, focus management for staging, and instant state changes where motion would trigger discomfort. Developers reach for accessible-motion when implementing reduced-motion alternatives, vestibular-safe transitions, or WCAG-compliant timing and pause controls in React, Vue, or plain CSS applications before shipping animated UI components.
- Maps motion to prefers-reduced-motion and safe alternatives
- Covers vestibular-risk patterns like parallax and large zoom
- Aligns duration, looping, and pause behavior with WCAG guidance
- Pairs semantic HTML and focus management with animated UI
- Documents test checks for keyboard and screen-reader regressions
Accessible Motion by the numbers
- 379 all-time installs (skills.sh)
- Ranked #671 of 2,245 Frontend Development skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/dylantarre/animation-principles --skill accessible-motionAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 379 |
|---|---|
| repo stars | ★ 68 |
| Last updated | December 30, 2025 |
| Repository | dylantarre/animation-principles ↗ |
How do you build accessible UI animations?
Implement UI motion that respects prefers-reduced-motion, avoids vestibular triggers, and meets WCAG timing and pause requirements in React, Vue, or plain CSS apps.
Who is it for?
Frontend developers adding motion to React, Vue, or CSS apps who must satisfy WCAG timing, pause controls, and prefers-reduced-motion requirements.
Skip if: Teams building animation-heavy games, marketing video motion graphics, or backends without any UI animation requirements.
When should I use this skill?
A developer implements UI animations and needs reduced-motion alternatives, vestibular-safe transitions, or WCAG motion compliance.
What you get
WCAG-compliant motion variants, prefers-reduced-motion CSS rules, and vestibular-safe component animation code.
- prefers-reduced-motion CSS rules
- accessible animation component code
- WCAG motion compliance checklist
By the numbers
- Maps Disney's 12 animation principles to accessible UI implementations
Files
Accessible Motion Design
Apply Disney's 12 animation principles while ensuring accessibility for users with vestibular disorders, motion sensitivity, and cognitive disabilities.
Quick Reference
| Principle | Accessible Implementation |
|---|---|
| Squash & Stretch | Opacity/color change instead |
| Anticipation | State change indication without motion |
| Staging | Focus management, not motion-based |
| Straight Ahead / Pose to Pose | Instant state changes |
| Follow Through / Overlapping | Eliminated or minimal fade |
| Slow In / Slow Out | Instant or very gentle ease |
| Arc | Straight or no movement |
| Secondary Action | Reduced or eliminated |
| Timing | Instant (0ms) or extended duration |
| Exaggeration | Removed entirely |
| Solid Drawing | Static visual clarity |
| Appeal | Clarity over personality |
Core Principle
Animation should enhance understanding, never hinder it. When motion causes harm, provide alternatives that maintain functionality.
Respecting User Preferences
CSS Media Query
/* Default: Full animation */
.element {
transition: transform 300ms ease-out;
}
/* Reduced motion preference */
@media (prefers-reduced-motion: reduce) {
.element {
transition: opacity 200ms ease-out;
/* Or no transition at all */
transition: none;
}
}JavaScript Detection
const prefersReducedMotion = window.matchMedia(
'(prefers-reduced-motion: reduce)'
).matches;
if (prefersReducedMotion) {
// Use instant transitions or subtle fades
} else {
// Use full animations
}Principle Adaptations
Squash & Stretch → Replace with opacity or color changes. A button can darken on press instead of compressing. Loading indicators can pulse opacity instead of bouncing.
Anticipation → Use static indicators. Show a loading state immediately rather than animated preparation. Hover states change color instantly rather than scaling.
Staging → Use focus management and visual hierarchy. Scroll to content rather than animated reveals. Static highlighting over motion-based attention.
Motion Types → Instant state changes replace transitions. Toggle switches snap position. Modals appear instantly. Menus show without animation.
Follow Through → Eliminated. Elements reach final state immediately. No settling, bouncing, or overshoot effects.
Easing → Either instant (0ms) or very gentle, extended duration (500ms+) with minimal distance. If using motion, slow and subtle.
Arc/Paths → Straight movement only if any movement. Prefer opacity transitions over positional. No circular or complex motion paths.
Secondary Action → Significantly reduced or eliminated. Single, clear feedback per interaction. No cascading or staggered animations.
Timing → Two approaches: instant (0ms) for snappy feedback, or extended (500ms+) for gentle perception. Avoid 150-400ms range—fast enough to notice, slow enough to trigger symptoms.
Exaggeration → Removed entirely. Literal, proportional visual feedback only. No overshoots, bounces, or dramatic effects.
Solid Drawing → Maintain visual clarity in static states. Design must work without any animation. Strong contrast and clear hierarchy.
Appeal → Appeal through clarity, not personality. Clean, predictable interactions. User confidence in interface stability.
Safe Motion Patterns
Generally Safe
- Opacity fades (keep subtle)
- Color transitions
- Small scale changes (<5%)
- Very slow movement (500ms+)
- Non-repeating animations
Potentially Harmful
- Parallax scrolling
- Background movement
- Zoom animations
- Spinning/rotating elements
- Fast repeated animations
- Large moving areas (>1/4 viewport)
Always Avoid
- Auto-playing video backgrounds
- Infinite animations
- Vestibular-triggering patterns
- Flashing (seizure risk)
- Rapid zoom in/out
WCAG Guidelines
WCAG 2.1 Success Criteria
2.3.3 Animation from Interactions (AAA) Motion triggered by interaction can be disabled unless essential.
2.2.2 Pause, Stop, Hide (A) Moving content lasting >5 seconds must be pausable.
2.3.1 Three Flashes (A) No content flashes more than 3 times per second.
Implementation Checklist
- [ ]
prefers-reduced-motionrespected globally - [ ] All animations have reduced/no-motion alternative
- [ ] No auto-playing motion over 5 seconds
- [ ] User can pause/stop any animation
- [ ] No content flashes more than 3x/second
- [ ] Essential functionality works without animation
- [ ] Focus states clear without motion
- [ ] Loading states work without animation
- [ ] Error states visible without motion
- [ ] Form validation static-friendly
Testing
1. Enable reduced motion in OS settings 2. Verify all functionality works 3. Check all states are clearly communicated 4. Ensure no motion remains that should be reduced 5. Test with screen reader users 6. Validate with vestibular disorder users if possible
Related skills
How it compares
Choose accessible-motion over generic animation libraries when WCAG motion compliance and prefers-reduced-motion fallbacks are required alongside polished UI transitions.
FAQ
What frameworks does accessible-motion support?
accessible-motion supports React, Vue, and plain CSS applications, providing accessible motion patterns and prefers-reduced-motion fallbacks for each stack.
How does accessible-motion handle Disney animation principles?
accessible-motion maps all 12 Disney animation principles to accessible alternatives such as opacity changes instead of squash-stretch and focus-based staging instead of motion hierarchy.