Writing & StyleStyle guide

Writing Accessible Timeout Warnings

Writing Accessible Timeout Warnings distinguishes timeout-warning content from general status messages and anchors the guidance in current WCAG timing and timeout documentation.

Quick answer

Write timeout warnings that state the inactivity consequence clearly, identify the relevant time limit when known, and tell users how to continue or extend the session when that option exists.

Key details

Core IssueWCAG 2.2 says users should be warned about inactivity durations that can cause data loss, with timing guidance also covering warnings before certain time limits expire.
Registerweb accessibility and interface content

Important caveats

Scope Boundary

This page covers warning content; timeout duration, security policy, focus behavior and extension implementation are separate technical concerns.

Further guidance

Content

Warn that inactivity can end the session or cause data loss, state the relevant duration when known, and give a clear next action when extension is available.

Purpose

Timeout warnings help users understand the consequence of inactivity before work is unexpectedly lost.

Sources and evidence

Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.

  1. Understanding SC 2.2.6: Timeouts — WCAG 2.2 (opens in a new tab)World Wide Web Consortium (W3C) · WCAG 2.2 guidance on warning users about inactivity periods that can cause data loss.
  2. Understanding SC 2.2.1: Timing Adjustable — WCAG 2.2 (opens in a new tab)World Wide Web Consortium (W3C) · WCAG 2.2 guidance on communicating and controlling time limits, including warnings and extensions.

Explore the topic