Designers
ToolsDocsProAll the Possibles

All 141 tools / Interface writing and content

Find error and status messages that blame, give no next step or vanish too fast, and get a fix template

Error message checkFreeFor writers, designers and product teams

25/day

free runs a day, no sign-in.

Before: what you give it

The example input, as typed in. You paste text, CSS, markup or notes.

messages: ["That address does not look right.","Error 500","You entered an invalid password.",{"text":"Saved your changes.","where":"toast"},"That address does not look right. Check it for typos and try again."]

After: what comes back

The first lines of a real run on that input. Nothing here is edited by hand.

Checked 5 messages: 3 to fix, 1 to review, 1 fine.

FIX: "That address does not look right."
  [HIGH] no-next-step (WCAG 3.3.3 Error Suggestion): Says what went wrong but not what to do next. Add one step starting with a verb.
  Template (wrong format): {Field name} is not in a form we can read. Use {format rule}, for example {example}.
FIX: "Error 500"
  [HIGH] code-only (WCAG 3.3.1 Error Identification): A code is not a description. Say in words what failed.
  Template (code only): {Plain description of what failed, naming the thing the person was doing}. {One step to take now}. Support reference: {code}.
FIX: "You entered an invalid password."
  [MEDIUM] blames-user (Plain-language convention): Puts the fault on the person. Describe what the system needs instead.
  [HIGH] no-next-step (WCAG 3.3.3 Error Suggestion): Says what went wrong but not what to do next. Add one step starting with a verb.
  Template (wrong format): {Field name} is not in a form we can read. Use {format rule}, for example {example}.
REVIEW: "Saved your changes." (shown in: toast)
  [LOW] not-an-error (Note): Reads as a status or success message, so next-step and vanishing checks were skipped.
... full output on the tool page

What you get

Each message rated fix, review or fine, with the WCAG criterion, the reason, and a rewrite template

What it cannot do

Judges the wording and timing you supply; it cannot see how the message is shown or announced in the live interface.

Who it is for

  • Writers
  • Designers
  • Product teams

Free and Pro

Free25 runs a day per IP address, up to 50,000 characters a run.
ProNo daily limit, 300 requests a minute, up to 200,000 characters a run.

What each plan includes

Use it from your assistant

The tool is called error_message_check. Connect the server once, then ask for it by name or just describe the job. Install steps for each app.

claude mcp add --transport http designers https://designers.allthepossibles.com/mcp
curl -X POST https://designers.allthepossibles.com/api/error-message-check -H 'content-type: application/json' -d '{"messages":["That address does not look right.","Error 500","You entered an invalid password.",{"text":"Saved your changes.","where":"toast"},"That address does not look right. Check it for typos and try again."]}'

Try it here

The form starts with the same example input, so you can run it first and then swap in your own.

More in interface writing and content

All interface writing and content tools