Skip to content

2.2.1

Jump to bottom
Andrew Hick edited this page Jun 4, 2026 · 10 revisions

2.2.1 Timing Adjustable

WCAG says:

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.

When this is applicable

Always.

Identify time limits

A page may impose a time limit on reading content or using some functionality. This might include:

  • content being updated or disappearing
  • no longer being able to submit a form
  • being logged out of an account
  • an automatic reload

To help identify time limits:

  • look for text at the start of a process warning users of a time limit
  • open the page in a separate browser or browser profile so it does not interfere with other testing, fill in any form fields and leave the page open as long as you reasonably can
  • you can ask the website owners whether there are any time limits, where possible

The success criterion requires you to wait 20 hours to check for a timeout, but this is often not practical due to working patterns or because browsers can put tabs to sleep. In many cases you can detect a timeout after 1 to 2 hours.

Check time limits

If a time limit is identified, check that you can either:

  • turn it off before you encounter it
  • increase it up to 10 times before you encounter it
  • extend it with a method that:
    • warns users at least 20 seconds before it expires
    • uses a simple control, such as pressing a single key
    • can be used at least 10 times

Exceptions

  • real-time events, for example bidding on an item in an online auction
  • when timing is essential, such as a school exam
  • time limits longer than 20 hours
  • holding or loading pages that have no other meaningful content and are essential to the process, for example, a page displaying the message "the payment is processing" while a transaction completes
  • pages that reload or redirect instantly that do not need to be read
  • if there is an alternative that does not rely on the time limit, for example chat bubbles showing a new message which disappear after a few seconds, but the message can also alternatively be read in the chat panel

Best practice

  • Avoid using time limits unless they are essential.
  • Notify users upfront about any time limits and provide clear instructions on how they can adjust or extend them.
  • Give users more than 20 seconds to extend a time limit.

Mobile app testing

No difference

Clone this wiki locally