Prevent a timed quote form from silently discarding customer answers

Reproduce the pause that loses information

Use harmless sample answers, pause at the point customers report trouble and observe what changes. Does the page refresh, a session expire, a booking hold end or the request fail after Submit? Those are different events. Record elapsed time and the visible message. Do not put private customer information into an uncontrolled test just to reproduce an expiry.

Identify the timer and the applicable adjustment option

WCAG Timing Adjustable addresses content-set time limits, including limits set by servers under the organization's control. Ask the maintainer to identify the actual limit and any applicable exception. An ordinary security-related session timeout is not automatically exempt merely because it serves a legitimate purpose.

For a non-exempt limit, use an applicable turn-off, adjustment or extension option. Extension requires a warning with at least 20 seconds to act and at least ten extensions. If choosing adjustment instead, allow a range at least ten times the default before the limit is encountered. Answer recovery is useful, but does not itself replace those requirements.

Source checks: W3C: Understanding Timing Adjustable

Test a slower completion and supported recovery

Ask the technical owner what the timer protects and whether the platform supports removing, extending or warning about it. Test the chosen approach in an agreed environment. Review what happens to entered answers and attachments, and whether the customer can tell if a request was accepted. Keep the process proportionate to the sensitivity of the information.

• Record the exact form stage, pause length and event that discards or rejects information.
• Ask the maintainer to identify the site-controlled or receiving-system timer.
• Choose a supported turn-off, adjustment or extension option for that limit, or document the applicable exception.
• Test the chosen option and any recovery with marked answers; operate extension by keyboard and a single pointer.
• Submit after recovery and verify one saved request without a false success receipt.

Avoid automatic refresh as a hidden deadline

Do not solve an expiry by exposing sensitive drafts in an insecure storage location. Do not assume disabling a visible countdown removes server-side limits. An automatic page refresh can discard work without an explanation. If a booking hold expires, avoid pretending the original slot remains available; the customer may need a new availability check.

Record retained answers and acceptance states

Record whether each tested answer survives the pause and what the customer must do to continue. Separate loss of local input from a failed delivery or expired slot. Check the acceptance record after recovery. These observations describe the timing behavior; they do not establish that every long-running browser session will remain valid.

Keep timing behavior documented

Document the controlled limit, reason, approved behavior and customer wording with the form owner. Retest after changing authentication, booking components or file uploads. Tell staff how to handle an uncertain submission without forcing duplicate requests. A recovery route should be understandable even when a customer cannot remember every answer they previously entered.

Worked example: an illustrative five-minute form timer

For example, a consultation form has a five-minute content-set timer. Its supported extension approach warns with 30 seconds remaining and offers a clearly named Extend time button. The configuration permits at least ten extensions; the maintainer verifies that behavior with non-sensitive test inputs.

A marked slower test activates the extension with a keyboard and then with a single pointer, retains its answers and completes through the verified receiving path. Any appointment hold is checked separately. The 30-second warning exceeds the criterion's 20-second minimum for this extension option; the example is illustrative and does not establish a security exception or an indefinitely valid session.

Questions about this task