Skip to main content

WCAG wiki

2.2.6 Timeouts (Level AAA) — WCAG 2.1

WCAG 2.1 Success Criterion 2.2.6 Timeouts (Level AAA): what it requires, a common e-commerce accessibility failure, and how to fix it.

This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.

WCAG 2.1 guidelines hub → Operable → 2.2.6 Timeouts

2.2.6 Timeouts (Level AAA)

What it requires: Users are warned in advance about any inactivity timeout that could cause data loss, unless the data is preserved for more than 20 hours.

Common failure: An account settings form silently logs the user out after inactivity with no warning, discarding unsaved edits.

Fix it: Warn users before a timeout that would cause data loss, with enough lead time to save or extend the session.


In 2.2 Enough Time: ← 2.2.5 Re-authenticating

↑ Back to Operable overview

This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.

This page was drafted with AI assistance and reviewed by a person for accuracy before publication.