Loading...
Loading content...
Loading content...
Suggest fixes for errors when possible (e.g., 'Did you mean...?').
Why it matters: Helps users correct mistakes quickly and easily.
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.
What This Means: This success criterion requires that when form validation detects an input error and the system knows how to correct it, suggestions for correction should be provided to the user. For example, if a user enters an invalid email address, the system might suggest 'Did you mean example@email.com?' This helps users correct mistakes quickly and easily.
Why It's Important: Providing error suggestions helps users understand what went wrong and how to fix it, reducing frustration and form abandonment. This is especially helpful for users with cognitive disabilities who may struggle to identify and correct errors. Error suggestions can also help all users by providing clear guidance on expected formats or valid values.
When errors are detected and correction suggestions are known, provide them to users. For example, suggest valid email formats, correct spelling, or valid date formats. Use clear, helpful language like 'Did you mean...?' or 'Please use the format: MM/DD/YYYY'. However, don't provide suggestions if they would compromise security (e.g., password hints) or the purpose of the content.
This criterion ensures that users with cognitive disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
This criterion ensures that all users can access and understand the content, improving their overall experience and ability to use the website effectively.
Impact: When this criterion is properly implemented, it removes barriers for these user groups and creates a more inclusive web experience for everyone.
This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 3.3.3 Error Suggestion are met. Check off items as you complete them.
Note: These are official W3C resources for 3.3.3. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 3.3.3 Error Suggestion correctly requires understanding your specific context. Code solutions vary significantly based on multiple factors:
HTML, React, Vue, Angular, PHP, Python, and other frameworks each have different patterns and best practices.
Server-side rendering, client-side rendering, static generation, and hybrid approaches require different solutions.
Your existing components, styling approach, and UI library influence how accessibility must be implemented.
Your specific user base, content type, and interaction patterns determine the most appropriate implementation.
We provide tailored implementation guidance by analyzing your specific technology stack, coding patterns, design system, and project requirements. Our team reviews your codebase and provides custom solutions that integrate seamlessly with your existing architecture.
Get Custom Implementation HelpPart of
Understandable PrincipleGuideline
3.3 Input Assistance