Designing form error messages that help people finish
A useful form error identifies the field, explains the problem and tells the visitor how to correct it.
AI-assisted practical guide · Editorial approach
The useful starting point
A useful form error identifies the field, explains the problem and tells the visitor how to correct it. Keep entered information intact when safe to do so. Errors should help someone complete a task rather than make them guess which rule failed.
Understand the decision
Review errors for empty, invalid and excessive input, then test delayed or failed server responses. Field messages and an error summary can serve different needs. Move attention to feedback appropriately and do not rely on colour alone. Distinguish an explicit rejection from an uncertain response after submission: a blind new retry could duplicate a request that was already stored.
A practical approach
Choose one visitor task and walk through it on a phone. Read the page without using knowledge of the business: can you explain the offer, its limits and the next action? Then test the complete action with synthetic details in a test environment. Include missing fields, invalid inputs, slow responses, interruptions and retries. A click is a sign of interest; it becomes an enquiry only when the receiving system confirms durable acceptance.
- Name the affected field and correction.
- Preserve safe entered values.
- Make feedback keyboard accessible.
- Distinguish rejection from uncertain acceptance.
Illustrative example
An enquiry form could say that the email address needs a valid format and retain the other fields. If acceptance cannot be confirmed after a timeout, it could keep the same request reference for a retry. That is different from telling the user that nothing was received.
A mistake to avoid
Avoid a generic something went wrong message when a specific correction is available. Also avoid declaring success solely because a submit button was clicked.
What to review
Test whether users can recover from each error and whether retries preserve one durable enquiry rather than creating duplicate records.
Turn the guide into a working brief
Create a short acceptance checklist covering content ownership, keyboard access, error messages, receipt behaviour and the receiving team. Give every unresolved item an owner. Keep the next action proportional to the visitor’s readiness: a practical guide or price explanation may suit someone who is not ready for a sales call. Inspect a few conversations alongside analytics so that a technical event is not mistaken for a useful commercial outcome.
Common questions
What should I prepare before asking for help?
Start with this checklist: Name the affected field and correction. Preserve safe entered values. Make feedback keyboard accessible. Distinguish rejection from uncertain acceptance. Add your business context, existing materials and the decision you need to make. A useful initial brief can include uncertainty; you do not need to invent answers before discussing scope.
How should I judge whether the work helped?
Test whether users can recover from each error and whether retries preserve one durable enquiry rather than creating duplicate records. Keep the observation period and definitions visible. Use the responsible team's evidence alongside the website journey; do not attribute every change in results to one asset or article.
Sources & scope
AI-assisted practical guide. Examples are illustrative; business-specific facts and sector claims need the responsible owner’s approval.
- W3C WAI: Forms Tutorial
Reference for accessible labels, instructions and feedback. Original business examples are illustrative, not research findings or verified client results.
Use this guide to start your brief.
Share your business context, existing materials and what is still unclear. The guide title will be included so the conversation starts with the right problem.
Prefer email? Send a brief with this guide’s context.Related guides
What should a service page include to generate useful enquiries?
A service page should explain the problem it solves, who it suits, what is included, what needs confirmation and the next action.
Read the guide →How many fields should an enquiry form have?
Use the fields the receiving team needs to take the next useful step.
Read the guide →Contact page design for customers who are not ready for a call
A contact page should offer a clear, low-pressure way to describe a need and understand the next step.
Read the guide →