Accessibility use case
Seizure and Motion Safety
Motion Safety access guidance for Tamil DS
How users stay safe from flashing or harmful motion, supported by WCAG 2.2.2 (Pause, Stop, Hide) and 2.3.1 (Three Flashes).
Detailed guidance for real users, assistive technology, component behavior, testing, and release checks.
Real user scenario
A user opens a learning page with animated cards and auto-playing media. They have reduced motion enabled. The page should show the same content without large transitions, flashing effects, or auto-advancing movement.
How people use this access method
Some users set prefers-reduced-motion at OS level.
Large movement, parallax, zoom transitions, and spinning loaders can trigger symptoms.
Flashing content can create seizure risk when frequency and contrast are unsafe.
Auto-moving content removes user control.
Safe motion keeps meaning without forcing movement.
Design requirements
These requirements are product requirements, not optional polish. If a Tamil DS component or page breaks one of these rules, users may be blocked even when the visual interface looks finished.
Component behavior implications
Accessibility becomes real at component level. The same page may pass content review but fail when dialogs, forms, menus, cards, or status messages do not expose the right behavior.
Carousel must not auto-advance without controls.
Dialog and Sheet transitions should reduce to near-instant changes when motion is reduced.
Toast should not slide aggressively across the viewport.
Skeleton shimmer should be subtle or disabled under reduced motion.
Charts should avoid looping animated drawing for essential data.
Confetti and celebration effects must be disabled when reduced motion is active.
Testing script
Run this script before release. Automated checks are useful, but they do not replace trying the actual access method and completing a real task from start to finish.
Enable reduced motion in the OS and reload the page.
Check CSS animations and JavaScript animation libraries.
Look for auto-playing movement.
Check flashing, blinking, and high-contrast animation.
Confirm all information remains available without motion.
Verify pause controls exist for moving media.
Test loaders and skeletons.
Common failures and fixes
Tamil public-service context
Tamil DS must work for Tamil-first, English-first, and bilingual users across phones, desktops, kiosks, classrooms, offices, and public-service counters. These notes keep the guidance connected to local product reality.
Public-service interfaces should prioritize calm state changes over excitement.
Education pages for Tamil learners should avoid motion that pulls attention away from reading.
Reduced-motion preference should be treated as a hard user setting, not a suggestion.
Release checklist
Reduced motion is respected.
No unsafe flashing exists.
Moving content can pause.
State remains clear without animation.
Celebration and decorative motion are optional.