Category: WCAG Principles and Conformance

Timing Adjustable

Also known as: WCAG Success Criterion 2.2.1, SC 2.2.1, Adjustable Time Limits

Simply put

Timing Adjustable is an accessibility requirement stating that when a website or application sets a time limit, users should generally be able to turn it off, adjust it, or extend it before it runs out. This helps people who need more time to read content, complete forms, or interact with a page. It is a Level A criterion in the Web Content Accessibility Guidelines (WCAG), the level most fundamental to accessibility.

Formal definition

Timing Adjustable is WCAG Success Criterion 2.2.1 (Level A). It requires that for each time limit set by the content, at least one of the following is true: the user can turn off the time limit before encountering it; the user can adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; the user is warned before time expires and given at least 20 seconds to extend the limit with a simple action (such as pressing a key), and can extend it at least ten times; the time limit is a required part of a real-time event (for example, an auction) and no alternative is possible; the time limit is essential and extending it would invalidate the activity; or the time limit is longer than 20 hours. This criterion appears across WCAG 2.0, 2.1, and 2.2. Meeting this success criterion supports but does not by itself guarantee an overall accessible experience or legal compliance, and applicable legal obligations depend on jurisdiction; consult qualified counsel and current agency guidance.

Why it matters

Time limits are common on the web, appearing in session timeouts, checkout flows, online forms, quizzes, and banking or government portals. For many users, a countdown that works fine for one person can create an insurmountable barrier for another. People who use screen readers or keyboard navigation, those with cognitive or learning disabilities, individuals with limited dexterity, and anyone who reads more slowly may need substantially more time to absorb content or complete an interaction. When a time limit expires without warning, users can lose entered data, be logged out mid-task, or be blocked from finishing a critical activity such as scheduling an appointment or submitting a benefits application.

Timing Adjustable (WCAG Success Criterion 2.2.1) addresses this by requiring that users generally be able to turn off, adjust, or extend a time limit before it runs out. Because it is a Level A criterion, the most fundamental conformance level in WCAG, it is widely treated as a baseline expectation rather than an enhancement. The criterion appears consistently across WCAG 2.0, 2.1, and 2.2, reflecting its long-standing role in the guidelines.

Meeting this success criterion supports a more equitable experience, but it does not by itself guarantee overall accessibility or legal compliance. Automated tools can flag some timing behaviors, yet confirming that warnings appear, that extension mechanisms work, and that the extension range is adequate typically requires manual and assistive technology testing. Legal obligations vary by jurisdiction and evolve through regulation and case law, so organizations should consult qualified counsel and current agency guidance rather than relying on conformance alone.

Who it's relevant to

Front-end developers and engineers

Developers implement the mechanisms that satisfy this criterion, including timeout warning dialogs, controls to disable or lengthen limits, and logic that lets users extend a session with a simple action. They should verify that extension ranges meet the required thresholds (such as at least ten times the default) and that warnings give users the minimum time to respond.

UX and interaction designers

Designers determine whether time limits are necessary at all and how warnings, extension prompts, and adjustment settings are presented. Clear, timely, and easy-to-use controls help ensure that users who need more time can respond before a limit expires without losing their work.

QA and accessibility testers

Because automated tools detect only a portion of timing issues, testers should manually confirm that warnings appear before expiration, that extension mechanisms function as intended, and that the criterion's conditions are met with keyboard and assistive technology. Testing should also account for the narrow exemptions, such as real-time events or essential time limits.

Product and compliance teams

Teams responsible for session security, form flows, and conformance targets should understand that Timing Adjustable is a Level A criterion commonly treated as a baseline. Balancing security-driven timeouts with the ability to warn and extend is often necessary. These teams should track how requirements are addressed but treat this guidance as informational rather than legal advice, consulting qualified counsel and current agency guidance for compliance decisions.

Inside Timing Adjustable

Timing Adjustable (WCAG Success Criterion 2.2.1)

A Level A success criterion under WCAG that addresses situations where a time limit is set by the content. It generally requires that users be able to turn off, adjust, or extend time limits, subject to defined exceptions.

Turn Off Option

Users are able to turn off the time limit before encountering it, allowing them to complete tasks without a countdown constraining them.

Adjust Option

Users can adjust the time limit before encountering it, commonly to a duration of at least ten times the default length, giving individuals more time to read or interact.

Extend Option

