Redundant Entry
Summary:
WCAG 3.3.7, "Redundant Entry," focuses on reducing the need for users to re-enter information that has been previously provided or is available within the system. This guideline is particularly helpful for users with cognitive impairments, motor disabilities, or anyone who finds repeated data entry challenging or tedious.
What:
This criterion requires websites and applications to minimize instances where users have to input the same information multiple times, especially in processes where the user's information is already known or has been entered earlier.
Why:
Requiring users to repeatedly enter the same information can be frustrating and error-prone. Reducing redundant data entry enhances the usability and accessibility of web content, making interactions smoother and more efficient.
Examples and Scenarios:
- E-commerce Checkout: Automatically filling in billing and shipping information for returning customers.
- Online Forms: Carrying forward information from one part of a form to another when relevant.
- Account Registrations: Using previously provided data to pre-fill fields in related services or forms.
How to Comply:
- Websites: Implement functionality that remembers user input and auto-fills it where appropriate.
- Mobile Apps: Utilize user data stored within the app to minimize the need for re-entering information.
- Software Applications: Provide features that allow for the reuse of previously entered data in different parts of the application.
Exceptions:
- Security Measures: Situations where re-entering information is necessary for security verification, like re-entering a password for account changes.
- Data Accuracy: In cases where confirming the accuracy of critical data is necessary, such as in medical or legal forms.