Level
AA
Since
WCAG 2.0
/ WCAG criterion

3.3.3 Error Suggestion

When a form detects a mistake and knows how to fix it, it must tell the person how, unless that would undermine security or the purpose of the content.

/ What it requires

3.3.1 makes sure people learn that something is wrong. This criterion makes sure they learn how to put it right. When the system detects an input error automatically and knows a correction, it has to offer it: the expected format, the allowed values or the value the person most likely meant. An input error is information the user provided that is not accepted, and that includes a required field left empty. Without a suggestion, people with cognitive disabilities may not work out the fix, blind users may never find the example printed under the field, and many abandon the form.

The requirement has two conditions and one exception. It applies only when the error is detected automatically and a suggestion is known; a system that cannot know the right answer has nothing to suggest. It does not apply where a suggestion would jeopardize the security or the purpose of the content: a login form does not hint at the correct password, and a test does not reveal the right answer. The suggestion may come from the author or from the user agent, so a browser message that says what is missing can meet it.

/ How pages fail it

  • A date field rejects 5/11/2026 with the message "Invalid date" and never states the format it accepts.
  • A postcode field says "Wrong postcode" although the system knows the pattern is 00-000.
  • A required field left empty turns red with the word "Error", and nothing says what belongs in it.
  • A new password is checked against rules such as a minimum length and a digit, and the message only says "Password not accepted".
  • A field that accepts a fixed list of values, such as a month or a country, rejects a misspelling without offering the closest match or the list.

/ How to check it yourself

  1. Submit each form with typical mistakes: empty required fields, wrong formats, values out of range and misspellings. Use a test account or a test environment where a real submission would place an order.
  2. For every message, ask whether it says how to correct the entry, not only that it is wrong.
  3. Where a message suggests nothing, decide whether the system could know a fix. A required format, a range or a list of allowed values means it could.
  4. Where a hint is withheld, check that security or the purpose of the content is the reason, as with a password or the answer to a quiz.
  5. Repeat with a screen reader such as NVDA and check that the suggestion is read when the error is announced or when the field receives focus.

/ How to fix it

  • Write the message as the fix: "Enter the date as DD.MM.YYYY, for example 05.11.2026" instead of "Invalid date".
  • For a field with a limited set of values, list the allowed values or offer the nearest match, as in "Did you mean December?".
  • Reuse the format hint shown under the field in the error message, and connect both to the input with aria-describedby.
  • When a field uses the pattern attribute, the browser can only say that the format does not match. State the expected format in the hint or in your own message.
  • Use the security exception only where a hint would help an attacker, such as the correct password. The rules for creating a new password are not a secret and belong in the message.

/ What our scanner checks

No automated check in our scan judges whether an error message suggests a fix, because that is a question about words. In the browser extension the form drill notices messages that appear when a field is left, and reports them under 3.3.1 and 4.1.3 when they are unconnected or unannounced, but it does not read what they say. It submits nothing, so errors raised by the server are not seen either. A person reads the messages in a manual audit.

/ Who fails it, in our own measurements

The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.

One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.

/ Questions about this criterion

Does Error Suggestion apply to login forms?

Yes, with the exception it names. The criterion does not require a suggestion that would jeopardize security, so a login form need not hint at the correct password. It still has to say what can be said safely, such as that a field is empty or that the email address is missing its at sign.

Is the browser's built-in validation message enough?

It can be. W3C says the description of the error may come from the author or from the user agent. The browser message for an email field without an at sign tells the person what is missing, which is a suggestion. For the pattern attribute the browser can only say the format does not match, so the page has to show the expected format.

What level is 3.3.3 Error Suggestion?

Level AA, part of WCAG since 2.0 and unchanged in 2.1 and 2.2. It applies only when an error is detected automatically and a correction is known, and not when the suggestion would put security or the purpose of the content at risk, as with the answer to a test question.