WCAG 2.2 (A) SC 3.3.7 Redundant Entry

WCAG 2.2 (A) SC 3.3.7 Redundant Entry (w3.org)

Issue description

WCAG 3.3.7, “Redundant Entry” aims to reduce the burden on users when filling out forms by minimizing the need to enter the same information multiple times. This is particularly beneficial for people with cognitive disabilities who may have difficulty remembering or recalling information, as well as users with motor impairments who may find repetitive typing tasks challenging.

Many websites require users to enter the same information multiple times within a form or across different forms. This can occur when:

Repeated fields: Forms have multiple fields that request the same information (e.g., asking for email address twice for confirmation).
Multiple forms: Users need to fill out similar forms on different pages or sections of the website.
Lack of pre-filling: Forms don’t pre-fill fields with information the user has already provided.

Why SC 3.3.7 redundant entry matters

Reduced cognitive load: Minimizing redundant entry reduces the mental effort required to complete forms, especially for users with cognitive disabilities.
Improved efficiency: It saves users time and effort by avoiding unnecessary repetition.
Reduced errors: It can help prevent errors that might occur when users have to re-enter the same information multiple times.
Enhanced user experience: It creates a more streamlined and user-friendly experience for everyone.

WCAG requirements

This guideline requires that information previously entered by the user is either:

Automatically populated: The information is automatically populated in the form fields where it is needed.
Available for the user to select: The user is provided with a mechanism to select and insert the previously entered information.

Essentially, this guideline promotes efficiency and reduces user burden by minimizing the need for repetitive data entry. This benefits all users, especially those with cognitive or motor impairments who may find repetitive tasks challenging.

Who this issue impacts

Follow the links for additional information on user impairments:

Suggestions for remediation

Remediating WCAG 3.3.7, “Redundant Entry” involves minimizing the need for users to enter the same information multiple times within a form or across different forms on your website. Here’s how:

Prefill form fields

Store user data: Store user data securely, such as their name, address, and contact information, so that it can be pre-filled in subsequent forms.
Auto-populate fields: When a user encounters a form that requires information they have previously provided, automatically populate the relevant fields with their stored data.
Provide options to update: Allow users to review and update the pre-filled information if necessary.

Offer autofill and browser autofill

Enable autofill: Ensure that your forms are compatible with browser autofill features, which allow users to store and automatically fill in their information across different websites. This is done with the input autocomplete attribute.
Provide clear labels: Use clear and descriptive labels for form fields to help browsers accurately identify and pre-fill the information.

Use data storage and retrieval mechanisms

Client-side storage: Use browser storage mechanisms, such as local storage or cookies, to store user data for pre-filling forms.
Server-side storage: Store user data on the server and retrieve it when needed to pre-fill forms.
User accounts: If your website has user accounts, store user information in their profiles and use it to pre-fill forms.

Minimize repeated fields

Avoid unnecessary repetition: Avoid asking for the same information multiple times within a single form, unless it’s essential for confirmation or security purposes.
Conditional fields: Use conditional logic to show or hide fields based on previous answers, reducing the number of fields the user needs to complete.

Testing

Test different scenarios: Test the forms with different user scenarios to ensure that information is pre-filled correctly and that users can update it if needed.
Assistive technology testing: Test with screen readers to ensure that pre-filled information is announced correctly and that users can easily navigate and edit the fields.

Examples

E-commerce checkout: Pre-fill the billing and shipping address fields with the user’s saved information from their account.
Contact form: If the user has previously filled out a form on the website, pre-fill their name and email address.
Registration form: If the user has started filling out a registration form but didn’t complete it, save their progress and pre-fill the fields when they return.

By implementing these techniques, you can reduce the burden on users by minimizing repetitive data entry, making your forms more efficient and user-friendly for everyone, especially those with cognitive or motor impairments.