Users are warned before a time limit expires and given the ability to extend it, typically through a simple action and multiple opportunities to do so.

Recognized Exceptions

The criterion generally allows exceptions such as real-time events (for example, an auction) where the time limit is essential, situations where extending the limit would invalidate the activity, and time limits longer than a defined threshold (commonly cited as twenty hours).

Affected User Groups

People who may need more time to read content or complete tasks, including individuals with cognitive, motor, or visual disabilities, as well as users of assistive technologies that add interaction overhead.

Common questions

Answers to the questions practitioners most commonly ask about Timing Adjustable.

Does meeting the Timing Adjustable success criterion mean my site is fully accessible or legally compliant?

No. Timing Adjustable is a single WCAG success criterion addressing time limits, and satisfying it does not guarantee an accessible experience across all disabilities or immunity from legal claims. Conformance with one criterion is distinct from overall WCAG conformance, from usability for real users, and from legal compliance. Automated testing detects only a portion of timing-related issues, so manual and assistive technology testing are generally needed. This guidance is not legal advice; consult qualified counsel regarding your obligations.

Does Timing Adjustable require removing all time limits from my content?

No. The criterion does not require eliminating every time limit. It generally provides options such as allowing users to turn off, adjust, or extend a time limit before it expires, subject to certain exceptions where a time limit is essential or where the limit is very long. The intent is to give users who need more time a way to accommodate that need rather than to prohibit time limits entirely.

How should we let users extend a session that is about to time out?

A common approach is to warn the user before a time limit expires and offer a simple action, such as a clearly labeled control, to extend the time. The user should be able to extend without losing their work or having to start over. The specific mechanism and thresholds should be evaluated against the criterion's provisions, including how much advance warning is given and how many extensions are permitted.

Are there situations where a time limit does not need to be adjustable?

The criterion recognizes certain exceptions, such as when a time limit is essential to the activity and adjusting it would invalidate the activity, or where the time limit is very long. Real-time events and auctions are examples often discussed where timing may be integral. Because the exact scope of these exceptions matters, review the criterion's language directly and evaluate each case rather than assuming an exception applies.

How do we handle content that auto-updates or refreshes on a timer?

Content that moves, updates, or refreshes automatically can create timing barriers and may implicate related criteria in addition to Timing Adjustable. Where feasible, provide a way for users to pause, stop, or control the timing of updates so they can read and interact at their own pace. Consider how automatic updates affect assistive technology users, and test with real assistive technology rather than relying on automated checks alone.

How can we verify that our time-limit handling actually works for users?

Combine methods: review the timing behavior against the criterion's provisions, then conduct manual testing and testing with assistive technologies to confirm that warnings, extension controls, and data preservation function as intended. Because automated tools detect only some issues, manual and assistive technology testing are generally required to confirm the experience works for people who need additional time.

Common misconceptions

Timing Adjustable means all time limits must be removed from a website or application.

The criterion does not require eliminating time limits universally. It generally provides options to turn off, adjust, or extend them, and it recognizes exceptions such as essential real-time events and time limits beyond a defined threshold.

Meeting Timing Adjustable is enough to guarantee an accessible or legally compliant experience.

Conformance with this single Level A success criterion does not by itself ensure overall accessibility or legal compliance. It is one of many criteria, and meeting WCAG does not guarantee immunity from legal claims. Manual and assistive technology testing remain necessary, and legal questions should be directed to qualified counsel.

Session timeouts for security reasons are exempt from any accessibility consideration.

Security-related timeouts are not automatically exempt. Where a time limit applies, the criterion generally expects users to be warned and given a means to extend it unless a recognized exception applies. Practitioners should evaluate whether an exception genuinely fits rather than assuming security overrides the requirement.

Best practices

Warn users before a time limit expires and provide a simple, clearly labeled way to extend it, offering multiple opportunities where feasible.

Where possible, allow users to turn off or adjust time limits before they take effect, commonly supporting an adjusted duration of at least ten times the default.

Preserve user-entered data when a session ends so that people can re-authenticate and resume without losing their work.

Review each time limit to confirm whether a recognized exception (such as an essential real-time event) genuinely applies before relying on it.

Test timing behavior with keyboard and assistive technologies and with real users, since automated tools detect only a portion of timing-related issues.

Document timing decisions and consult current agency guidance and qualified legal counsel, recognizing that requirements evolve through regulation and case law and that this guidance is not legal advice.