Goal
Warn users about inactivity timeouts that could cause data loss.
Success Criterion · WCAG 2.2.6
Timeouts
Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.
Level AAAWCAG 2.1Operable2.2 · Enough Time
Copy button ready
What to do
Provide a warning before inactivity timeouts occur and explain how to extend or prevent data loss.
Why it matters
Inactivity timeouts can end sessions unexpectedly; users may need more time and may lose work if not warned.
Success criterion
What WCAG 2.2.6 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.
Intent
Why WCAG created this requirement
- Users should not be surprised by inactivity timeouts.
- Warnings help users avoid losing work and plan their time.
- Data preservation can remove the need for warnings.
Benefits
Who gains when you pass
- Users who need breaks can avoid unexpected data loss.
- Users with cognitive disabilities can manage pace without penalty.
- All users benefit from transparency about timeouts.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may lose unsaved work without warning.
Users may abandon tasks if they cannot trust that progress will be preserved.
Exception guidelines
Use the WCAG 2.2.6 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Data preserved for > 20 hours
If data is preserved for more than 20 hours without user action, warning is not required.
Requirement
Preserve data for > 20 hours to qualify for this exception.
Overview
If your system uses inactivity timeouts that can cause loss of data (unsaved changes), you must warn users about the timeout duration. If data is preserved for more than 20 hours without user action, you do not need to warn.
- Warn users about the timeout duration before inactivity can cause data loss.
- Prefer autosave/drafts to preserve data and reduce reliance on warnings.
- Ensure the warning itself is accessible and provides actionable options (save, extend, continue).
Reference: All summaries and highlights originate from Understanding WCAG 2.2.6 and the W3C quick reference.
Fast facts
- Conformance level
- Level AAA
- WCAG version introduced
- WCAG 2.1
- Principle
- Operable
- Guideline
- 2.2 · Enough Time
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Inactivity warning
Pass
Before form entry, UI states: “You will be logged out after 15 minutes of inactivity. Drafts are saved.”
Fail
Session expires with no warning and user loses unsaved changes.
Autosave
Pass
Draft is saved and restored after returning later.
Fail
No autosave; inactivity equals data loss.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document timeout durations and where warnings appear.
- Capture evidence of warning UI and available user actions.
- Document draft/autosave strategy and retention duration.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Identify all inactivity timeouts that can cause data loss.
- Provide a clear warning about the timeout duration before users begin the activity or before inactivity triggers.
- Offer actions to prevent loss (save draft, extend session, continue).
- Autosave work to minimize risk and potentially meet the 20-hour preservation exception.
- Ensure warnings are accessible (screen reader, keyboard, focus management).
Testing ideas
Prove conformance with evidence
- Identify inactivity timeouts and verify the user is warned of duration.
- Verify warning is presented in time to act and provides clear actions.
- Test with keyboard and screen reader (focus moves to dialog if modal; can dismiss appropriately).
- If claiming the 20-hour exception, verify data persists beyond 20 hours without action.
Related success criteria