An error message should identify the problem and explain a useful next step. It should appear where the person can connect it to the relevant field or action. A generic failure message gives little help when several inputs might be responsible.

A practical approach

Preserve valid information when an error occurs. Requiring someone to re-enter a long enquiry because of one invalid field creates unnecessary work. Test both field validation and failures outside the visitor’s control, such as a temporarily unavailable submission service.

Your checklist

  • Explain the specific input that needs attention.
  • Keep existing valid entries where possible.
  • Provide a realistic alternative when submission is unavailable.

For example

If a phone field rejects an international number, the message should not merely say invalid. The field rules may need correction; a more detailed message cannot rescue an unnecessarily restrictive requirement.

Planning a project? Explore our website design or tell us what you need.