Accessibility Advocate logo

Accessibility Advocate

Community
dylantarre
accessibility-advocate

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

Overview

Publisherdylantarre
Repositoryanimation-principles
Skill nameaccessibility-advocate
Stars
84
Forks
12
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by dylantarre on GitHub. Read the source before you install it.

Installation

Install the Accessibility Advocate AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/dylantarre/animation-principles.git /tmp/animation-principles
mkdir -p .claude/skills
cp -r /tmp/animation-principles/skills/03-by-role-persona/accessibility-advocate .claude/skills/accessibility-advocate
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Accessibility Advocate in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Accessibility Advocate on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Accessibility Advocate is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Frequently asked questions

What does the Accessibility Advocate AI skill do?

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

Why use Accessibility Advocate on TypingMind?

Because you install it once and use it with any model. Accessibility Advocate is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Accessibility Advocate in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dylantarre/animation-principles/tree/main/skills/03-by-role-persona/accessibility-advocate. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Accessibility Advocate?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Accessibility Advocate?

As many as you like. As long as a model supports skills, you can use Accessibility Advocate with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Accessibility Advocate AI skill free?

Yes. It is published on GitHub by dylantarre under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