WCAG 2.2.1: Timing Adjustable

Back to all WCAG criteria

OVERVIEW

Effort:

  • Complexity:Difficult
  • Duration:Slow

Important for:

Development

What's it about?

For time-dependent actions — such as automatic logouts or timers — users must have the option to extend, pause, or disable the time limit.

Illustration of an online banking page showing a countdown labeled “Remaining time: 0:21.” A large warning dialog appears stating, “Warning: You will be logged out in 20 seconds!” with two buttons: “Give me more time” and “Okay.”

How to

Depending on your situation, you can implement one of the following options to meet the criterion. For a deeper dive, please refer to the linked WCAG techniques.

    Notes

    • Exception: A time limit is essential

      If a time limit is required for security reasons, it is exempt from this criterion. Example: payment processes or the protection of sensitive data.

      This also applies when the time limit is an essential part of a real-time event, such as an auction or an exam.

    • Exception: Alternative for time-limited status messages

      Status messages often disappear automatically after some time. This is problematic when they contain important information that the user cannot find elsewhere on the website.

      If status messages disappear on their own, the information must be available again in another place on the website.

      Example: An online shop shows a temporary toast message saying that you successfully added a product to your cart. You also receive this information in another way, because the number “one” appears next to the cart icon.

      Illustration of an online shop website. A message with a disappearing progress bar says: Successfully added to the cart. Additionally, the user receives the same information through the number 1 displayed in the top right next to the cart icon.

            Create accessible designs?

            Our workshop for designers!

            Learn everything you need to know as a designer to create accessible design systems for digital products and entire brands.

            Learn more about the workshop
            Four principles of the Web Content Accessibility Guidelines: Perceivable – a red triangle holding a magnifier. Operable – a yellow circle with question marks overhead. Understandable – a green rectangle looking confused at a screen. Robust – a blue square wearing sunglasses and holding a keyboard.

            Learn accessibility with us?

            Looking to implement WCAG best practices in your design, development, or content workflow? Book a workshop for your team or contact us directly to learn more.

            Send us an email!