Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
dylantarre avatar

Accessibility Advocate

  • 348 installs
  • 68 repo stars
  • Updated December 30, 2025
  • dylantarre/animation-principles

Champion reduced-motion, focus order, and perceptual safety when designing or reviewing animated interfaces for inclusive web and mobile products.

About

Accessibility-advocate equips agents to argue for and enforce inclusive animation choices, including reduced motion, safe timing, readable focus behavior, and WCAG-aligned interaction patterns during UI review.

  • Reduced-motion compliance
  • Focus and timing audits
  • Perceptual safety checks
  • Inclusive motion rationale
  • Stakeholder accessibility arguments

Accessibility Advocate by the numbers

  • 348 all-time installs (skills.sh)
  • Ranked #732 of 1,880 Design & UI/UX 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 accessibility-advocate

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs348
repo stars68
Last updatedDecember 30, 2025
Repositorydylantarre/animation-principles

What it does

Champion reduced-motion, focus order, and perceptual safety when designing or reviewing animated interfaces for inclusive web and mobile products.

Files

SKILL.mdMarkdownGitHub ↗

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

@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

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.