JDDST Website Design How to Design Website Error Messages That Help Customers Finish Their Tasks

How to Design Website Error Messages That Help Customers Finish Their Tasks

Good website error message design tells people what went wrong, where it happened and how to fix it. With that information, visitors can correct one field and finish the task they came for.

Plenty of sites still show red text that says “Invalid input” and nothing else. JDDST is a web design agency that designs and builds websites for businesses. We treat vague messages as a design problem, because each one can cost an enquiry or a sign-up.

This guide covers what user-friendly error messages contain and when form validation should fire. You’ll also learn which wording helps or hurts, plus how to reach visitors on screen readers and keyboards.

Clear Error Messages Tell People the Problem and the Fix

Frustrated person sitting at a desk facing a laptop

Every useful error message names the problem in plain words and then tells the person what to do next. Codes like “Error 400” or “Invalid entry” do neither, so visitors start guessing and often abandon the form.

The fix deserves more space than the problem. The South Australian Government form error guidance advises focusing on how users can fix an issue instead of describing what went wrong. For example, “Enter a postcode with four digits” works better than “Postcode invalid”, since the visitor knows exactly what to type.

Tone carries equal weight in UX writing. In our client form reviews, we rewrite blaming lines such as “You entered the wrong date” as neutral instructions. Blame can put people on the defensive and make them less willing to try again. Before you sign off any message, run it through this short checklist:

  • Name the Problem Field: The message should mention the exact field, such as “Email” or “Postcode”. On a long form, visitors otherwise have to work out which box needs attention. Match the wording to the field label so both read the same.
  • State What the Field Needs: Spell out the required format, length or range. “Use eight or more characters” gives the visitor a clear target. Show rules up front so nobody discovers them only after an error.
  • Use Everyday Words: System codes and developer terms mean nothing to most visitors. Replace labels like “DOB_FORMAT” with “date of birth”. Read each message aloud to catch jargon your team no longer notices.
  • Keep Messages Brief: A visitor should take in the message in a single glance. Aim for one sentence of around 10 words. Move longer explanations into hint text near the field.
  • Stay Calm and Neutral: Avoid blame, sarcasm and jokes, since a frustrated visitor rarely finds them funny. Write each message as a simple instruction that points to the next step. A plain instruction keeps attention on the next step.

Check every existing message on your site against these five points, and rewrite any that fail two or more. Fix messages missing a field name or requirement first, since visitors have nothing to act on until both appear.

Form Validation UX Design: When and Where Errors Should Appear

Once the wording works, timing and placement decide whether visitors see each message at a useful moment. Good form validation UX checks entries at sensible points and places feedback where the eye already rests. The five rules below cover both, starting with when a check should run.

Validate Entries Once Someone Leaves a Field

Inline checks should fire when a visitor leaves a field, an action developers call the blur event. Checking on every keystroke can flag an email address as wrong before the person finishes typing.

Early warnings like these feel like nagging (nobody enjoys a correction halfway through a word). They also pull attention away from the next field in the form.

Ask your developer to run checks on blur and clear each error once the entry becomes valid. Visitors then get feedback after they finish and watch the message disappear as they correct the entry.

Place Each Message Right Beside Its Field

An error message works best directly between a field’s label and its input box. In that spot, visitors never need to scan the page to pair a message with its input.

Distance becomes a bigger problem in mobile design. A message shown at the top of a phone screen can sit a full scroll away from the field that failed. Alongside the message, change the field border to a visible colour and add an icon.

Keep Everything Visitors Typed When a Submit Fails

Wiping a form after a failed submit forces visitors to retype every entry, and some will leave instead. The Australian Government form validation and recovery pattern states that users should not lose the data they entered when a submission fails.

Picture losing a long quote request because of one typo in the phone number. Password fields are the usual exception, since security rules often require clearing them.

To check your own forms, submit each one with a single deliberate mistake. If any correct field comes back empty, your developer will need to keep entered values on reload.

Summarise Errors When Several Fields Fail

When three fields fail and only inline messages appear, visitors have to hunt down a long page. A summary box at the top of the form gathers every problem in one place.

Each item in the summary should link straight to its field. One tap then moves the visitor to the right input, which helps reduce friction on web and mobile alike.

Keep the summary text identical to the inline messages. Visitors read one version of each problem, and your team writes and maintains each message only once.

Show the Expected Format Before a Mistake Happens

Hint text under the label prevents many errors before validation ever runs. A line such as “DD/MM/YYYY” or “Mobile number, starting with 04” tells visitors exactly what to enter.

Placeholder text inside the box handles this job poorly, because it disappears once typing starts. People can forget the format halfway through (a date split across three boxes makes recall harder).

Give every field with a strict format, such as dates, ABNs or phone numbers, a hint that stays visible. Clear hints mean fewer visitors ever see an error at all.

Close-up photograph of a right index finger poised above a keyboard

Which Error Message Wording Helps Customers and Which Drives Them Away?

When an error does appear, the words you choose decide what happens next.

Wording that gives a plain instruction helps visitors finish, while blame and system codes push them to leave. Vague copy is one of the common web design mistakes we see during site reviews. Teams often write it as a placeholder during a build and forget to replace it. Compare these rewrites to see how a few words change the result:

FieldMessage That Drives People AwayMessage That HelpsWhy the Rewrite Works
EmailInvalid inputEnter an email address like [email protected]Shows the exact format expected
Date of birthError: DOB_FORMATEnter your date of birth as DD/MM/YYYYSwaps a code for plain words
PhoneYou entered a wrong numberEnter a 10-digit mobile numberDrops the blame and states the rule
PasswordPassword too weakUse at least eight characters, including a numberLists what a passing password needs

Rewrite blame-based messages first, since many sites still have a “You entered…” line live. Search your form copy for “you” followed by a verb, then turn each match into an instruction. Track completion rates before and after the change, or run A/B testing on your busiest form to confirm the improvement.

Accessible Website Error Messages for Screen Readers and Keyboards

Clear wording only helps if every visitor can perceive it, including people who use screen readers, keyboards or magnification. During our own form testing, we tab through each form without a mouse first, which quickly reveals which errors stay invisible to assistive technology. Three fixes close the largest gaps in accessible website error messages:

  • Announce Errors Out Loud: Screen readers stay silent about new text unless the code tells them to speak. Adding an aria-live region or role=”alert” makes the reader announce each message as it appears. Ask your developer to add one to every error container.
  • Pair Colour With Text: Red borders alone fail many people with colour vision deficiency. Add an icon and begin the message with a written word such as “Error”. Check the result by viewing your form in greyscale.
  • Link Each Message to Its Field: Connecting the message to its input with aria-describedby lets screen readers read the error alongside the label. If the link is missing, users may hear only “Email, edit text” and nothing about the problem. Add the attribute wherever an error can appear.

Free screen readers such as NVDA on Windows and VoiceOver on Apple devices let you check all three fixes. Repeat this usability testing after every form change, because new fields often ship without these attributes.

Person at a desk holding a completed printed form in both hands

Build Error Messages That Improve the Form Experience

With those checks in your routine, the next step is working through your existing forms.

Start with your busiest form, such as a contact or checkout page. Rewrite its error messages using the checklist above, then tab through it with a keyboard and a screen reader. Once that form passes, move on to the next one and add the fixes to your design system so new forms inherit them.

If you manage several sites, a short UX audit of every form will show which messages need work first. JDDST designs and builds websites for businesses that want forms their customers can complete. Contact JDDST to book a form review and keep more enquiries coming through.

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Post