Timeouts that can be extended or turned off

What it is

Automatic timeout behavior appears throughout interfaces — expiring login sessions, verification-code countdowns, pages that auto-redirect after inactivity. This is about giving users a way to extend or turn off these timeouts, rather than fixing one duration and forcing everyone to live with it.

Why it happens

Timeout durations are usually set as a fixed value based on some assumed "average operating speed," but the time it actually takes different people to complete the same operation varies widely — reading speed, decision speed, and familiarity with the operation path all affect it. With those factors stacked up, the same timeout duration is comfortable for some users and simply not enough for others. Giving users a way to extend or disable a timeout hands the judgment of "how long is enough" back to the person doing the task, instead of asking the designer to guess a single number that fits everyone.

Where it stops holding

Timeouts in security-sensitive contexts — confirming a financial transaction, a login session on a public device — cannot simply be removed; extending or disabling them there directly conflicts with the goal of keeping an unattended, logged-in device safe from other people. The right move there is to offer renewal, not to remove the timeout itself. Nor does every user need a longer timeout: for fast, experienced users, an overly long timeout mainly makes it easier to forget to log out, widening the window during which the device could be accessed by someone else.

Applying it

• For timeouts tied to reading, filling in forms, or verification (form sessions, verification-code windows), give a clearly noticeable warning well before expiry — at least a quarter of the total timeout duration in advance, or at minimum one distinct, perceptible warning moment — and provide a one-tap way to extend it.
• Non-security auto-redirects (a support page returning to the home screen after inactivity, a tutorial auto-advancing) should offer a way to turn the behavior off or extend it substantially; it should not be a fixed, unchangeable default.
• Security-related timeouts (login sessions) should not be disabled indefinitely, but users should be able to renew the session with a single action before it expires, rather than having to redo the entire login flow afterward.
• Verification: have participants who genuinely operate more slowly (not limited to older adults) complete a full flow, and record how much of the default timeout duration they actually use. If a meaningful share come close to or exceed the default, it is set too tight — recalibrate it from that measured data, or make the extension option far more visible.

Related

• Same group: A11.03.4 task decomposition and single-task screens · A11.03.5 persistent, visible undo affordance
• Nearby: A11.01 age-related capability change · A10.08 error tolerance and graceful degradation
• Search terms: session timeout · adjustable timeout · time-out warning