Better than a good error message is a design in which the error cannot occur.
Heuristic · Nielsen heuristics
Tag
errors
Entries tagged errors, drawn from across the library. Tags cut through the section structure, which is where most of the useful connections are.
11 entries across 3 sections
Type
Category
Level
11 entries
Error messages should say what happened, why, and what to do next, in plain language.
Heuristic · Nielsen heuristics
Restricting what is possible is the cheapest way to prevent an entire class of error.
Principle · Interaction
Checking input at the right moment, which is rarely while the user is still typing.
Pattern · Forms
An interruption that should be reserved for genuinely irreversible actions, because it stops being read when it is routine.
Pattern · Safety
Actions that remove or destroy, which need separation in space, distinct styling and a recovery path.
Pattern · Safety
The screen before there is anything to show, which is a teaching opportunity rather than a gap.
Pattern · Content states
A persistent message tied to a context, which is where anything requiring action belongs.
Component · Feedback
The small pieces of text that do most of the work: labels, hints, empty states, errors and confirmations.
UX writing · UX writing
Say what happened, why if you know, and what to do next, in that order and in plain language.
UX writing · UX writing
Errors must be identified in text, described specifically, and accompanied by a suggested fix where one is known.
Accessibility · Understandable