Explain the problem and preserve valid work
A form error should identify the affected field, explain what is wrong and tell the user how to recover. Keep valid entries intact. Distinguish a validation problem from a delivery failure, since the recovery action differs. Make feedback available to assistive technology and avoid relying on color alone to communicate the issue.
Worked example
Illustrative scenario; not a claim of measured client results.
If a phone field rejects a legitimate international number, an error saying Invalid input does not help. Explain the accepted format or improve the validation if the restriction is unnecessary. If the server is unavailable, do not mark a correctly entered email as wrong. State that submission failed and provide a suitable retry or alternative contact route.
Checks, limitations and next decisions
Test empty required fields, malformed values, slow responses and server errors. Confirm that focus and error summaries help users locate the issue, especially with a keyboard. Review the message after correction so stale errors do not remain visible. Good recovery design reduces repeated effort and avoids falsely suggesting that the user caused a system failure.
A practical starting point
Work through these checks in order. Use the results to decide what needs to change in your own workflow.
- Associate the message with the relevant field.
- Use specific language and avoid blame.
- Test recovery with keyboard and assistive technology.
A mistake to avoid
Do not rely only on color to identify a failed field.
How to check progress
Track abandonment after errors and verify that users can correct them successfully.
Your action checklist
Use this checklist while reviewing your own setup. Checkmarks are temporary and stay in this open page.
For the wider decision process, read Reducing friction in a project enquiry form.
Further reading
W3C: form success and error notifications provides relevant platform or accessibility guidance.
Official background resources for this topic. The workflow above is general guidance, not a guarantee of a particular result.
AI-assisted editorial content. Examples are illustrative, not client case studies. Read our editorial policy or report a correction.