Operable · Level AAA · Introduced in WCAG 2.1
WCAG 2.2.6: Timeouts
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
At Level AAA, tell users how long inactivity can last before it causes data loss, unless the data is preserved for more than 20 hours without action. The notice should help users plan before investing effort.
A practical example
An application explains before data entry that an unsaved draft is cleared after 30 minutes of inactivity. A later warning and extension mechanism address other timing requirements but do not replace the initial duration information.
How to check it
- Identify inactivity limits that can discard user-entered information.
- Locate a clear explanation of the duration before the user is at risk of losing work.
- If relying on preservation, test and document storage beyond 20 hours with an appropriate privacy and security design.
What can be missed
“Your session may expire” does not communicate the duration. This AAA notice requirement is distinct from the Level A rules for adjusting or extending time limits.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.