Loading...
Loading content...
Loading content...
Don't make users re-enter information they've already provided in the same session.
Why it matters: Re-entering data increases cognitive load and error potential.
Information previously entered by or provided to the user is auto-populated or available for selection.
What This Means: This success criterion requires that information that users have already entered or provided in the same session should be auto-populated or available for selection, rather than requiring users to re-enter it. This reduces cognitive load and the potential for errors.
Why It's Important: Requiring users to re-enter information they've already provided increases cognitive load, takes more time, and increases the likelihood of errors. This is especially problematic for users with cognitive disabilities or memory impairments who may struggle to remember what they've already entered. Auto-populating or making previously entered information available for selection improves the user experience and reduces errors.
Auto-populate form fields with information users have already provided in the same session. Make previously entered information available for selection (e.g., dropdown lists of previous entries). Use browser autocomplete features. Store and reuse information within the same session. Don't require users to re-enter information unnecessarily.
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 users with memory impairments 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.7 Redundant Entry are met. Check off items as you complete them.
Note: These are official W3C resources for 3.3.7. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 3.3.7 Redundant Entry 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