Animation & Motion Tester – Test Reduced Motion
Test animations and motion effects with prefers-reduced-motion support. Verify WCAG 2.3.3 compliance, detect system preferences, and ensure animations respect user accessibility needs. Test spin, slide, fade, pulse, bounce, parallax effects with live examples and CSS implementation guide.
Advertisement
Ad blocked by browser
Examples of Real-World Usage
6 real-world examples
Web Developers
Implement and test prefers-reduced-motion support to ensure animations respect user preferences.
Accessibility Specialists
Verify WCAG 2.3.3 compliance, test animation behavior, and audit motion accessibility.
UX Designers
Design animation patterns that work with reduced motion, ensuring inclusive user experiences.
QA Testers
Add reduced motion testing to accessibility checklist and verify proper implementation.
Product Managers
Understand accessibility requirements for animations and ensure products respect user needs.
Frontend Engineers
Learn CSS techniques for implementing accessible animations that adapt to user preferences.
Complete Animation Accessibility Testing
Test animation behavior with reduced motion preferences, verify WCAG compliance, and ensure your animations are accessible to users with vestibular disorders and motion sensitivities.
Live Animation Preview
See animations in action and test how they behave with reduced motion settings
Reduced Motion Toggle
Enable/disable reduced motion mode to simulate user preferences and test accessibility
System Preference Detection
Automatically detect if user has enabled prefers-reduced-motion in their operating system
CSS Implementation Guide
Get ready-to-use CSS code for implementing prefers-reduced-motion media queries
Multiple Animation Types
Test various animations: spin, slide, fade, pulse, bounce, shake, and parallax effects
WCAG 2.3.3 Compliance
Verify compliance with WCAG animation and motion requirements for accessibility
Educational Content
Learn why motion reduction matters and who benefits from reduced motion interfaces
Accessibility Guidelines
Understand best practices for implementing animations that respect user preferences
How to Use
Simple 6-step process
Step 1
Check your system's motion preference status shown at the top of the tool
Step 2
View the animation examples to see common CSS animations in action
Step 3
Toggle 'Reduced Motion Mode' to simulate how animations behave when users enable this preference
Step 4
Verify that animations stop or are significantly reduced when the toggle is enabled
Step 5
Review the CSS implementation code to learn how to add prefers-reduced-motion support
Step 6
Test your own website by enabling reduced motion in your OS settings and checking animations
Frequently Asked Questions
Everything you need to know about our process, pricing, and technical capabilities.
See Full FAQprefers-reduced-motion is a CSS media query that detects if the user has requested reduced motion in their operating system accessibility settings. How to enable it: Windows: Settings → Accessibility → Visual Effects → Animation effects (toggle off) macOS: System Preferences → Accessibility → Display → Reduce motion iOS: Settings → Accessibility → Motion → Reduce Motion Android: Settings → Accessibility → Remove animations CSS usage: @media (prefers-reduced-motion: reduce) { .animated-element { animation: none; } }
Motion and animation can cause serious issues for users with: Vestibular disorders: Inner ear problems causing dizziness, vertigo, nausea from motion Migraine: Animations can trigger severe headaches Seizure disorders: Flashing or rapid motion can cause seizures ADHD: Animations distract and make focusing on content difficult Autism: Sensory overload from excessive movement Motion sickness: Parallax and scrolling effects cause nausea For these users, animations aren't just annoying - they can make websites completely unusable or even cause physical harm.
When users enable reduced motion, you should: Remove animations entirely: Set animation: none and transition: none Reduce duration: Make transitions very short (0.01ms) Disable parallax: Use static positioning instead Stop auto-play: Disable auto-playing carousels and videos Remove loading spinners: Use static progress indicators Simplify transitions: Use instant state changes instead Keep essential feedback: You can keep very subtle transitions for things like :focus states - just make them immediate (0.1s max). Example: @media (prefers-reduced-motion: reduce) { * { animation-duration: 0.01ms !important; transition-duration: 0.01ms !important; } /* Allow essential focus indicators */ *:focus { transition: outline 0.1s; } }
Even with reduced motion, some visual feedback is important: Keep these (but make subtle): Focus indicators (:focus outlines) Hover states on interactive elements Loading/progress indicators (use static instead of spinning) Form validation feedback (instant, no delay) Disable these completely: Parallax scrolling effects Auto-playing carousels Decorative animations Infinite animations (spinners, pulses) Zoom/scale effects Rotating elements Background animations Key principle: Essential feedback can remain, but should be instant or very brief. Decorative motion must stop.
Auto-playing content is particularly problematic: WCAG 2.2.2 (Pause, Stop, Hide): Users must be able to pause, stop, or hide moving content. Best practices: Videos: Don't auto-play. Provide play/pause controls. Respect prefers-reduced-motion. Carousels: Provide pause button. Stop auto-advance when reduced motion enabled. Animations: Offer controls to pause/disable. Stop when user enables reduced motion. Example: const prefersReducedMotion = window.matchMedia( '(prefers-reduced-motion: reduce)' ).matches; if (!prefersReducedMotion) { startCarousel(); } Remember: Motion that lasts more than 5 seconds MUST have controls (WCAG 2.2.2).
Testing checklist for prefers-reduced-motion: Enable in OS: Turn on reduced motion in system settings Check media query: Use DevTools to verify @media (prefers-reduced-motion: reduce) is applied Test animations: Verify all decorative animations stop or reduce significantly Check carousels: Auto-advance should stop Test parallax: Parallax effects should be disabled Videos: Auto-play should be prevented Loading indicators: Should use static or minimal animation Hover effects: Can remain but should be instant Browser testing: // Chrome DevTools: Rendering → Emulate CSS media feature // Firefox DevTools: Accessibility → Simulate → prefers-reduced-motion
Still have questions?
Can't find what you're looking for? We're here to help you get the answers you need.