35 lines
1.5 KiB
Markdown
35 lines
1.5 KiB
Markdown
[Back to 2 Operable index](index.html)
|
|
|
|
# 2.2.6 Timeouts
|
|
|
|
- Level: AAA
|
|
- Guideline: 2.2 Enough Time
|
|
- Principle: 2 Operable
|
|
|
|
## What it is
|
|
|
|
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.
|
|
|
|
## How to test
|
|
|
|
- Check: 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.
|
|
- Use the sufficient techniques below as acceptable methods when applicable.
|
|
|
|
## Sufficient techniques (W3C)
|
|
|
|
- Setting a session timeout to occur following at least 20 hours of inactivity
|
|
- Storing user data for more than 20 hours
|
|
- Providing a warning of the duration of user inactivity at the start of a process
|
|
|
|
## Notes
|
|
|
|
- Note: Privacy regulations may require explicit user consent before user identification has been authenticated and before user data is preserved. In cases where the user is a minor, explicit consent may not be solicited in most jurisdictions, countries or regions. Consultation with privacy professionals and legal counsel is advised when considering data preservation as an approach to satisfy this success criterion.
|
|
|
|
## Resources
|
|
|
|
- WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#timeouts
|
|
- Understanding: https://www.w3.org/WAI/WCAG22/Understanding/timeouts.html
|
|
- Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#timeouts
|
|
|
|
[Back to 2 Operable index](index.html)
|