SC 2.2.1 Timing Adjustable
Ensure users can manage time limits to complete tasks at their own pace.
- Turn Off: Allow users to disable the timer before it starts.
- Adjust: Allow increasing the limit to at least 10x the default.
- Extend: Provide a warning 20+ seconds before expiry and allow extending at least 10 times.
- Exceptions: Real-time events (e.g., auctions), essential limits (e.g., security timeouts where extension invalidates the activity), or limits > 20 hours.
2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true:
- Turn Off: The user is allowed to turn off the time limit before encountering it; or
- Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least 10 times the length of the default setting; or
- Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, “press the space bar”), and the user is allowed to extend the time limit at least 10 times; or
- Real-Time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
- Essential Exception: The time limit is essential and extending it would invalidate the activity; or
- 20-Hour Exception: The time limit is longer than 20 hours.
SC 2.2.1 Timing Adjustable (In Context) supports the Operable principle by ensuring that users with disabilities have the capability to use native or Web applications that have time constraints. The intent of this SC is to ensure that users have the ability to turn off, adjust, or extend the time limit. A common example is giving a user five minutes to fill in and submit a Web form. Users must be provided notification of the time expiration and be allowed at least 20 seconds to extend or turn off the time limit.
Without notification, simply timing out may make some systems unusable for some users with disabilities. Time limits for Web content are often set at the Web server level, but they can also be set programmatically within content. Native software applications can rely on operating system time-out configuration, or build in these time-outs.
Impact of Nonconformance with SC 2.2.1 Timing Adjustable
| Type of Disability | Description of Impact |
|---|---|
| 302.1 Without Vision | Users who are blind cannot use a mouse to interact with electronic content and typically use an assistive technology, such as a screen reader, to get audible or other alternative output for the information represented visually. To be able to navigate the content, understand its structure and relationships, and understand the meaning of content represented in graphics and images, the content must provide textual and programmatic cues in addition to the content presented purely visually. |
| 302.2 With Limited Vision | Users with limited vision may have widely different visual perception. Individuals with limited vision may or may not use assistive technologies. Therefore, in addition to textual and programmatic cues necessary for assistive technologies, ICT must also present content consistently and predictably. Users who view content with magnifiers may not pick up alerts, warnings, or other content if such content is presented outside of a consistent and predictable navigation pattern or if the content is not itself viewable at large magnification. Content that becomes distorted when magnified can also prevent some users with limited vision from being able to understand or interact with the content. |
| 302.7 With Limited Manipulation | Some users may not be able to perform actions that require fine motor control (clicking and dragging), path dependent gestures (pattern-based passcodes), or simultaneous actions (Ctrl + Alt + Del). Providing alternative means to perform the same actions, such as entering the size specifications in an input field to resize an object or allowing sequential key entries, can enable users with limited manipulation to interact with the same content. |
| 302.8 With Limited Reach and Strength | Some users may lack sufficient strength to perform actions such as squeezing, grasping, or depressing a hardware control. Some users, including those in wheelchairs or of shorter stature, may not be able to reach controls that are placed too high or too far away from where a user would access the device controls or interface. ICT designers and developers must consider a broad range of statures, strength and dexterity limitations, and the needs of wheelchair users in order to provide interfaces that are operable with limited reach and/or strength. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Some users require more time than average to process information while others may find complicated instructions difficult to follow. Furthermore, some ICT content can distract or overwhelm users, preventing them from being able to interact with or understand other ICT content. Designers and developers of ICT must consider a broad range of cognitive abilities in order to provide ICT that is simple and easy to use. |
Applicability of Success Criteria 2.2.1 Timing Adjustable
| Technology | Applicability of SC 2.2.1 Timing Adjustable |
|---|---|
| All (Web, Software, Office documents, PDFs, Mobile Native) | Numerous methods exist for setting time limits on Web and software content. While time limits may not be encountered or utilized with much frequency in Office or PDF documents, it is possible to implement limits using custom coding. Whatever method is used to set time limits for content, authors and developers must ensure that they also provide a method turn off, adjust, or extend the time limit. |