WCAG Guideline 2.2.6: Timeouts Explained
Estimated read time: 6–7 minutes
Guideline 2: Operable
The Operable principle ensures that all users can interact with and control web content, regardless of their abilities. This includes informing users about timeouts and their impact on data or progress.
Guideline 2.2: Enough Time
Guideline 2.2 focuses on making sure users have enough time and information to complete tasks. Timeouts can cause users to lose data or progress if not properly communicated.
What Is Guideline 2.2.6 Timeouts?
"Users are warned about timeouts and can request more time before being logged out or losing data."
Guideline 2.2.6 Timeouts is a Level AAA requirement in the Web Content Accessibility Guidelines (WCAG) .
- Users must be warned about session or activity timeouts that could cause data loss.
- Exception: if data is preserved for more than 20 hours of inactivity, no warning is required.
- Applies to forms, applications, and any activity with a timeout.
This ensures users are warned about timeouts and can request more time, preventing data loss and frustration.
For more, see Stanford UIT: Session Timeout Accessibility .
Why Does It Matter?
- Inclusivity: Timeouts can cause data loss for users who need more time.
- Legal Compliance: Timeouts is a Level AAA requirement in WCAG 2.1 and 2.2.
- Usability: Prevents frustration and loss of work for all users.
For more, see W3C’s guidance on timeouts .
What Needs to Support Timeouts?
- Online forms and checkouts
- Applications with session timeouts
- Any feature with a timeout
All must warn users about timeouts that could cause data loss.
How to Make Timeouts Accessible
- Warn users before timeouts occur
- Allow users to request more time
- Document timeout policies
- Test with users who need more time
For more, see the W3C's Timeouts Techniques .
Common Mistakes to Avoid
- No warning before timeout
- No way to request more time
- Not documenting timeout policies
- Not testing with users who need more time
Differences Between A, AA, and AAA for Guideline 2.2.6 in WCAG 2.2
- Level A: Not applicable for this guideline.
- Level AA: Not applicable for this guideline.
- Level AAA: Requires users are warned about timeouts and can request more time. This is the core requirement for 2.2.6 and is mandatory for AAA conformance.
For more, see the W3C’s official documentation for 2.2.6 Timeouts .
Quick Checklist
- Users are warned before timeouts
- Users can request more time
- Timeout policies are documented
- Tested with users who need more time
Summary
Guideline 2.2.6 is essential for preventing data loss and supporting users who need more time. By warning users about timeouts and allowing them to request more time, you support users with disabilities, improve usability, and meet legal requirements. Test your site regularly and make timeout management a core part of your development process.
Up Next