2.2.6 Timeouts
Introduction
This document provides information about the related Acquia Web Governance accessibility check:
What
This check verifies that when inactivity can trigger a session timeout and cause loss of unsaved, user-entered information, the interface clearly informs users how long they can be inactive before the timeout occurs. The requirement is met if users are warned in advance (for example, at the start of the relevant process) or if the data that the user has entered is preserved for more than 20 hours without any action from the user.
Why
Many users require more time to complete forms or read content. Without a warning, these individuals may lose significant work or be forced to restart a process unexpectedly. This also benefits anyone in a distracting environment who may be interrupted when they perform a task.
Who
This check affects individuals with:
- Cognitive disabilities: Who may require more time to complete forms or read content.
- Physical impairments: Who may require more time to complete forms or read content.
- Vision impairments: Who use assistive technologies.
- No impairments: Who may be interrupted or distracted.
Examples
Pass example
During checkout, a message at the start of the flow states: “Your session will end after 15 minutes of inactivity. If the session ends before you place your order, the information you entered may not be saved.”
Fail example
A banking application automatically logs a user out after 10 minutes without any prior notification, which causes the user to lose the data they entered into a loan application.
HTML
<meta http-equiv="refresh" content="600;url=logout.html">
How
This section provides information on how to review and fix this issue.
How to review it
Identify flows that can time out due to inactivity (for example, checkout or long forms).
If the site keeps the data that the user entered for more than 20 hours without any user-action, this check is met. Otherwise, review user journeys that can time out if the person stops interacting, and ensure that the page informs users in advance how long they can be inactive before the session ends, and that they might lose what they have entered.
How to fix it
If a flow can time out due to inactivity and users could lose what they have entered, fix it in one of these ways:
- Preserve the user’s input for more than 20 hours without any action from the user (for example, save the form as a draft and restore it when they return).
- Inform users in advance, at the start of the flow, how long they can be inactive before the session ends, and that they might lose unsaved information. Place this where users can view it before they begin (for example, on the first step of checkout or at the top of the form).
Additional resources
WCAG success criteria
Are users warned if inactivity could cause them to lose work?
2.2.6 Timeouts
Introduction
This document provides information about the related Acquia Web Governance accessibility check:
What
This check verifies that when inactivity can trigger a session timeout and cause loss of unsaved, user-entered information, the interface clearly informs users how long they can be inactive before the timeout occurs. The requirement is met if users are warned in advance (for example, at the start of the relevant process) or if the data that the user has entered is preserved for more than 20 hours without any action from the user.
Why
Many users require more time to complete forms or read content. Without a warning, these individuals may lose significant work or be forced to restart a process unexpectedly. This also benefits anyone in a distracting environment who may be interrupted when they perform a task.
Who
This check affects individuals with:
- Cognitive disabilities: Who may require more time to complete forms or read content.
- Physical impairments: Who may require more time to complete forms or read content.
- Vision impairments: Who use assistive technologies.
- No impairments: Who may be interrupted or distracted.
Examples
Pass example
During checkout, a message at the start of the flow states: “Your session will end after 15 minutes of inactivity. If the session ends before you place your order, the information you entered may not be saved.”
Fail example
A banking application automatically logs a user out after 10 minutes without any prior notification, which causes the user to lose the data they entered into a loan application.
HTML
<meta http-equiv="refresh" content="600;url=logout.html">
How
This section provides information on how to review and fix this issue.
How to review it
Identify flows that can time out due to inactivity (for example, checkout or long forms).
If the site keeps the data that the user entered for more than 20 hours without any user-action, this check is met. Otherwise, review user journeys that can time out if the person stops interacting, and ensure that the page informs users in advance how long they can be inactive before the session ends, and that they might lose what they have entered.
How to fix it
If a flow can time out due to inactivity and users could lose what they have entered, fix it in one of these ways:
- Preserve the user’s input for more than 20 hours without any action from the user (for example, save the form as a draft and restore it when they return).
- Inform users in advance, at the start of the flow, how long they can be inactive before the session ends, and that they might lose unsaved information. Place this where users can view it before they begin (for example, on the first step of checkout or at the top of the form).
Additional resources
WCAG success criteria
Web Governance