elite-accessibility

To make web animations accessible, you must integrate prefers-reduced-motion handling to provide accessible fallbacks for users with vestibular disorders or motion sensitivity. This ensures CSS and GSAP animations remain usable by offering reduced-motion strategies.

WCAG compliance for motion-heavy components requires accessible focus indicators, skip links, ARIA roles, and keyboard navigation patterns. Applying these motion accessibility patterns ensures scroll-driven reveals and parallax effects provide an inclusive UX.

Handle prefers-reduced-motion in GSAP and CSS by applying provided motion accessibility patterns that respect the user setting and offer accessible fallbacks. This approach ensures motion-rich interfaces degrade gracefully for users needing reduced motion.

Yes, this skill explicitly instructs on co-loading with elite-gsap or elite-css-animations. You integrate these motion accessibility patterns into your animation workflow by consulting the references and applying the frontmatter guidance.

Accessible web animations require focus management and keyboard navigation patterns, including accessible focus indicators, skip links, and ARIA roles. These practices ensure motion-rich interfaces are navigable and comply with WCAG standards.