Make a failed form submit button usable again

What to change

Require a submission state that prevents accidental repeats while the request is pending and restores the appropriate action after a known failure.

A worked example

Illustrative example

The visitor sees Sending while a request is pending. A confirmed rejection restores Send enquiry beside a clear explanation of the failure.

How to check the result

Accept when a recoverable failure never leaves the interface stuck, and each retry produces one understandable outcome for the current answers.

A mistake to avoid

Enabling retries after an uncertain connection loss requires a separate duplication strategy; a working button alone does not resolve that uncertainty.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordAsk the supplier to simulate a rejected test request. Check that the button leaves its busy state and becomes available once retry is appropriate.Correct a field after the failure and activate the button with keyboard and touch. Confirm the retry uses the corrected values rather than the earlier attempt.Compare the pending, failed and successful states. Each should describe what is happening without using the same generic label for incompatible outcomes.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.