---
title: "Timing Adjustable"
url: "https://www.barrierefreihochzwei.de/en/wcag/2-2-1-timing-adjustable"
language: "en"
description: "WCAG 2.2.1 requires that users can turn off, adjust or extend time limits. Learn how to build warnings and extensions that actually work for everyone."
published: "2025-01-01T08:00:00+01:00"
updated: "2026-10-15T09:42:00+02:00"
---

# Timing Adjustable

When time becomes a luxury.

- **Erfolgskriterium:** 2.2.1
- **Prinzip:** Operable
- **Konformitätsstufe:** Level A
- **Erklärung beim W3C:** [www.w3.org/WAI/WCAG22/Understanding/timi...](https://www.w3.org/WAI/WCAG22/Understanding/timing-adjustable.html)

Success criterion 2.2.1

# 2.2.1 Timing Adjustable

Level AOperable

When time becomes a luxury.

## 1. What is the goal of this criterion?

Imagine ordering pizza online, and after 30 seconds the page jumps back to the homepage – because the system decided you were too slow. Annoying for anyone, but for people with disabilities it is often the reason they can’t use certain online services at all.

People with motor impairments need longer to type, people with low vision need more time to read, and people with cognitive disabilities often need extra time to understand content. The goal of Success Criterion 2.2.1 is therefore to give everyone enough time to finish their tasks – without the clock running out on them.

## 2. What exactly does it require?

It covers every time limit set by the website or application itself. For each of these time limits, at least one of the following must be true:

**Turn off:** Users can turn off the time limit before they encounter it.

**Adjust:** Users can adjust the time limit in advance over a wide range – at least ten times the default setting.

**Extend:** Users are warned before time expires, get at least 20 seconds to extend the limit with a simple action (for example, “press the space bar”), and can do so at least ten times.

**Exceptions** only apply in specific cases:

- The time limit is a required part of a real-time event (such as an auction) and no alternative is possible.
- The time limit is essential and extending it would invalidate the activity (for example, an exam where time is part of the task).
- The time limit is longer than 20 hours.

Important: security is not an exception. An automatic session timeout in online banking must also offer one of the three options – in practice, usually a warning with the chance to extend.

An example: a ticketing site gives you two minutes to confirm your selection. The system warns you in time and offers an “Extend time” button that you can use several times.

## 3. Why does it matter for accessibility?

Imagine filling out an important form – for a government service, a job application or an online purchase – and halfway through, the page resets because your session has expired. Everything you entered is gone.

Time limits create barriers because they:

- disadvantage people with motor impairments who need longer to type and navigate.
- put pressure on people who are blind or have low vision and need more time to find and take in content.
- exclude people with cognitive disabilities who need to process information at their own pace.
- disadvantage Deaf people for whom written language is often a second language, so reading takes longer.
- create stress for everyone – including people without disabilities.

Flexible time limits, on the other hand, let everyone use digital services successfully without feeling rushed or missing important steps.

## 4. How to meet the criterion

The good news: flexible time limits are usually straightforward to build and improve the experience for everyone. Here are some proven tips:

**Principles for user-friendly time limits:**

- Only use time limits where they are really needed (security, fair distribution of scarce resources).
- Tell people about time limits at the start of an activity.
- Warn before time runs out and give at least 20 seconds to respond.
- Make extending easy: a single click or key press must be enough.
- Allow at least ten extensions.

**Technical implementation:**

- **JavaScript timers:** Build countdown functions with pause and extend options.
- **Session management:** Extend the server-side session as soon as someone confirms the extension.
- **Personal settings:** Let people increase or turn off default time limits in their account.
- **Warnings:** Show the warning as a dialog that receives focus and is announced by screen readers (for example with `role="alertdialog"`). A toast message that disappears on its own is not enough.

**When a time limit has to stay:** In security-critical areas (online banking, email portals) you can keep time limits, but you must warn before they expire and offer an extension. It also helps to:

- save form data automatically
- move time-critical steps to the end of a process
- let people continue exactly where they left off after signing in again (see [Re-authenticating](https://www.barrierefreihochzwei.de/en/wcag/2-2-5-re-authenticating))

Even stricter requirements are set at Level AAA by [No Timing](https://www.barrierefreihochzwei.de/en/wcag/2-2-3-no-timing) and [Timeouts](https://www.barrierefreihochzwei.de/en/wcag/2-2-6-timeouts).

## 5. Why this criterion matters for businesses

Success Criterion 2.2.1 shows once again that accessibility isn’t just a cost – it brings real benefits.

### 1. Fewer abandoned processes

Anyone who has to start over in the middle of checkout because their session expired will often give up entirely. Flexible time limits and timely warnings make sure orders and forms actually get completed.

### 2. Happier customers

Nobody likes being rushed. User-friendly time limits reduce stress and frustration – which means fewer support requests and more people who are glad to come back.

### 3. A wider audience

According to the WHO, around 1.3 billion people worldwide live with a significant disability. Add older people and anyone who is distracted or on a slow connection. Flexible time limits make your services usable for all of them.

And finally: 2.2.1 is a Level A criterion and therefore part of WCAG 2.1 AA, which the harmonised standard EN 301 549 references. Under the European Accessibility Act (EAA), many consumer services such as online shops must meet these requirements; in Germany, the EAA is implemented by the Barrierefreiheitsstärkungsgesetz (BFSG), which has applied since 28 June 2025. This is general information, not legal advice.

## 6. The success criterion in the W3C’s words

> **Success Criterion 2.2.1 Timing Adjustable (Level A)**
> 
> 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.
> 
> 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.

In short: every time limit must be possible to turn off, adjust substantially or extend easily after a warning – except for real-time events, essential time limits or limits longer than 20 hours.

**Official explanation from the W3C**

The W3C explains every success criterion in depth – with intent, examples and techniques.

[Understanding 2.2.1](https://www.w3.org/WAI/WCAG22/Understanding/timing-adjustable.html)

## More criteria from “Operable”

 [  2.1.1 Level A ### Keyboard

When every click can also be a keystroke.

 ](https://www.barrierefreihochzwei.de/en/wcag/2-1-1-keyboard) [  2.1.2 Level A ### No Keyboard Trap

When there’s no way out.

 ](https://www.barrierefreihochzwei.de/en/wcag/2-1-2-no-keyboard-trap) [  2.1.3 Level AAA ### Keyboard (No Exception)

When everything really has to work by keyboard.

 ](https://www.barrierefreihochzwei.de/en/wcag/2-1-3-keyboard-no-exception)
