2.2.2: Pause, Stop, Hide
For any moving, blinking or scrolling information that:
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.
For any auto-updating information that:
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.
The intent of this WCAG success criterion is to remove distractions and disorientating elements on a website. This allows for users with disabilities to freely access information when they choose to do so, especially in the case of auto-updating information.
Examples of elements that contain moving, blinking, scrolling, and auto-updating include:
Users of screen reader technology such as JAWS, NVDA, Windows Narrator, ORCA, VoiceOver, and TalkBack can be affected by auto-updating elements. A user could have the screen reader focus on a carousel or on real time information. The carousel then moves to a new set of information, or the real time event changes. A screen reader user might not be aware of this change and thus feels that the information they are now presented with is incorrect.
Low vision users or users with motor skill issues may also have trouble with these updating elements, as they may not have finished reading a particular portion of the website before it changes and then find it difficult to look for the controls that will navigate back.
As part of our consultations, accessibility audits, and training sessions, we can identify and explain all the contextual nuances that would apply to WCAG 2.1 Success Criterion 2.2.2 Pause, Stop, Hide.
If you have any questions or need help with any digital accessibility issue, please don’t hesitate to make contact with IA Labs.