‘Error Suggestion’ requires websites to suggest corrections when users make mistakes.
All users make mistakes – they’re only human after all. When they make mistakes on your website (whether it’s their fault or not), they get frustrated.
Input errors are common, especially where fields are mandatory or will only accept input in a specific format. Gong beyond identifying errors to suggesting corrections is particularly helpful to users with cognitive or visual limitations.
How to Pass ‘Error Suggestion’
- You identify input errors and suggest corrections where possible
- When the error is missing a required field, communicate this to the user with a text suggestion.
- If the error is in the format of the input, the suggestion shows the correct format (for example, ‘The date must be in the form DD/MM/YYYY’).
- If the error is because the input needed to be from a limited list of values, provide these values and explain them.
- This guideline builds on 3.3.1 – Identify Errors by adding a requirement to make a suggestion for user input to fix errors.
- Be specific.
- If a user makes an error, provide a list of links that the user can follow to jump back to correct their input.
- Make it easy to re-submit incorrect forms by retaining all correct data.
‘Error Suggestion’ Exceptions
You don’t need to provide suggestions if:
- It would negatively impact data security; or
- It goes against the purpose of the content.
- Error Identification
- Error Prevention (Legal, Financial, Data)
- Error Prevention (All)
- Understanding Success Criterion 3.3.3 (W3C)
Free Developer Resources
Join over 3,700 subscribers on my weekly web accessibility email and get free developer resources like WCAG Checklists and special offers.
Over 600 developers like you have learned more about the Web Content Accessibility Guidelines with my guidebook.