Resource guide
2.2.6 Timeouts
Users must be warned about timeouts that could cause data loss, unless data is preserved for more than 20 hours.
By Calling All Minds·Last updated April 2026
Success criterion
Conformance level
Enhanced accessibility — beyond the legal minimum.
What it means
Where inactivity could lead to data loss, users must be warned upfront at the start of a process. The warning must tell them how long they have and what will happen when the time runs out.
If the system preserves all user data for at least 20 hours of inactivity, this warning is not required.
In practice
Display session duration and timeout information at the start of any multi-step process.
If data is not preserved, warn users explicitly: 'This form will time out after 30 minutes of inactivity. Your data will not be saved.'
The simplest solution is to save data automatically and preserve it for at least 20 hours.
Common failures
- Multi-page form with a 15-minute timeout that is not disclosed at the start of the process
- Application form that clears data after inactivity with no upfront warning
AXS Audit
AXS Audit checks your site against 2.2.6 and flags issues your team can act on straight away. It covers criteria that automated scanners often miss.