smithery/dylantarre

accessibility-issues

Use when animation excludes users with vestibular disorders, cognitive disabilities, or assistive technology needs

Installation

$ npx skills add smithery/dylantarre --skill accessibility-issues

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/dylantarre · top by installs.

npx skills add smithery/dylantarre

Browse all from smithery/dylantarre

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,409 B
  • docs SUMMARY.md 142 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Accessibility Issues

Make animations inclusive using Disney's principles thoughtfully.

Problem Indicators

  • Motion sickness complaints
  • Vestibular disorder triggers
  • Screen reader confusion
  • Cognitive overload
  • Seizure risk (flashing)
  • Keyboard focus lost during animation

Diagnosis by Principle

Squash and Stretch

Issue: Excessive distortion causes disorientation Fix: Reduce or eliminate squash/stretch for users with prefers-reduced-motion. Use opacity changes instead.

Secondary Action

Issue: Too many moving elements Fix: Limit to one animated element at a time. Secondary actions should be subtle or removed.

Exaggeration

Issue: Dramatic motion triggers vestibular responses Fix: Reduce scale, rotation, and position changes. Keep movements small and predictable.

Timing

Issue: Animations too fast or too slow Fix: Provide consistent, predictable timing. Avoid sudden speed changes.

Arcs

Issue: Curved motion paths cause tracking difficulty Fix: Use linear motion for essential UI. Save arcs for optional decorative elements.

Quick Fixes

  1. Respect prefers-reduced-motion - Always check and honor
  2. No autoplay animation - Let users trigger motion
  3. Keep focus visible - Never animate focus indicator away
  4. Announce changes - Use ARIA live regions for dynamic content
  5. Provide pause controls - For any looping animation

Troubleshooting Checklist

  • Does animation respect prefers-reduced-motion?
  • Is there a way to pause/stop animations?
  • Are state changes announced to screen readers?
  • Does keyboard focus remain visible and logical?
  • Is flash rate under 3 per second?
  • Can users complete tasks without animation?
  • Are animations triggered by user action (not autoplay)?
  • Test with screen reader enabled

Code Pattern

@media (prefers-reduced-motion: reduce) {
  *,
  *::before,
  *::after {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
  }
}
// Check preference in JS
const prefersReducedMotion = window.matchMedia(
  '(prefers-reduced-motion: reduce)'
).matches;