- Success Criterion 2.2.1
- Conformance level A
- W3C reference F58
Server Redirect Timeout With No Warning or Way to Extend It
2.2.1 — Timing Adjustable
Scenario
Setting
A streaming music app's search results
What’s wrong
The server automatically redirects the user to another page after a timeout, with no warning and no way to extend the time.
Example
setTimeout(() => logOut(), 60000); // no warningWhy it matters
People who read, type, or move slowly, including many screen-reader users.
How to test
Wait through any server-driven auto-redirect after a timeout: check whether a warning appeared beforehand and offered to cancel or extend.
How to fix
Remove server-side timed redirects, or warn the user and let them extend/cancel before it happens. setTimeout(() => showExtendSessionPrompt(), 55000); Users need a warning and a way to extend a time limit before it expires, unless the limit is essential (e.g. an auction).
Outcome
On a streaming music app's search results, this barrier is gone for people who read — they reach the same outcome without extra effort.
Who is affected
People who read, type, or move slowly, including many screen-reader users.
Learn more
- Understanding Understanding document (opens in a new tab)
- Technique Related technique (opens in a new tab)
Related scenarios
- Page Auto-Redirects on a Timer With No Way to Stop It
- Page That Auto-Reloads and Resets the User’s Position
- Session Expiring With No Warning and No Way to Extend It
- Session Warning That Gives Users Less Than 20 Seconds to Respond
- Session Extension Allowed Fewer Than the Required 10 Times
- Timeout Adjustment Option Set Below the Required 10x Default