W3C WCAG 2.2.1 Timing Adjustable (Level A)
Allow users to turn off, adjust, or extend time limits in content, with exceptions for real-time events, essential functions, and limits exceeding 20 hours
Where this comes from
Provision: 2.2.1 Timing Adjustable (Level A)
Instrument: W3C Web Content Accessibility Guidelines (WCAG) 2.2
Citation: W3C, Web Content Accessibility Guidelines (WCAG) 2.2, Success Criterion 2.2.1 Timing Adjustable, Level A, W3C Recommendation 05 October 2023
Text version: WCAG 2.2
Who it applies to
It applies when all of these are true:
- Service type — any answer
- Service is likely to be accessed by children under 18
What engineering work it implies
Sample acceptance criteria Landfall generates for this obligation:
- For each content-set time limit, users can turn it off, adjust it to >=10x, or extend it before it expires
- Session/timeout warnings appear >=20 seconds before expiry with a simple extend action (allowing >=10 extensions)
- Auto-advancing or auto-updating content (carousels, tickers, countdowns) has pause/stop controls
- Exceptions (real-time events, essential limits, limits >20 hours) are documented, not assumed
- Unit tests cover the core logic (aim for >80% coverage on new code)
Questions people ask
- Does W3C WCAG 2.2.1 Timing Adjustable (Level A) apply to my service?
- It applies when Service type — any answer; Service is likely to be accessed by children under 18.
- From when does this apply?
- W3C WCAG 2.2.1 Timing Adjustable (Level A) applies from 5 October 2023. Its current status is: in force.
Find out whether this one lands on you
Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.
Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.