Default font size Increase font size  |   Decrease font size   |  
Skip to main content

Success Criterion 2.2.1 Timing Adjustable: [Level A]

The intent of this Success Criterion 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. This is not a requirement for real-time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours.

Techniques

Extending or cancelling time limits for form completion

If a multi-part form is to be completed and a time limit set fr, a checkbox should be provided to allow the user to request more time for completion of the form. This is particularly important if the form is complex and when links are available to view additional information. A similar mechanism could be used to cancel the time limit completely. These controls must be placed at or near the top of the page.

If a script is controlling time limits on a page, the user should be provided with ability to cancel the time limit, extend it by up to 10 times the default limit or be warned when the limit is about expire. When a warning is issued, the ability to extend the limit should also be offered.

Extending time limits for reading content

This occurs when there is some kind of dynamic activity occurring which is controlling the scrolling or display of content, such as a scrolling news headline banner or an animation imparting information. A method must be provided to pause the content and be able to restart it. If there was a news headline which was updated say every minute, a mechanisn should be provided which could cancel the update thus providing extra time for the headline to be read.

Failures

Using meta refresh with a time limit

If a meta element is being used to redirect the user to a new page there should be no time limit set.

<meta http-equiv="refresh" content="5; url=http://www.example.com/newpage" />

It should also not be used to refresh the page after a given period. This in fact is a deprecated method.

<meta http-equiv="refresh" content="60" />

Using server-side redirects with a time limit

If a redirect or refresh is being performed by server-side functionality it is a failure if any time limit is applied to the process. This is a rather old example of a classic ASP page performing this.

<% @Language = "VBScript" %>
<% 
option explicit    
Response.Clear   
Response.AddHeader "Refresh", "5; URL=TargetPage.htm"   
%>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"    
	"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">   
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
Top