Respect Time & Interruptions

Timers can create stress — especially for users with cognitive disabilities, attention limitations, or mobility impairments. If your interface auto-logs users out, rotates content without consent, or refreshes the page mid-interaction, it could leave them confused or locked out.

Accessibility means respecting people’s pace — not rushing or surprising them with interruptions.

WCAG Says:

• 2.2.1 Timing Adjustable (A): Users must be able to turn off, adjust, or extend time limits unless the limit is essential (e.g., auction countdown).
• 2.2.6 Timeouts (AAA): Users must be warned about inactivity timeouts before losing data, with a chance to extend the session.

Good Practice

• Warn users before a session timeout
• Allow users to pause, extend, or disable auto-advancing carousels or timers
• Avoid content that auto-refreshes or updates while users are reading or interacting
• Don’t move focus without user action

📘 Examples:

🔒 Session Timeout

<p>You will be logged out in 2 minutes due to inactivity.</p>
<button>Extend session</button>

Watch Out For

• Auto-advancing slides with no controls
• Session timeouts that don’t warn users or discard data
• Focus shifts caused by content updates
• Refreshing dashboards or content without notice
• Countdown timers with no way to pause or adjust

Pro Tip

For web apps and SPAs:

• Use modals or toast warnings to alert about timeouts
• Store user data frequently to avoid loss
• Use aria-live regions for updates — but don’t steal focus

A simple warning before timeout gives users agency and reduces frustration.

Do this today: Check your app or site for timed actions: session timeouts, rotating carousels, countdowns, or auto-refresh. Can users pause, extend, or stop those timers? If not, add controls or remove the time limit altogether unless it’s essential.