accessibility-advocate
Use when designing inclusive animations, addressing vestibular disorders and motion sensitivity, or ensuring animation accessibility compliance.
Best use case
accessibility-advocate is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when designing inclusive animations, addressing vestibular disorders and motion sensitivity, or ensuring animation accessibility compliance.
Teams using accessibility-advocate should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/accessibility-advocate/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How accessibility-advocate Compares
| Feature / Agent | accessibility-advocate | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when designing inclusive animations, addressing vestibular disorders and motion sensitivity, or ensuring animation accessibility compliance.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 systemRelated Skills
App Accessibility
Your approach to handling app accessibility. Use this skill when working on files where app accessibility comes into play.
accessibility-testing
Guide for conducting comprehensive accessibility audits of code to identify WCAG compliance issues and barriers to inclusive design. This skill should be used when reviewing accessibility, ARIA implementation, keyboard navigation, or screen reader compatibility.
accessibility
Quality assurance for web accessibility and usability, particularly for users with disabilities. Use when involved in any web project.
accessibility-ux-audit
Audit and enhance accessibility and UX across all pages and components.
accessibility-rules
Concise accessibility checklist and practices for components in the repository. Use when implementing UI to ensure keyboard, screen reader, and focus semantics.
accessibility-planning
Plan accessibility compliance - WCAG 2.2, Section 508, EN 301 549, inclusive design principles, audit planning, and remediation strategies.
accessibility-design
WCAG 2.1 AA compliance patterns, screen reader compatibility, keyboard navigation, and ARIA best practices. Use when implementing accessible interfaces, reviewing UI components, or auditing accessibility compliance. Covers semantic HTML, focus management, color contrast, and assistive technology testing.
accessibility-design-checklist
Эксперт по accessibility дизайну. Используй для WCAG, a11y чеклистов и inclusive design.
accessibility-design-checker
Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.
accessibility-contrast-audit
[Design System] Quantitative accessibility audit for UI - contrast ratios, font sizes, tap targets, heading hierarchy. Use when (1) checking WCAG color contrast compliance, (2) auditing text sizes for readability, (3) validating touch/click target sizes, (4) reviewing heading structure and landmarks, (5) user asks to 'check accessibility', 'audit contrast', 'WCAG compliance', or 'a11y check'.
accessibility-compliance
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
accessibility-by-default
Treats accessibility as a baseline requirement, not a feature. WCAG 2.1/2.2 AA principles embedded into every decision.