Resource guide
3.3.3 Error Suggestion
When an input error is detected, suggestions for correction must be provided where possible.
By Calling All Minds·Last updated April 2026
Success criterion
Conformance level
Legal standard — required for EAA compliance.
What it means
It is not enough to tell users that an error has occurred. Where possible, the error message must also suggest how to fix it.
This goes beyond 3.3.1 (which requires errors to be identified and described) by requiring actionable guidance. If a postcode is in the wrong format, say 'Enter a valid UK postcode in the format SW1A 1AA', not just 'Invalid postcode'.
In practice
Write error messages that explain both what went wrong and how to correct it.
If a date is entered in the wrong format, show the correct format in the error: 'Please enter the date as DD/MM/YYYY, for example 25/12/2026'.
If a password does not meet the required criteria, list the criteria in the error message.
Do not expose security-sensitive suggestions, such as 'password must be at least 8 characters' before an attempt is made, but do provide this information in the error response.
Common failures
- Error message that says 'Invalid input' with no indication of what valid input looks like
- Password error that says 'Password too weak' without explaining what the requirements are
AXS Audit
AXS Audit checks your site against 3.3.3 and flags issues your team can act on straight away. It covers criteria that automated scanners often miss.