Skip to Content
WCAG GuidesTime Limits & Moving Content

Time Limits and Moving Content

Give users control over time limits and moving, blinking, scrolling, and auto-updating information under WCAG 2.2.1 and 2.2.2

Maintained by Martin KrugerLast reviewed

WCAG 2.2.1 requires most author-set time limits to be turned off, adjusted, or extended, with specific real-time, essential, and long-duration exceptions. WCAG 2.2.2 applies to moving, blinking, or scrolling information that starts automatically, lasts more than five seconds, and appears alongside other content, and separately to auto-updating information. Users need controls to pause, stop, hide, or control update frequency unless the behavior is essential.

An auto-dismiss toast is not automatically a 2.2.1 failure. Evaluate whether its timing limits an activity, whether equivalent persistent information exists, and whether any action remains available. Reduced-motion preferences improve comfort but do not replace required pause or timing controls.

Uncontrolled Timeout and Ticker vs. User Controls

Inaccessible

Your session ends in 20 seconds.

Breaking updates move continuously across this area…
View inaccessible code
<p>Your session ends in 20 seconds.</p> <div class="moving-ticker">Updates…</div> <!-- No way to extend, pause, stop, hide, or change frequency. -->
Accessible

Your session ends in 20 seconds.


Latest update: services are operating normally.

View accessible code
<p id="warning">Your session ends in 20 seconds.</p> <button aria-describedby="warning">Extend session</button> <button>Sign out now</button> <button aria-pressed="false">Pause updates</button>

Test it

Measure timing from the user’s perspective, including warnings and extension duration. Operate pause and extension controls with keyboard and touch. Confirm that pausing actually freezes meaningful updates, focus is not moved unexpectedly, and any status confirmation is concise and non-interactive.

Resources