A customer fills in an enquiry form, presses send and sees “Something went wrong.” Which detail needs changing? Was anything submitted? Should they start again? A short message can leave a surprisingly large amount of work for the person trying to contact you.
When reviewing a website, deliberately try the paths that fail. The useful question is whether a customer can understand the problem and take the next appropriate step without guessing. Begin with the errors people can correct, then separate them from problems the website itself needs to resolve.
Make a small error inventory
Ask your developer to list the conditions that can stop the form. These might include an empty required field, an address in an unsupported format or a file larger than the configured limit. The list should reflect the actual implementation. Do not invent restrictions simply because a familiar form uses them.
For each condition, record the field label, what the system rejects, the message shown and the action that should resolve it. Add a place to record the observed result of a test. That last column matters: a written intention is not evidence that the website behaves that way.
Keep system failures on a separate list. A service being unavailable is different from an incomplete field. Asking someone to correct their email address when the server cannot process requests sends them towards the wrong fix.
Say which detail needs attention
W3C’s Error Identification guidance explains that an automatically detected input error needs to identify the affected item and describe the error in text. A coloured outline can support that explanation, but should not carry the whole message.
Consider a fictional service enquiry form with a required contact email. “There is an error” leaves the visitor searching. “Enter your email address” points to a specific missing detail. If an address has been entered but does not match the accepted format, use a different explanation that reflects that condition.
The examples here are invented review material, not wording tested on a client website. Before adopting any message, compare it with the field’s visible label and the actual validation rule. Calling the same field “contact address” in one place and “email” in another creates an avoidable interpretation task.
Give a correction the form accepts
W3C’s Error Suggestion guidance says to provide known correction suggestions for detected input errors unless doing so would compromise security or the content’s purpose. That exception matters: helpful wording should not disclose protected account information.
For an ordinary public enquiry form, a useful suggestion could explain an accepted file type or give a format example. Confirm the rule first. A message that tells someone to upload a PDF is misleading if the implementation accepts only image files.
Try the suggested correction yourself in a test environment. Does it actually clear the error? Does it reveal another requirement that could have been explained earlier? If a phone field unnecessarily rejects spaces or brackets, ask whether the restriction should change rather than making customers work around it.
Put the explanation where people can use it
The GOV.UK error-message component pairs an explanation of what went wrong with how to fix it. Its patterns are guidance for government services, not proof that a small-business implementation is accessible. They provide useful questions for your own review.
Ask the developer to demonstrate the relationship between the field and its error message. A person using a screen reader should not have to discover an unrelated warning at the bottom of the page. Someone using a keyboard needs a workable route to the affected control and back through the form.
On a narrow screen, check whether the explanation stays readable beside the relevant field. Increase text size and inspect long messages. A warning hidden behind a sticky footer, clipped container or disappearing pop-up may look acceptable in a screenshot while being difficult to use during the task.
Protect the work already entered
After a failed attempt, inspect the unaffected fields. Have the customer’s ordinary enquiry details disappeared? Do selected options reset? Does a file need to be chosen again? Decide what should remain and explain any step that must be repeated.
Preserving useful input during correction is a design recommendation, not permission to store everything indefinitely. Ask the developer how the form handles that information and avoid adding persistent storage merely to solve a temporary error state. Sensitive information needs its own handling decisions.
Also test two errors together. Correct one and submit again. The remaining message should still make sense, and the corrected field should not continue to look broken. Record the exact steps when this fails so the developer can reproduce the problem.
Treat an uncertain submission honestly
A connection problem can leave the result unclear. The interface should not say “Nothing was sent” unless the system knows that, or “Received” merely because the person pressed the button. Ask what evidence the application has when it chooses each message.
Agree on a recovery route appropriate to the service. That may be a supported retry or a verified alternative contact method. Do not promise that retrying cannot create a duplicate unless the implementation has been checked for that behaviour. Keep technical diagnostics out of customer-facing copy while retaining enough information for the team to investigate safely.
Review a complete correction journey
Give a reviewer a fictional enquiry and a deliberate mistake. Ask them to submit it, explain what the message means and correct it without coaching. Observe where they pause or lose information. This is a proposed check, not a claim that usability testing has already taken place.
Save the test conditions, observed result, needed fix and person responsible. Repeat the relevant cases after a form change. Clear copy and working behaviour need to agree; neither alone proves a successful recovery or full accessibility conformance.
To discuss a website project with ZXP, bring the form and examples of messages customers encounter. A short list of failed attempts gives the conversation a concrete starting point.
Sources & references
- 01
- 02
- 03Error message
GOV.UK Design System
A perspective from the ZXP team.
Designed to help you ask better questions and take a clearer next step.



