Success criterion 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 AAA
- Principle 2: Operable
- Guideline 2.2: Enough Time
In a user’s words
“I stepped away for a coffee and came back to a locked vault. Let me know if you're timing me out!”
What each role can do
- Product manager
- Clearly communicate any timeouts that might result in data loss.
- Designer
- Design notifications or alerts to inform users about the session timeout.
- Developer
- Implement mechanisms to warn the user prior to timeouts and preserve data whenever possible.
- Tester
- Test for session timeout warnings and data preservation across different scenarios.
Once it is fixed
“Now I can enjoy my coffee and still know what's going on. Cheers!”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 2.2.6 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.