Protocol
Make the error show the next repair
Invalid is a verdict, not an instruction.
When it fits
- A form rejects input but leaves people guessing what to change.
When to avoid it
- Do not reveal private account information through detailed errors. Avoid blaming the user for network failures or conditions they cannot repair.
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
- Describe the specific problem the system can actually detect.
- Show where to fix it and give an example or constraint when useful.
- 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?
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.
Connected ideas
Useful withAnnounce the result without stealing the user’s place
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.