qa-detect-reduced-motion

Detect CSS animations and transitions lacking prefers-reduced-motion media query coverage.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-reduced-motion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-detect-reduced-motion
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-detect-reduced-motion
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-reduced-motion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps catch accessibility defects where animations and transitions ignore users who prefer reduced motion, preventing motion sickness and improving compliance with WCAG 2.3.3.

Core Features & Use Cases

  • Reduced-motion detection: Scans stylesheets for animation and transition rules that should be gated by user motion preferences.
  • Accessibility compliance review: Flags pages that animate without any prefers-reduced-motion support.
  • Use case: A product team shipping a marketing site with parallax effects can use this Skill to verify that motion-sensitive users are protected before release.

Quick Start

Use the qa-detect-reduced-motion skill to inspect the current page for animations or transitions that are not properly wrapped in reduced-motion media queries.

Frequently Asked Questions about qa-detect-reduced-motion

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

FAQPage Schema
How do I check my CSS for missing prefers-reduced-motion support?

To check CSS for missing prefers-reduced-motion support, scan stylesheets for animation and transition rules that are not gated by the media query. This detects motion effects that ignore user preferences and violate accessibility expectations.

What animations violate WCAG 2.3.3 reduced motion requirements?

Animations violate WCAG 2.3.3 reduced motion requirements when they play without being wrapped in a prefers-reduced-motion media query. This includes parallax effects, autoplay UI, and CSS transitions that lack motion preference gating.

How do I audit a component library for reduced-motion accessibility issues?

Auditing a component library for reduced-motion accessibility requires inspecting frontend stylesheets for animation and transition patterns. The process flags any motion effects or autoplay-driven UI that lacks prefers-reduced-motion media query coverage.

Can I detect parallax and autoplay UI that ignore reduced-motion preferences?

You can detect parallax and autoplay UI that ignores reduced-motion preferences by scanning web pages for animation and transition rules. The review flags motion effects that are not properly wrapped in reduced-motion media queries.

Does this work with frontend stylesheets that have no animation rules?

It does not apply to frontend stylesheets that have no animation or transition rules. The detection requires the presence of motion effects to check for missing prefers-reduced-motion media query coverage.

Why do my CSS transitions cause issues for motion-sensitive users?

CSS transitions cause issues for motion-sensitive users when they are not wrapped in a prefers-reduced-motion media query. Playing animations without checking user motion preferences can cause motion sickness and reduce accessibility compliance.