accessible-motion — Claude Code skill: motion that won't trigger
This skill swaps harmful animations for safe alternatives and covers the WCAG motion criteria. Useful when your UI has parallax, zoom or infinite loops.
npx skills add dylantarre/animation-principles --skill accessible-motion -a claude-codeWhat accessible-motion does
The skill takes Disney's 12 animation principles and rewrites each one for accessibility. Squash & Stretch becomes an opacity or color change, Anticipation becomes a static loading indicator, Follow Through gets dropped. Inside you get a mapping table, ready CSS and JavaScript snippets for prefers-reduced-motion, and lists of safe versus harmful motion patterns.
A separate section covers WCAG 2.1 criteria 2.3.3 (AAA), 2.2.2 (A) and 2.3.1 (A). There's a ten-item checklist and a testing order: turn on reduced motion in OS settings, confirm every feature still works, then test with a screen reader.
The skill advises against the 150–400 ms range because that speed is fast enough to notice and slow enough to trigger symptoms. Pick either instant state changes (0 ms) or a gentle transition of 500 ms and up. If your project already has autoplaying background video or infinite animations, that's where to look first.
What it helps with
- replace parallax and zoom with safe transitions
- add
prefers-reduced-motionsupport in CSS and JavaScript - meet WCAG 2.3.3, 2.2.2 and 2.3.1
- remove infinite and flashing animations
- verify the UI against OS motion settings
Example prompts for the agent
- Audit the animations on this page and replace harmful ones with safe alternatives
- Add
prefers-reduced-motionsupport for modals and toggles - Build an accessible motion checklist for this component
How to install accessible-motion
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill accessible-motion -a claude-code2Manually: put the files in place
~/.claude/skills/accessible-motion/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/accessible-motion/
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill accessible-motion -a codex2Manually: put the files in place
.agents/skills/accessible-motion/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill accessible-motion -a cursor2Manually: put the files in place
.cursor/skills/accessible-motion/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dylantarre/animation-principles accessible-motion2Manually: put the files in place
.github/skills/accessible-motion/SKILL.md1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill accessible-motion -a gemini-cli2Platform CLI
gemini skills install https://github.com/dylantarre/animation-principles --path skills/01-by-domain/accessible-motionManually: put the files in place
.devin/skills/accessible-motion/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill accessible-motion -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about accessible-motion
How do I install accessible-motion in Claude?
Run npx skills add dylantarre/animation-principles --skill accessible-motion -a claude-code. The skill lands at ~/.claude/skills/accessible-motion/SKILL.md.
What does accessible-motion do?
It rewrites Disney's 12 animation principles for accessibility and ships ready snippets for prefers-reduced-motion. It also walks through the WCAG motion criteria.
Which animations does the skill flag as harmful?
Parallax, background movement, zoom, spinning, fast repeated animations and moving areas larger than a quarter of the viewport. Autoplaying video and infinite loops are on the always-avoid list.
Source text
SKILL.md · MIT
---
name: accessible-motion
description: Use when implementing reduced motion alternatives, vestibular-safe animations, WCAG compliance, or designing for users with motion sensitivity.
---
# 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
```css
/* 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
```javascript
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-motion` respected 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
© dylantarre · MIT · dylantarre/animation-principles