WELCOME [ Log In · Register ]        SITE [ Search · Page Index · Recent Changes ]    RSS

Time Limits

Home > PDF/UA Home > Working Draft > Breadcrumb placeholder text

Reference WCAG 2.0 Guideline 2.2
Allow users to control time limits on their reading or interaction.

2.2.1

For each time-out that is a function of the content, at least one of the following is true:
  • the user is allowed to deactivate the time-out or;
  • the user is allowed to adjust the time-out over a wide range which is at least ten times the length of the default setting or;
  • the user is warned before time expires and given at least 20 seconds to extend the time-out with a simple action (for example, "hit any key") and the user is allowed to extend the timeout at least 10 times or;
  • the time-out is an important part of a real-time event (for example, an auction), and no alternative to the time-out is possible or;
  • the time-out is part of an activity where timing is essential (for example, competitive gaming or time-based testing) and time limits can not be extended further without invalidating the activity.

2.2.2

Content does not blink for more than 3 seconds, or a method is available to stop any blinking content in the delivery unit.

2.2.3

Content can be paused by the user unless the timing or movement is part of an activity where timing or movement is essential.

2.2.4

Except for real-time events, timing is not an essential part of the event or activity presented by the content.

2.2.5

Interruptions, such as updated content, can be postponed or suppressed by the user, except those involving an emergency.

2.2.6

When an authenticated session has an inactivity timeout, the user can continue the activity without loss of data after re-authenticating.

When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.