Goal
Give users enough time to read and complete tasks.
Success Criterion · WCAG 2.2.1
Timing Adjustable
For each time limit that is set by the content, the user can turn off, adjust, or extend the time limit before encountering it, except for real-time events, essential time limits, or time limits longer than 20 hours.
Level AWCAG 2.0Operable2.2 · Enough Time
Copy button ready
What to do
If there is a time limit, let users turn it off, adjust it, or extend it (with defined exceptions).
Why it matters
Users may need more time due to disabilities, language, or situational constraints; hard time limits can block access or cause data loss.
Success criterion
What WCAG 2.2.1 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
For each time limit that is set by the content, at least one of the following is true: (1) Turn off: The user is allowed to turn off the time limit before encountering it; or (2) 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 (3) Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (e.g., “press the space bar”), and the user is allowed to extend the time limit at least ten times; except for real-time events, time limits that are essential, and time limits longer than 20 hours.
Intent
Why WCAG created this requirement
- Time limits can disproportionately affect users with motor, cognitive, or reading disabilities.
- Extensions must be offered with clear warning and a simple action.
- Provide flexibility unless the timing is essential or real-time.
Benefits
Who gains when you pass
- Users with motor impairments can complete tasks without rushing.
- Users with cognitive disabilities can read and respond at their own pace.
- Users using screen readers can complete forms that otherwise timeout.
- All users benefit when interruptions don’t cause data loss.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may lose work when sessions expire without warning or extension.
Users may fail timed interactions they could otherwise complete.
Users may abandon tasks due to stress caused by countdown timers.
Exception guidelines
Use the WCAG 2.2.1 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Real-time events
Timing is inherent to real-time events.
Requirement
If truly real-time, time limit exception may apply.
Essential time limit
Timing is essential to the activity.
Requirement
Only if essential; user preference is not essential.
20 hours or longer
Very long time limits are exempt.
Requirement
If the limit is at least 20 hours, it is exempt.
Overview
If your content imposes time limits (session timeouts, timed quizzes, expiring forms), users must be able to disable, adjust, or extend the time. Exceptions exist for real-time events, truly essential time limits, and limits longer than 20 hours.
- Warn users before timeout and provide an easy way to extend.
- Save progress to prevent data loss on expiration.
- Do not reset timers unexpectedly without informing the user.
- If timing is essential (e.g., auctions), document rationale and consider alternatives.
Reference: All summaries and highlights originate from Understanding WCAG 2.2.1 and the W3C quick reference.
Fast facts
- Conformance level
- Level A
- WCAG version introduced
- WCAG 2.0
- Principle
- Operable
- Guideline
- 2.2 · Enough Time
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Session timeout
Pass
User is warned and can extend session with a single keypress; form data is preserved.
Fail
Session ends without warning and wipes form data.
Timed quiz
Pass
User can adjust timer to a longer duration or request extra time before starting.
Fail
Quiz has fixed 2-minute timer with no adjustment or extension.
Expiring link
Pass
User can request a new link and progress is preserved.
Fail
Link expires mid-flow and forces restart with data loss.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document all timers/timeouts and the user controls available.
- Record evidence of warning dialogs and extension behavior.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Inventory all time limits (auth timeouts, expiring links, quizzes, inactivity timers).
- Provide a way to turn off or adjust the limit where feasible.
- If not, warn before expiry and provide a simple extend action (≥ 20 seconds window).
- Allow extending at least 10 times for extend-based approach.
- Preserve user data on timeout (autosave drafts) where possible.
- Document any “essential” time limits with justification.
Testing ideas
Prove conformance with evidence
- Identify each time-limited flow and verify one compliant option (turn off/adjust/extend).
- Verify warning occurs before expiry and extension is simple and repeatable.
- Confirm extension window is at least 20 seconds.
- Verify users can extend at least 10 times where applicable.
- Verify data is not lost unexpectedly when timeouts occur.
Related success criteria