-
-
Notifications
You must be signed in to change notification settings - Fork 263
Description
We probably should include a mechanism to stop or pause the weekly downloads animation on the package page.
weekly-downloads-animation.mp4
WCAG 2.2 Success Criterion 2.2.2 Pause, Stop, Hide (Level A) states:
For moving, blinking, scrolling, or auto-updating information, all of the following are true:
- Moving, blinking, scrolling
For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
- Auto-updating
For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
For “Moving, blinking, scrolling,” the weekly downloads animation applies for all cases (i.e. it starts automatically, lasts more than five seconds, and is present in parallel with other content).
It’s a little iffy whether or not respecting reduced motion—which this animation does—is sufficient to conform to this success criterion (see Hidde de Vries’ article “Meeting ‘2.2.2 Pause, Stop, Hide’ with prefers-reduced-motion”). Conformance isn’t the purpose of accessibility—providing a better user experience for those with various need is. For example, folks with some cognitive conditions might find it distracting for an animation like this to be continually playing, however, they might positively benefit from the effects of UI animations as it can help with context switching.