Loading article…

Table of Contents

Quick Answer: How should a form error help the user recover?

An effective form error identifies the affected answer, describes the problem and gives a correction the visitor can make. When the website cannot confirm a submission, give recovery instructions that match the known status.

  1. Name the field or step in plain language.
  2. Explain how to fix the actual problem.
  3. Keep valid answers and make the error easy to find with a keyboard.
  4. Verify the corrected request reaches the confirmation state once.

Test invalid values and service failures separately because they need different messages.

Form error messages and accessible recovery checklist
Form error messages and accessible recovery checklist

“Something went wrong” leaves a visitor guessing whether to edit a field, try again or wait. Start by determining what the website knows. Then give the visitor one safe next step for that state.

Tell the User Which Answer Needs a Fix

If the project size is missing, say “Enter the approximate project size” and give the unit or range the service accepts. If the value uses a recognizable format the website can interpret safely, accept it instead of creating extra correction work. In WCAG 2.2, the error identification criterion calls for automatically detected input errors to identify the item and describe the issue in text. [1] Include that information even when the field also has a visual error style.

Use the same terms as the field label. A hypothetical event enquiry might ask for “Event date.” If the person chooses a date in the past, use “Choose an event date today or later” when the system actually accepts both. Review required and optional fields so instructions match the fields the visitor must complete.

Separate Invalid Inputs From Service Failures

An eligibility issue needs a different response from a missing answer. If the service cannot cover a postcode, explain the service area or give an alternative route. Avoid asking people to re-enter a valid postcode when changing the value would misrepresent their location.

If the system confirms the request did not save, tell the visitor it was not sent and give a safe retry or contact route. If a timeout leaves the result uncertain, explain that the website could not confirm the status. Where supported, a status check or retry tied to the original attempt can recover it without creating a second request. Show a confirmation only when there is a verified record.

Keep Answers and Make Recovery Accessible

Put a specific message near the affected field. When several fields fail, a summary with links can help visitors find each one. The GOV.UK Design System’s error-summary pattern uses a summary even for a single validation error, moves keyboard focus to the summary and links to the corresponding answers using wording that matches the inline errors. [2] Verify that focus, links and messages work with the actual form and assistive technology.

Preserve entries that are safe to keep. A form may have to ask for sensitive input again or require a file to be selected a second time. Explain that immediately and retain the rest. With multi-step forms, send users back to the relevant step and confirm unrelated answers are still present.

Test How People Recover

Submit with two invalid fields using only the keyboard. Check where focus lands, whether the message names the problem and what changes after each correction. Simulate a server rejection and both timeout outcomes. If a request was saved, retrieve its original reference. If nothing was saved, verify that a retry creates one request. Then verify which record was saved and whether the next step produces a duplicate.

If tracking recovery, divide distinct attempts that recover and reach acceptance by distinct eligible attempts that encountered that error and had the full time allowed to finish. Count each attempt once. Track unresolved service failures separately from validation errors so a site outage does not look like confusing field copy.

Verify Error Messages in Each Language

If your WordPress forms serve multiple languages, evaluate StagLingo on a representative form. Test actual errors and verify the instruction matches the input format in each version.

Explore StagLingo and trial options

FAQs About Form Error Messages

Should errors appear before submission?

Use early validation when feedback can help with the current task. Avoid showing an error before the visitor had a reasonable chance to finish typing. Always check the submitted value against the actual requirements.

Should the same message appear next to a field and in a summary?

Use consistent wording in both places when a summary is present. The summary helps the visitor find the problem and the inline message helps them fix it.

What should a form say after a network timeout?

State that the result could not be confirmed and provide a status or help route if you have one. Retrying should preserve the original attempt where possible so the visitor does not send a duplicate.

Sources

[1] W3C Web Accessibility Initiative. Understanding Success Criterion 3.3.1: Error Identification

[2] GOV.UK Design System. Error summary