Timed Events

Current:

2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A)

• 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.

Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

Proposed:

2.2.1 @@Timed Events: Timed event are not used except for the situations listed below:@@

• @@Security Exception: Where security may be at risk a session can timeout after half an hour of inactivity. Where financial or sensitive information is at risk the time out can be shorter.@@

• 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 @@of inactivity.@@

@@Where there is a Security Exception or 20 Hour Exception the content must also conform to all of the below:@@

• @@No loss of data: The user can easily return to the same point in a task, without data loss, for a period of at least a week:

  1. as the default
  2. via a standardized system setting (for example, the user can choose an option that disables the storage of data)
  3. option to set a user preference that has a conformant interface and is directly available at each stage of the task.@@

• @@Timing adjustable: The function to turn off, adjust or extend the timing are controlled by simple action and labeled with simple text. A user or administrator settable time minimum must be provided to complete any controlling action or the user must be given at least 120 seconds to extend the time limit. The the user is allowed to extend the time limit at least ten times. Note that all user setting must be easy to set and use standardized techniques when available.@@

• @@Aware: The user should be informed of the timeout limits, including the length of the warning.@@

Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

Suggestion for Priority Level

(A)

Related Glossary additions or changes

sensitive information

Information that can put people at risk or information the user wishes to protect.

essential

if removed, would fundamentally change the information or functionality of the content, and information and functionality cannot be achieved in another way that would conform

safe standardized techniques

Standardized by WCAG, other w3c groups, or by the platform, browser or operating system where user vulnerabilities are not exposed without informed consent this will be a discussion and is not yet finalized

What Principle and Guideline the SC falls within.

Principle 2, Guideline 2.2

This is an update to SC 2.2.1

Description

The use of timed events can present significant barriers for users with cognitive disabilites as these users may require more time to read content or to perform functions such as filling out an online form. For situations where the absence of a timed event would significantly change the intended functionality of an application (for example, an auction or other real-time event) it is important to ensure that users with disabilities are properly notified of timed events along with an indication of the duration of the time given as well mechanisms which are clearly labeled to adjust, extend or stop the time duration of such an event in order to allow them to fully engage and interact with Web content and functionality. For example, if the checkout process in an an e-commerce Web site is automatically disabled to provide secure credit card transations, the user is notified of the timeout and is given at least 120 seconds for the ability to extend the time.

During the completion of an online process for reserving and purchasing a ticket for a hotel and flight on a travel Web site, a user with a congnitive impairment may become overwhelmed with the amount of instruction and data input required to complete the process. The user may not be able to complete the process in one sitting and may need to take a break. The user should be able to leave the process without losing their current place in the process and without losing data that has already been entered.

While making a purchase on an e-commerce Web site a user with a congnitive disability may not remember required information that may seem easy to remember for users without a cognitive impariment, for example, a phone number or zip code. These users may need additional time to look up the information required to complete a transaction without losing their place in the process and without losing data that has already been entered.

These experiences have been reported by members of the task force who have have various cognitive impairments.

Benefits

This Success Criterion helps users who need additional time performing tasks or reading content. This can include:

• A Web site uses a client-side time limit to help protect users who may step away from their computer. After a period of inactivity the Web page asks if the user needs more time. If the user does not respond within 120 seconds - it times out. The user is able to request more time at least 10 times.
• A Web page has a field that automatically updates with the latest headlines in a rotating fashion. There is an interactive control that is easy to activate and labeled with simple text that allows the user to extend the length of time between each update to as much as ten times the default. The control can be operated with either a mouse or a keyboard.
• A ticket-purchasing site allows the user two minutes to confirm purchase of selected seats, but warns the user when their time is almost out and allows the user to extend this time limit at least 10 times using a simple action which is labeled with simple text such as clicking a button labeled "Extend time limit".
• In an auction, there is a time limit on the amount of time a user has to submit a bid. Since the time limit applies to all users who want to bid on a particular item, it would be unfair to extend the time limit for any one particular user. Therefore, a time limit is required for this type of activity and no extension, adjustment, or deactivation of the time limit is required by this Success Criteria.

The Success Criterion helps people with a variety of disabilities including:

• People with physical disabilities often need more time to react, to type and to complete activities. People with low vision need more time to locate things on screen and to read. People who are blind and using screen readers may need more time to understand screen layouts, to find information and to operate controls. People who have cognitive or language limitations need more time to read and to understand. People who are deaf and communicate in sign language may need more time to read information printed in text (which may be a second language for some).
• In circumstances where a sign-language interpreter may be relating audio content to a user who is deaf, control over time limits is also important.
• People with reading disabilities, cognitive limitations, and learning disabilities who may need more time to read or comprehend information can have additional time to read the information by pausing the content.

This Success Criterion helps people with many different cognitive disabilities including people with:

• Language related disabilities
• Memory related disabilities
• Focus and attention related disabilities
• Disabilities that effects executive function and decision making

Techniques

• Do not use session timeouts unless there has been a week of inactivity.
• If a situation exists where a timeout is appropriate, use a mechanism to prevent data loss and a conforment mechanism to turn off, adjust or extending the time with a warning.