Timing Adjustable: Fair Time Limits and Timeouts
Also called: Session timeout, Time limit, Timeout warning
Definition
Timing Adjustable is WCAG success criterion 2.2.1. For each time limit set by the content, users can turn it off, adjust it to at least ten times the default or extend it after a warning – unless the limit is part of a real-time event, essential, or longer than 20 hours.
Timing adjustable is the WCAG rule for time limits – a session that logs you out, a form that expires, a reservation that is held for ten minutes, a quiz with a countdown. Everyone needs a different amount of time to read, type and decide. If your site sets a time limit, people must be able to turn it off, make it longer or ask for more time before it runs out.
What it means
WCAG 2.2.1 Timing Adjustable is a Level A criterion in WCAG 2.2. It is also clause 9.2.2.1 of EN 301 549, the standard used for the European Accessibility Act. For each time limit set by the content, at least one of these is true:
| Option | Requirement |
|---|---|
| Turn off | Users can turn the time limit off before they encounter it |
| Adjust | Users can adjust it before they encounter it, over a wide range of at least ten times the default |
| Extend | Users are warned before time expires, get at least 20 seconds to extend it with a simple action (such as pressing a key), and can extend it at least ten times |
| Real-time exception | The limit is a required part of a real-time event, such as an auction, and no alternative is possible |
| Essential exception | The limit is essential and extending it would invalidate the activity |
| 20-hour exception | The time limit is longer than 20 hours |
W3C orders the options by how helpful they are: turning a limit off is best, adjusting it next, extending it last. Content that moves or updates faster than people can read it also counts as a time limit – that overlaps with pause, stop, hide.
People who benefit, according to W3C: people with physical disabilities who need longer to react or type, people with low vision, screen reader users, people with cognitive, language or reading disabilities, and Deaf users who sign and may need more time to read text.
Examples
<div role="alertdialog" aria-modal="true" aria-labelledby="t-title" aria-describedby="t-text">
<h2 id="t-title">Are you still there?</h2>
<p id="t-text">For your security, you will be signed out in 2 minutes.</p>
<button type="button">Stay signed in</button>
<button type="button">Sign out now</button>
</div>The warning appears well before the session ends – far more than the minimum 20 seconds – and one button extends it. As an alert dialog it is announced to screen reader users; for silent updates such as a countdown, an ARIA live region can report the remaining time. W3C's own example: a site that times out after inactivity asks whether the user needs more time and only ends the session if there is no response.
Warn before a session ends and offer "Stay signed in", let people extend at least ten times, let them switch off or lengthen limits in settings, keep entered data after a timeout, and avoid limits that are not needed.
Log people out without warning, give them a warning they cannot answer in time, redirect a page after a few seconds with a meta refresh, or hide the extend option behind a scroll.
How to check timing adjustable
Questions
Are session timeouts allowed under WCAG?
Yes. A session can end after inactivity if users are warned before it expires, get at least 20 seconds to extend it with a simple action and can do so at least ten times – or if they can turn the limit off or lengthen it.
How long must the timeout warning give users?
At least 20 seconds to respond. W3C keeps that window finite on purpose: an unlimited extension period could be a security risk on shared terminals such as kiosks.
What does "ten times the default" mean?
If users can adjust a limit instead of extending it, the range must reach at least ten times the default. A 5-minute limit must be adjustable to at least 50 minutes.
Do online exams and auctions need adjustable timing?
Not always. An auction is a real-time event, and a timed test can be essential if extending it would invalidate the activity. Both are exceptions – other time limits on the same site are not.
Related terms
Pause, Stop, Hide: Control Moving Content
Pause, Stop, Hide is WCAG success criterion 2.2.2. Moving, blinking or scrolling content that starts automatically, lasts more than five seconds and appears alongside other content needs a way to pause, stop or hide it; auto-updating content needs a way to pause, stop or control how often it updates.
Read definition: Pause, Stop, Hide: Control Moving ContentAccessible Authentication: Logins Without Memory Tests
Accessible Authentication (Minimum) is WCAG success criterion 3.3.8. No step of a login may require a cognitive function test – remembering a password, transcribing a code, solving a puzzle – unless an alternative, a helping mechanism or an allowed exception is available.
Read definition: Accessible Authentication: Logins Without Memory TestsARIA Live Regions: Announce Status Messages
An ARIA live region is a part of the page marked with aria-live or a live role such as status or alert. When its content changes, screen readers announce the new text without the user having to move focus to it.
Read definition: ARIA Live Regions: Announce Status Messages