Accessible Form Response Time

Accessible form response time

Whenever a form puts a time limit on the user, WCAG 2.1 Success Criterion 2.2.1 Timing Adjustable says they have to be able to turn off, adjust (up to 10×) or extend it. To get a rough baseline, figure T_total = n · t_field + t_review + t_submit. Count on t_field being 5–15 s for typed answers and 2–5 s for checkboxes. People using assistive technology generally need two to three times that.

Show the timeout warning at least 20 seconds before the limit runs out, and give people one easy way to keep going (something like "press any key"). For field and submission feedback, lean on ARIA live regions. Use role="status" or aria-live="polite" when things go right, and role="alert" (or aria-live="assertive") for errors, so a screen reader speaks them up without yanking focus away. And remember that SC 3.3.1 Error Identification wants the error spelled out in words, not signalled by color alone.

Applications

Reach for the calculator when you need to size session timeouts for checkouts, government forms, banking apps or exam platforms. The relevant references are WCAG 2.1/2.2, W3C ATAG 2.0, Brazil's eMAG 3.1 recommendation 1.7, the Lei Brasileira de Inclusão (Lei 13.146/2015) and Section 508 (§ 502.2.1).

FAQ

Can the form auto-submit on timeout? Only when the data is kept and the user can pick up where they left off within 20 hours. Anything short of that breaks 2.2.1.

How do I announce a success message? Drop the text into a node carrying role="status" and assistive technology will read it out, focus untouched. Skip alert() popups.

What is the AAA target? At that level, SC 2.2.3 No Timing strips out time limits entirely, sparing only real-time events like auctions or live auth.