Error Messages That Help People Finish
An error message is read at the exact moment a visitor is closest to leaving. Written as help - at the field, in plain words, saying what to do - it rescues completions. Written as a verdict, it ends them.
The short answer
A good error message does three things: it appears at the field that needs attention, it says in plain words what is wrong, and it says what to do to fix it. It never blames, never uses codes or jargon, and never punishes the visitor by clearing the rest of the form. Most form abandonment at the error point is not caused by the mistake - visitors mistype constantly and expect to - it is caused by messages that scold, confuse, arrive all at once at the top of the page, or force the visitor to start again. Errors are a normal part of every form; treat them as a service moment, not a failure event.
At the field, at the moment, in context
Place the message beside or directly under its field, visually connected to it, and keep it there until fixed. The alternatives fail predictably: a summary banner at the top saying three fields need attention sends the visitor hunting; a message that appears only after submit, for a mistake made five fields earlier, arrives stripped of context; and red outlines with no words leave the visitor guessing which of several possible rules they broke. Validate as the visitor leaves each field where the check is instant and certain - an email with no @, a date in the past - and reserve submit-time checks for things that genuinely depend on the whole form.
Write the fix, not the fault
Compare two messages for the same mistake. First: Invalid input. Second: Enter the email address the quote should go to - it needs an @ and a domain, like [email protected]. The second is longer and infinitely cheaper, because it converts confusion into a next action. The pattern generalises: name the field in human words, state the expected shape with an example when format matters, and keep the tone of a helpful person standing beside the visitor. Avoid error codes, avoid all-caps warnings, avoid exclamation marks entirely. If a rule is genuinely yours rather than the world's - a password length, a date window - say so and say why, briefly.
Never clear the form, and other forms of respect
The single most destructive error behaviour is wiping completed fields when one field fails. A visitor who has typed a long message, then mistypes a postcode, and returns to an empty form has been told their effort is worthless, and they believe it: most do not type it twice. Preserve everything, return the visitor to the first field needing attention with the message visible, and let them repair one thing at a time. The same respect applies to passwords and uploads: re-asking for one sensitive field is acceptable and explainable; silently discarding a written message never is. Test this deliberately, because several form tools do it by default.
Errors everyone can perceive
Colour alone is not an error message. A red border that a colour-blind visitor cannot distinguish, or text a screen reader never announces, abandons exactly the visitors accessibility guidance exists to protect. Pair colour with words and an icon or marker, connect the message to its field in the code so assistive technology announces it, and move focus thoughtfully on submit so keyboard and screen-reader users land at the problem, not at the top of a silent page. The WCAG guidance on error identification and suggestions is the reference here, and meeting it helps every visitor, because clarity under stress is clarity for all.
Count your errors; they are a design report
Form tools and analytics can show which fields produce errors and how often - treat that list as a prioritised design report, covered in measuring form completion. A field that errors for a large share of visitors is rarely full of careless people; it is asking an unclear question, demanding an unforgiving format, or sitting in the wrong place in the layout from the layout guide. Fix the field's question or format first and the message second. Fewer errors beats better errors, every time; the messages exist for the residue that honest design cannot prevent.
The tone is the brand, under stress
Visitors judge a business by how it behaves when something goes wrong, and a form error is often the first thing that goes wrong in the relationship. A message that helps, in the same voice as the rest of the site, quietly proves the promise the microcopy makes: this business is careful with people. A message that blames - You entered an incorrect email - spends trust the business has not earned yet. Read your five most common error messages aloud, as if to a frustrated customer on the phone. If you would soften any of them in speech, soften them in the form.
Sources and evidence on the record
- W3C, Web Content Accessibility Guidelines - the accessibility standard behind the form, error-message and mobile guidance.
- Nielsen Norman Group, articles - usability research on reading behaviour, forms, response times and navigation.
Evidence basis: Research-led guide. Figures are attributed to the published sources listed below and carry their check date; the method sections are the desk's, the numbers are the sources'. Applies when: Every form with validation, and every form tool change