reduced-motion-accessibility

Enforce reduced-motion fallbacks and validate with browser/runtime evidence.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill reduced-motion-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reduced-motion-accessibility
Source: https://github.com/vTRKA/supervibe/tree/main/skills/reduced-motion-accessibility
Command: npx skills add https://github.com/vTRKA/supervibe --skill reduced-motion-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduced Motion Accessibility prevents motion-heavy UI and media from triggering vestibular risk, hiding essential state, or failing accessibility expectations when users enable reduced-motion preferences.

Core Features & Use Cases

  • Motion risk classification & decisioning: Identifies vestibular triggers (scroll effects, parallax, large transforms, autoplay loops) and selects safe reduced-motion equivalents rather than just slowing animations.
  • Runtime-focused proof and fallbacks: Requires browser/runtime evidence for motion/media surfaces (video, Lottie/Rive, Canvas/WebGL) including console/network health, state availability, and cleanup.
  • WCAG mapping and anti-slop gating: Produces a structured anti-slop report with evidence-backed gate IDs so approvals and handoffs are blocked when proof is missing.

Quick Start

Ask your AI tool to review your target page or prototype for reduced-motion behavior, generate the required evidence plan, and return a PASS/PARTIAL/BLOCKED result with missing runtime proof called out.

Frequently Asked Questions about reduced-motion-accessibility

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify reduced motion accessibility for animated UI and media?

Verify reduced motion accessibility by enforcing correct fallbacks and validating them with browser runtime evidence. This requires a motion inventory, scoped reduced-motion equivalents, and testing with preference on/off to satisfy proof contracts.

What is the best way to handle vestibular safety for scrolling effects and autoplaying media?

Handle vestibular safety by classifying motion risks like scroll effects and autoplay loops, then selecting safe reduced-motion equivalents rather than simply slowing animations. This prevents triggering vestibular issues when users enable reduced-motion preferences.

Can I use runtime verification to prove WCAG mapping for Lottie, Rive, Canvas, and WebGL visuals?

Yes, runtime verification proves WCAG mapping for Lottie, Rive, Canvas, and WebGL by requiring browser evidence including console and network health. This ensures state availability and proper cleanup across advanced visual surfaces.

How do I generate an anti-slop gating report for product UI transitions?

Generate an anti-slop gating report for product UI transitions by mapping motion risks to structured, evidence-backed gate IDs. This blocks approvals and handoffs when runtime proof is missing, returning a PASS, PARTIAL, or BLOCKED result.

Does route change animation require scoped reduced-motion fallbacks during accessibility review?

Yes, route change animations require scoped reduced-motion fallbacks during accessibility review. Identifying vestibular triggers and selecting safe equivalents across review, implementation, and handoff workflows ensures compliance with accessibility expectations.