Error Suggestion: Help Users Fix Form Errors
Also called: Error correction suggestions, Correction hints, Helpful error messages
Definition
Error suggestion means that when a website detects an input error and knows how it could be corrected, it offers that correction to the user. WCAG 3.3.3 requires it at Level AA, unless it would jeopardize security or the purpose of the content.
Error suggestion is the step after the error message: the form does not only say that something is wrong, it says how to put it right. "Invalid date" leaves people guessing, while "Please enter the date as DD.MM.YYYY, for example 05.03.2026" gets them through the form. Correction hints like this are one of the cheapest ways to reduce abandoned forms.
What it means
WCAG 3.3.3 Error Suggestion (Level AA, WCAG 2.2) reads: "If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content."
It builds on error identification (3.3.1), which makes sure people notice the error at all. W3C explains why the extra step matters: some people, including people with cognitive or visual disabilities, know that an error occurred but not how to correct it – and may abandon the form.
| Situation | What a good suggestion looks like |
|---|---|
| Wrong format (date, phone, IBAN) | Name the expected format and show an example |
| Value from a limited set (month, country) | List the valid values or ask "Did you mean …?" |
| Value out of range | State the allowed range, e.g. "Choose 1 to 10 tickets" |
| Wrong password or PIN | No hint about the correct value – security exception |
| Quiz or test answer | No correct answer shown – it would defeat the purpose |
W3C's example: a user types "12" in a month field that expects names. The page can list the valid months or ask "Do you mean 'December'?"
Examples
<label for="date">Arrival date</label>
<input id="date" name="date" aria-invalid="true" aria-describedby="date-error">
<p id="date-error">
Error: "5/3" is not a full date. Please use DD.MM.YYYY, for example 05.03.2026.
</p>
<label for="country">Country</label>
<input id="country" aria-invalid="true" aria-describedby="country-error">
<p id="country-error">We don't know "Austira". Did you mean "Austria"?</p>The suggestion sits in the error text, which is linked to the field with aria-describedby, so screen readers read it with the field. Technique G177 ("Providing suggested correction text") describes exactly this.
Say what is expected and give an example, offer the closest valid value ("Did you mean …?"), state allowed ranges, keep what the user typed so there is no redundant entry, and place the hint right next to the field.
Show only "Invalid input", hide the expected format until after a failed submit, reveal parts of a password in the error, or replace the user's entry with a guess without telling them.
How to check error suggestions
Questions
What is the difference between WCAG 3.3.1 and 3.3.3?
3.3.1 Error Identification requires that the error is noticed: the field is identified and the error is described in text. 3.3.3 Error Suggestion adds how to correct it, whenever the website knows a correction.
Do I have to show the correct password when a login fails?
No. The criterion has an exception when a suggestion would jeopardize the security or purpose of the content. A login can say that the email or password is incorrect without saying which one or what it should be.
Is a format hint before typing enough?
A hint at the field helps everyone and is good practice, but the error itself should also say how to fix the entry. When the message appears, repeat the expected format or give an example.
Is error suggestion required by the European Accessibility Act?
The European Accessibility Act points to EN 301 549, which takes over WCAG Level AA for websites. 3.3.3 is Level AA, so it belongs to the requirements most websites in its scope are measured against.
Related terms
Error Identification: Clear Form Error Messages
Error identification means that when a website detects an input error automatically, it points out the field in error and describes the problem to the user in text. It is required by WCAG 3.3.1 at Level A.
Read definition: Error Identification: Clear Form Error MessagesForm Labels: Clear Labels and Instructions
Form labels are the visible texts that name what a form field expects, such as “Email address”. WCAG 3.3.2 requires labels or instructions wherever content asks for user input, including formats and required fields.
Read definition: Form Labels: Clear Labels and InstructionsARIA Live Regions: Announce Status Messages
An ARIA live region is a part of the page marked with aria-live or a live role such as status or alert. When its content changes, screen readers announce the new text without the user having to move focus to it.
Read definition: ARIA Live Regions: Announce Status MessagesRedundant Entry: Don't Ask for the Same Data Twice
Redundant Entry is WCAG success criterion 3.3.7. Information a user already entered or was given in the same process must be auto-populated or available to select when it is needed again – unless re-entry is essential, needed for security or the information is no longer valid.
Read definition: Redundant Entry: Don't Ask for the Same Data Twice