accessibility-advocate

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

181 stars

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

$curl -o ~/.claude/skills/accessibility-advocate/SKILL.md --create-dirs "https://raw.githubusercontent.com/majiayu000/claude-skill-registry/main/skills/data/accessibility-advocate/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/accessibility-advocate/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How accessibility-advocate Compares

Feature / Agentaccessibility-advocateStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/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 system

Related Skills

accessibility

181
from majiayu000/claude-skill-registry

Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast".

accessibility-wcag

181
from majiayu000/claude-skill-registry

Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities.

accessibility-validation

181
from majiayu000/claude-skill-registry

Validate digital outputs for compliance with accessibility standards (e.g., WCAG, Section 508). Use when reviewing reports, dashboards, documents, or interfaces from pilot projects to identify and remediate accessibility barriers.

accessibility-ux-audit

181
from majiayu000/claude-skill-registry

Audit and enhance accessibility and UX across all pages and components.

accessibility-testing

181
from majiayu000/claude-skill-registry

WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.

accessibility-tester

181
from majiayu000/claude-skill-registry

Expert accessibility tester specializing in WCAG compliance, inclusive design, and universal access. Masters screen reader compatibility, keyboard navigation, and assistive technology integration with focus on creating barrier-free digital experiences.

accessibility-test-axe

181
from majiayu000/claude-skill-registry

Эксперт по a11y тестированию. Используй для axe-core, automated testing и accessibility audits.

accessibility-standards

181
from majiayu000/claude-skill-registry

Implement WCAG 2.1 accessibility standards for Vue 3 apps. Use when adding ARIA labels, keyboard navigation, screen reader support, or checking color contrast. Mentions "accessibility", "ARIA", "keyboard nav", "screen reader", or "color contrast".

accessibility-rules

181
from majiayu000/claude-skill-registry

Concise accessibility checklist and practices for components in the repository. Use when implementing UI to ensure keyboard, screen reader, and focus semantics.

accessibility-review

181
from majiayu000/claude-skill-registry

Reviews UI for accessibility issues against WCAG 2.1/2.2 AA. Triggers on "is this accessible?", "check accessibility", or contrast/a11y review requests.

accessibility-report

181
from majiayu000/claude-skill-registry

Generate accessibility compliance reports including VPAT and ACR documents

accessibility-remediation

181
from majiayu000/claude-skill-registry

Use this skill when the user writes/edits components, asks to "fix accessibility issues", "add ARIA labels", "improve accessibility", "check WCAG compliance", "remediate a11y violations", mentions "screen reader support", "keyboard navigation", or wants AI-powered accessibility fixes with one-click application. Automatically analyzes components for a11y issues and suggests context-aware fixes. Trigger on PostToolUse hook or explicit request.