Moving content can be paused or hidden easily
What this criterion checks
This criterion maps to 2.2.2 Pause, Stop, Hide. A detailed plain-language description is maintained in the WebLens criteria catalogue; the WCAG sub-test breakdown below describes exactly what the agent checks and what it does not.
How it's assessed
WebLens walks each user journey, captures a screenshot at every step, and an agent reasons over that evidence. See the how WebLens works for the full pipeline and the deterministic checks layered in for accessibility.
Sub-test coverage
2.2.2 Pause, Stop, Hide is broken into 3 sub-tests. Coverage is honest about where the agent is reliable, where it only partially checks the requirement, and where a human reviewer is still needed.
1 partial2 not covered
- Moving/blinking/scrolling content can be paused, stopped, or hiddenPartial
Our tool detects the use of the deprecated marquee element (scrolling text) and blink element (flashing text), both of which violate this criterion. However, it does not detect moving, blinking, or scrolling content created via CSS animations, JavaScript, carousels, animated GIFs, or other modern techniques.
- Auto-updating content can be controlledNot covered
Detecting auto-updating content (live feeds, stock tickers, auto-refreshing sections) and verifying user control mechanisms requires behavioral testing. Not automatable with static code analysis.
- Essential movement exceptionNot covered
Determining whether movement or auto-updating is essential to the activity (e.g., a loading spinner indicating actual processing) requires human judgment. Not automatable.
How reliable it is
This criterion is currently scoring below its expected accuracy range, so confirm each finding before acting on it. See Accuracy & confidence for how the confidence tags are set.