Level AAUnderstandable
3.3.3

Error Suggestion

When you can tell what someone meant, suggest the fix, not just 'invalid', but 'the date should be MM/YYYY'.

In plain English

Identifying an error is step one. Helping fix it is step two. If someone enters a date in the wrong format and you can tell what they meant, do not just say “invalid”, tell them the format you need: “Enter the date as MM/YYYY.” The more specific and helpful the message, the faster people recover, and the fewer abandoned carts you get.

The only time to hold back is when a suggestion would hurt security, like revealing which half of a login was wrong.

Who this is for

  • Everyone filling in a form, who recovers faster with a clear suggestion.
  • Screen-reader users, who benefit most from precise, spoken guidance.
  • People with cognitive differences, for whom vague errors are a wall.

What “good” looks like

Say what is wrong and how to fix it.

Bad:   "Invalid input."
Better: "Enter a valid email address."
Best:  "Enter a valid email address, like you@store.com."

Bad:   "Wrong format."
Best:  "Enter the expiry date as MM/YY."

Where stores get it wrong

Checkout errors that say only “invalid” or “error”, format requirements revealed only after you get them wrong, and no guidance on how to correct a field. Pairing a clear suggestion with proper error identification removes a big source of checkout drop-off and appears on the common failures list.

How to meet it

Techniques the W3C accepts as sufficient (summarized). Follow a link for the full method.

Frequently asked questions

What does error suggestion require?+

Success Criterion 3.3.3 (Level AA) says that when an input error is detected and you know how to fix it, you should suggest the correction to the user, unless doing so would risk security or defeat the purpose of the form.

How is this different from 3.3.1 Error Identification?+

3.3.1 (Level A) requires telling people that a field is wrong and which one. 3.3.3 (Level AA) goes further: when you can, tell them how to fix it. 'Enter a valid date' identifies the error; 'Enter the date as MM/YYYY' suggests the fix.

When can I skip the suggestion?+

When suggesting a correction would compromise security (for example, you should not say which part of a password or login was wrong) or when the correct value genuinely cannot be known.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 3.3.3?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit