|
|
|
|
|
Timing Adjustable
Guideline
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 ten 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 ten 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.
Intent
The intent of this regulation is to ensure that users with disabilities are given adequate time to interact with Web content whenever possible. People with disabilities such as blindness, low vision, dexterity impairments, and cognitive limitations may require more time to read content or to perform functions such as filling out on-line forms. If Web functions are time-dependent, it will be difficult for some users to perform the required action before a time limit occurs. This may render the service inaccessible to them. Designing functions that are not time-dependent will help people with disabilities succeed at completing these functions. Providing options to disable time limits, customize the length of time limits, or request more time before a time limit occurs helps those users who require more time than expected to successfully complete tasks. These options are listed in the order that will be most helpful for the user. Disabling time limits is better than customizing the length of time limits, which is better than requesting more time before a time limit occurs.
Any process that happens without user initiation after a set time or on a periodic basis is a time limit. This includes partial or full updates of content (for example, page refresh), changes to content, or the expiration of a window of opportunity for a user to react to a request for input.
It also includes content that is advancing or updating at a rate beyond the user's ability to read and/or understand it. In other words, animated, moving or scrolling content introduces a time limit on a user’s ability to read content.
Finding Applicable Components
Determine if there is a timeout function from the application's documentation, or by leaving the session inactive for a period of time.
Inspecting and Using Components
- Check that an alert for a timeout is displayed, rather than the application exiting without warning.
- Check that the user is offered the option to continue their task (i.e., request more time), or exit.
- Check that the alert message is displayed for at least 20 seconds before the page actually times out.
Section 508/WCAG 2.0 Failure Conditions
- A time-out occurs, and users are not alerted.
- Fails 1194.22(p): Time out notification.
- Fails 2.2.1 Timing Adjustable.
- A time-out occurs, and users cannot request more time.
- Fails 1194.22(p): Time out notification.
- Fails 2.2.1 Timing Adjustable.
- A time-out occurs, and is displayed for less than 20 seconds.
- Fails 1194.22(p): Time out notification.
- Fails 2.2.1 Timing Adjustable.
Reporting Test Results
Any failure in Section 508 Failure Conditions results in: Fails Baseline Requirement #25.
A time-out occurs, users are alerted, AND users can request more time, AND the length of time that the alert is displayed is 20 seconds or more then: Passes Baseline Requirement #25.
See Also |