This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung
Accessibility
Automatic log-out: how long can a session last?
This depends on what a stranger can do in the account. The security organization OWASP cites as usual time without activity 2 to 5 minutes for high-value applications and 15 to 30 minutes at low risk. The US standards institute NIST recommends a maximum of 1 hour at the medium and 15 minutes at the highest registration level. The shorter the deadline, the more it depends on the warning.
Time without activity and total duration are separate deadlines
Time without activity begins anew with each activity. The total duration runs independently, even while the customer is working. OWASP calls for an application that someone uses for an entire working day a total duration of 4 to 8 hours. NIST staggers by Authentication Assurance Level (AAL): maximum 30 days on AAL1, 24 hours on AAL2, 12 hours on AAL3. A deadline without activity is not required on AAL1. NIST is a US Directive, version 2025. It is a standard and does not apply automatically to you.
Which value fits which account
Ask about the damage: Can someone in the account only view orders, or can they move money, change delivery addresses or read health data? A customer account with order history is at the long end, an account with payment release is the shortest. A shared computer at the reception speaks for the shorter period. Also add long forms: The server only sees the typing when something is sent to it. Whoever writes long in a field is inactive for him.
A short period of time needs the warning
Criterion 2.2.1 requires, if the deadline cannot be switched off or adjusted, an expiration warning, at least 20 seconds to extend with one simple action and at least 10 possible extensions. NIST advises the same from the point of view of registration: visitors are invited to an activity shortly before the expiration, as an example NIST mentions 2 minutes before. The fixed total duration cannot be extended in this way. For this, NIST advises asking in time for saving. A total duration of more than 20 hours is exempted from the criterion. The W3C can consider shorter deadlines as essential for safety reasons, but cites two-factor codes for limited periods as an example.
The deadline belongs on the server
OWASP requires that the process be enforced on the server. Checks in the browser can be easily bypassed by a skilled attacker. The countdown in the browser shows the visitor how long it still takes. The server blocks access.
- Write down what a stranger could do in each account type, and then set the deadline.
- Keep time without activity and total duration separately, including justification.
- Before expiration, let a warning appear with a button to extend.
- Save input so that even an expired session does not destroy work.




