Protocol

Make the error show the next repair

Invalid is a verdict, not an instruction.

About 1 min read

Before you use it

Use when
  • A form rejects input but leaves people guessing what to change.

Keep this limit in mind

  • Do not reveal private account information through detailed errors. Avoid blaming the user for network failures or conditions they cannot repair.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Connect the message to the affected field and explain the correctable problem in plain language. Preserve useful context so the user can repair the entry rather than restart blindly. Test what happens after correction as well as the first error.

Steps

  1. Describe the specific problem the system can actually detect.
  2. Show where to fix it and give an example or constraint when useful.
  3. Submit a corrected value and check that the message and state update consistently.

An example

Instead of Something went wrong, a form says that the end date precedes the start date and identifies the relevant field.

Check your result

Can a user make a valid correction without a moderator translating the message?

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingMake the error show the next repair

Evidence and sources
Supports

WAI guidance calls for errors to be identified and described so users can understand and correct them.

Error wording must not expose sensitive information or claim knowledge the system lacks.

User Notifications · Error notifications and correction guidance.

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details