WCAG 2.0 · Level A · Operable
2.2.2 Pause, Stop, Hide
Manual verification
How to validate 2.2.2 by hand
Check moving, blinking, scrolling, or auto-updating content that starts automatically and continues alongside other content.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Load the page and wait to identify motion or updates that start automatically and last more than five seconds.
- Locate a mechanism to pause, stop, or hide moving content, or to control the update frequency for auto-updating content.
- Operate the mechanism by keyboard and pointer, then confirm the content stays paused or updates at the chosen rate.
Evidence to record
Record the content, start/duration, control, and whether motion can be paused or updates controlled without losing the task.
Scope and exceptions
Essential activity and certain user-controlled updates have exceptions. Automatically updated information may need a separate pause or frequency control from animation.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.