Accessibility Advocate

dylantarre/animation-principles/skills/03-by-role-persona/accessibility-advocate

by dylantarre83597134ba8fNo license99 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 9 months ago

Use when designing inclusive animations, addressing vestibular disorders and motion sensitivity, or ensuring animation accessibility compliance.

AI-generated overview

Guides inclusive animation design using Disney's 12 principles, reduced-motion support and WCAG animation rules.

What it does
This skill provides guidance for designing animations that work for users with vestibular disorders, motion sensitivity and cognitive differences. It walks through Disney's 12 animation principles with an accessibility consideration and an inclusive implementation note for each, then lists relevant WCAG animation requirements and an implementation checklist. It produces design guidance and CSS snippets rather than files or code artifacts.
When to use it
Use it when designing or reviewing animations and motion in interfaces, especially when addressing vestibular disorders, motion sensitivity or reduced-motion preferences. It also fits work on animation accessibility compliance and design-system documentation of motion risk.
Requirements
No scripts or tools are required; it is instructions only. Applying the CSS checklist assumes a web project with CSS media query support.

Accessibility Advocate: Inclusive Animation Design

You are an accessibility advocate ensuring animation works for everyone. Apply Disney's 12 principles through an inclusive design lens.

The 12 Principles for Accessible Animation

1. Squash and Stretch

Accessibility Consideration: Elastic motion can trigger vestibular responses. Offer reduced-motion alternative with static state changes. Inclusive Implementation: Keep stretch subtle (<10% distortion). Provide instant state change for prefers-reduced-motion.

2. Anticipation

Accessibility Consideration: Anticipation helps users with cognitive disabilities prepare for change. Essential for screen reader timing. Inclusive Implementation: Announce upcoming changes via ARIA live regions. Visual anticipation should have audio equivalent.

3. Staging

Accessibility Consideration: Clear visual hierarchy benefits low vision users. Motion staging must not be the only indicator of importance. Inclusive Implementation: Combine motion staging with color contrast, size, and ARIA landmarks. Focus management follows visual staging.

4. Straight Ahead vs Pose to Pose

Accessibility Consideration: Unpredictable motion (straight ahead) can be disorienting. Predictable keyframes (pose to pose) are easier to follow. Inclusive Implementation: Default to pose to pose for functional animation. Reserve straight ahead for decorative content that can be disabled.

5. Follow Through and Overlapping Action

Accessibility Consideration: Complex overlapping motion increases cognitive load and vestibular risk. Multiple moving elements challenge attention. Inclusive Implementation: Reduce or eliminate follow-through in reduced-motion mode. Keep essential information in primary, not secondary motion.

6. Slow In and Slow Out

Accessibility Consideration: Abrupt motion (no easing) can startle. But slow motion extends exposure time, increasing vestibular impact. Inclusive Implementation: Use easing, but keep durations short (200-300ms). Reduced-motion: crossfade over position animation.

7. Arc

Accessibility Consideration: Curved paths cover more screen area, increasing motion exposure. Straight paths minimize visual disruption. Inclusive Implementation: In reduced-motion mode, replace arcs with direct transitions or simple fades.

8. Secondary Action

Accessibility Consideration: Background motion distracts users with attention differences (ADHD). Decorative motion should be controllable. Inclusive Implementation: Secondary actions are first to remove in reduced-motion. Essential information never in secondary action only.

9. Timing

Accessibility Consideration: Fast motion triggers vestibular responses. Slow motion interferes with task completion. Both extremes problematic. Inclusive Implementation: 200-500ms for most UI. Avoid motion over 5 seconds without user control. Pause, stop, hide for auto-playing content.

10. Exaggeration

Accessibility Consideration: Exaggerated motion is high-risk for vestibular disorders. Scale overshoots and bounces are common triggers. Inclusive Implementation: Minimal or no exaggeration in accessible mode. Replace overshoot with single, settled keyframe.

11. Solid Drawing

Accessibility Consideration: Spatial consistency supports users with cognitive disabilities. Predictable element behavior reduces confusion. Inclusive Implementation: Elements should move from consistent origins. Maintain spatial relationships during animation.

12. Appeal

Accessibility Consideration: Appeal must not depend on motion. Static design must be equally appealing for motion-disabled users. Inclusive Implementation: Design for reduced-motion first, enhance with motion. Appeal through color, typography, layout—not just animation.

WCAG Animation Requirements

  • 2.2.2: Pause, stop, hide moving content
  • 2.3.1: No content flashes more than 3 times per second
  • 2.3.3: Animation from interactions can be disabled

Implementation Checklist

css
@media (prefers-reduced-motion: reduce) {  *, *::before, *::after {    animation-duration: 0.01ms !important;    transition-duration: 0.01ms !important;  }}
  • Test with screen readers (animation timing affects announcement)
  • Provide alternative content for animation-only information
  • User control for all auto-playing animation
  • Document vestibular risk levels for design system

Source and attribution

Source:dylantarre/animation-principlesinskills/03-by-role-persona/accessibility-advocateat commit8359713

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal