Skip to content
Motif UI
Go Pro
Craft

Writing error messages that name the fix

An inventory of this site's own error copy, graded by one rule: does the sentence tell the reader what to do next?

Beginner1 min read (computed · recorded 6)updated 2026-09-12copyerrorsa11y

by Motif Editors

revised 2026-09-12 — First publication in bank-3 batch 4.

Part 3 of 3 in The review craft← Design review for engineers

Key takeaways
  • — Name what happened, what it means for the task, and the next step.
  • — Screen readers read errors cold: plain words, no sarcasm.
  • — The best error copy you ship is the build-fix note in a run log.

The rule

'Something went wrong' is a status, not a message. A message names what happened, what it means for the reader's task, and the one next step. Three clauses, one sentence if you can.

The inventory

  • Form error: name the field, the rule, an example. '+44 7700 900123' beats 'invalid phone'.
  • Empty result: 'No components match “xyz” — clear filters or try the tag cloud.' Two exits, stated.
  • Load failure: say it is a failure, show retry, and keep the layout so nothing shifts when content arrives.
  • Build error in a run log: the model's failure note includes what fixed it — the site publishes these because they are the most-read copy it has.

Tone is accessibility

Screen readers read errors cold, without the surrounding mood. Plain words, no sarcasm, no 'oops'. The reader who hears your error has not seen your friendly illustration.

Words this guide uses that the glossary defines: Run log

Practise the lesson

Theory sticks when you ship it. These original Motif assets put this guide's lesson to work — open one and copy it into your own page.

Error SummarypracticeShake-on-error FieldpracticeError Boundary Cardpractice
Keep learning
All guidesTry the interactive Lab