Understanding WCAG SC 3.3.7 Redundant Entry
Version and Level: 2.2 (Level A)

This success criterion requires that information previously entered by or provided to the user, which is needed again in the same process, should be auto-populated or made available for selection. This minimizes the need for users to re-enter the same information multiple times, reducing the cognitive load and physical effort required.

Benefits:

  1. Reduced Cognitive Load: Helps users with cognitive and learning disabilities by minimizing the need to remember and re-enter information.
  2. Increased Efficiency: Saves time and effort for all users, especially those with limited mobility using alternative input mechanisms.
  3. Enhanced User Experience: Improves the overall experience by streamlining processes and reducing redundancy.

Main Objective:

To simplify processes and enhance user experience by minimizing the need for users to repeatedly enter the same information, especially beneficial for those with cognitive and short-term memory challenges:

In multi-step forms where users interact with various inputs, specific fields or data entries may reappear on subsequent pages. Re-entering the same information can be cumbersome. To address this, we employ techniques such as automatic or optional field population. For example, in a phone provider's multi-step form, if a user's phone number is required in one step and then again on a following page the company’s main contact’s phone number is required, a checkbox labeled "Use the same phone number as entered in the previously" is provided.

Authors must ensure that information is not stored beyond the user's session to protect privacy and comply with security guidelines, especially if sensitive information is used. If a user's session expires due to inactivity, all stored details should be promptly deleted from the website.

It's crucial to highlight that relying only on autocomplete features is insufficient to meet these success criteria, as they may not address all essential user scenarios and security concerns.

There are instances where re-entering specific data is necessary. For example, if a password is required again to verify the user's identity, such sensitive information should not be stored for security reasons, necessitating the user to re-enter it when prompted.

Best Practices:

  • Auto-populate Fields: Automatically fill in previously entered information when appropriate.

  • Minimize Redundant Entry: Where possible, aim to reduce redundant data entries. If certain data or details are not essential, consider minimizing their requirement whenever possible.

  • Provide Selection Options: Allow users to select previously entered information from a dropdown or similar control.

  • Use Checkboxes: For scenarios where the same information may be reused, provide checkboxes to confirm reuse.

  • Maintain Security: Ensure that any auto-population or selection mechanism maintains the security and privacy of user data.

Examples & Explanation:

Example: University Application Personal Information

What Should Be Avoided

A university application form necessitates students to input their personal information, including name, address, and contact details, across multiple sections of the form. Specifically, in the accommodation section, users are required to select the personal information of the contact who will be responsible for their accommodation, including their name, address, and contact details.

Explanation:This approach increases the cognitive load and physical effort required, especially for users with disabilities, leading to frustration and potential errors.

What Should Be Done

The university application form provides a button labeled "Copy information from previous step." When clicked, this button copies the personal information entered in the first section to subsequent sections of the form.

Explanation: By providing a mechanism to copy information from a previous step, the form reduces redundant entry, making the process more efficient and user-friendly. This approach benefits users with cognitive disabilities, limited mobility, and all users by simplifying the form completion process.

Next Up

Expand your knowledge with SC 3.3.8 - Accessible Authentication (Minimum). Learn to ensure authentication is accessible for all users.

Go to SC 3.3.8