This page is in progress -
Why This is Important
Not requiring time limits is accessible for people who require more time to complete tasks, e.g. folks with ADD/ADHD, motor impairments, low vision, etc.
Not requiring time limits is also accessible for people who are multi-tasking, in a busy environment, or could get distracted by something. By making time limits adjustable or not required, we are extending access to a diversity of disabilities and situations.
How to Implement This
Don't require a time limit
The easiest way to fulfill this guideline is by not requiring a time limit at all. Keep this in mind during the design and planning phases of work. This would lead to Level AAA compliance.
Provide a way to extend or turn off the time limit
There are certain user experiences where a time limit is considered necessary because supply is limited (e.g. buying concert tickets) or for security reasons (e.g. bank account login session).
In these instances, W3C (World Wide Web Consortium) recommends giving users the ability to extend or turn off the time limit. This can be achieved in a banner or message that notifies users of their time limit (e.g. "You have 8:20 minutes left") and a button (e.g. "Extend by 10 minutes").
Other recommendations for timing:
- IBM 2.2.1 Timing Adjustable
- Understanding SC 2.2.1 Timing Adjustable * Digital A11Y
- 2.2.1 - Timing Adjustable (Level A) | Wuhcag
How to Test This
Testing for time limits requires manually going through major user flows and identifying the presence (or absence) or time limits and what controls are available.
(Do you know of an automated way to test this? Please reach out!)
Contribute and Give Feedback
If you would like to provide feedback or contribute content on this resource, please fill out the form below.