Centsbot · audit · samples · guides

Signup form error messages review: stop losing signups at the last step

"Invalid input." "Error 422." "Password does not meet requirements." A visitor who reached your signup form already wants in; a vague or scolding error message is often what makes them leave. This page covers sourced guidelines for error messages, the WCAG rule, a rewrite checklist, and a $19 review that gives you 3 copy fixes within 24h.

Free observation first — not ready to pay? Send your URL and get 1 concrete observation on your page, free, no account. Request your free observation →

What makes a good error message

Nielsen Norman Group's Error-Message Guidelines say to "Design effective error messages by ensuring they are highly visible, provide constructive communication, and respect user effort." Concretely: "Display the error message close to the error's source", "Use human-readable language", "Preserve the user's input", and "Take a positive tone and don't blame the user", avoiding words like "invalid, illegal, or incorrect."

The accessibility rule

The W3C's Understanding Error Identification states WCAG 2.1 success criterion 3.3.1: "If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text." A red border alone isn't enough.

Rewrite checklist for your signup form

Say what to do, not what went wrong. "Use at least 8 characters" instead of "Invalid password".
Show rules before the error. Put password or format rules under the field from the start.
Put the message next to the field, in text, not only colour. See the accessibility review.
Keep what they typed so they fix one field, not the whole form.
Remove fields you don't need; fewer fields means fewer errors. See the checkout friction review.

Validation logic is your developers' job; these tips are about the words and their placement.

Fewer fields also means fewer errors to write. See the signup form field count review for what NN/g and Baymard found.

Password typos before Submit? See the show password review for NN/g guidance on masking.

Still shipping Clear Form next to Submit? See the Reset button review for NN/g guidance.

What the $19 review gives you

We read your live page and pick the 3 gaps most likely to cost you signups. You get 3 before → after rewrites (hero, CTA, offer or proof), each with a one-line reason and a metric hypothesis you can check later, ready to paste, within 24h of 1 BTC confirmation. No call and no account. See an example deliverable (excerpt from a public sample) or browse all public samples.

Honest limits: we review the public page you send (we can't see errors behind a login or test your validation code), and we don't promise a lift. If your form copy is among your 3 highest-impact gaps, the fix rewrites the labels, hints or messages. For a full testing program, see audit vs CRO agency.

$19 · 3 fixes · delivered within 24h · paid in BTC

You get a BTC invoice page with address, amount, a QR code and an open-in-wallet link. Work starts once payment is seen. Not sure yet? Ask for 1 free observation on /audit.

FAQ

Why do form error messages matter for signups?

A visitor who hits a confusing error on your signup form is one step from converting and may give up. Nielsen Norman Group advises error messages that are highly visible, provide constructive communication, and respect user effort.

Where should an error message appear?

Nielsen Norman Group says to display the error message close to the error's source, so users can connect the message with the field that needs fixing.

Should I clear the form when there is an error?

No. Nielsen Norman Group recommends preserving the user's input, so people can correct errors by editing their original action instead of starting over.

What does WCAG require for form errors?

WCAG 2.1 success criterion 3.3.1 (Error Identification) says that if an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

What do I receive for $19?

3 before and after rewrites for the highest-impact spots on your page (hero, CTA, offer or proof), each with a one-line reason and a metric hypothesis, ready to paste, within 24h of 1 BTC confirmation. No call and no account.

Questions: [email protected]