Giraffe Forum

A form error is not a slap on the wrist. It is a chance to help someone finish the task they already started.

Too many sites treat failure as theater: a red banner at the top, a vague line like “Please correct the errors below,” and a page that jumps back to the beginning. The customer loses their place, sometimes loses typed values, and has to hunt for what went wrong. That is organization-centric design. It protects the system. It does not help the person.

Start with recovery, not blame. Name the problem in plain words next to the field that needs attention. “Enter a phone number with ten digits” is useful. “Invalid input” is not. If several fields failed, list them, but keep each message tied to a control people can see and change.

Never punish people by clearing what they already typed. Password fields may need to be re-entered for security; almost everything else should stay. Preserving input says you respect their time. Wiping a long form after one missing checkbox says you do not.

Move focus to the first problem. Screen readers and keyboard users should land where the fix begins, not on a logo or a decorative alert that explains nothing. A short summary at the top can help—“Two fields need attention”—as long as it links or points to the fields themselves.

Timing matters. Inline checks can help when the rule is obvious (an incomplete email address), but do not interrupt every keystroke with scolding. Validate on submit for rules that need the whole form, and again when the person leaves a field if you can do it without noise.

Avoid clever copy. “Oops!” and “Uh-oh, that didn’t work” waste a moment when people are already annoyed. Warmth is fine; vagueness is not. Prefer concrete verbs and outcomes: what to change, what format to use, what happens next when they try again.

Server and network failures deserve honesty too. If the form could not be saved because the service was down, say that and offer a retry. Do not dress a timeout as a validation error on the customer’s address.

Measure recovery the way you measure completion. Track how often people succeed after an error, how many abandon on the error screen, and which messages correlate with repeat failures. A witty banner with a high abandon rate is not friendly. It is a blocked task.

Forms are promises. When the promise breaks, the interface should still guide people to the finish. Clear field messages, preserved work, and one obvious next step—that is simplicity customers can feel.