• Success Criterion 2.2.1
  • Conformance level A

Session Warning That Gives Users Less Than 20 Seconds to Respond

2.2.1 — Timing Adjustable

Scenario

Setting

A nonprofit's donation form

What’s wrong

Warning shown but with <20s to respond, or requiring complex re-auth as the "simple action".

Example 

setTimeout(() => submitLogout(), 8000);
// "Extend" requires re-entering password and a one-time code

Why it matters

A donor filling out payment details gets logged out before they can even read the warning dialog.

How to test

Time the warning before session expiry: it must appear at least 20 seconds before the timeout, giving a simple way to extend — less time fails.

How to fix

Give at least 20 seconds and let one click extend the session, no password re-entry.

setTimeout(() => showExtendDialog(), sessionDuration - 30000);
// Extend button just calls: extendSession(); // no re-auth required

Outcome

Reading the warning calmly, a donor extends their session with one click and finishes giving.

Who is affected

Users with dyslexia or slower reading speeds cannot process the warning and respond within 8 seconds.

Learn more

Related scenarios