- 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
// Server response header:
Refresh: 20; url=/searchWhy it matters
A user comparing search results gets bounced back to an empty search page before deciding what to play.
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
Never redirect users away from content on a server timer with no warning.
<!-- Remove the timed Refresh header entirely -->
<p>Your search results are ready. <a href="/search">View them</a></p>Outcome
Search results stay put long enough for a listener to browse them and pick a track.
Who is affected
Users with cognitive or memory disabilities lose track of their search and must start over repeatedly.
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