Redundant Entry (WCAG 2.2)

Redundant Entry is WCAG 2.2 Success Criterion 3.3.7, a Level A requirement that prevents websites from asking users to re-enter information they have already provided within the same process or session. When a user has previously entered data, the website must either auto-populate the field with the previously entered value or provide a way for the user to select it, rather than requiring manual re-entry. This criterion was introduced in WCAG 2.2, published in October 2023, specifically to reduce cognitive burden in multi-step processes. It falls under Principle 3 (Understandable) and Guideline 3.3 (Input Assistance), reflecting the goal of minimizing the effort and memory required to complete tasks. The criterion applies within a single process or session. Information from previous sessions (like a past order's address) is not covered, though providing it would be a good usability practice. The focus is on information entered during the current interaction, such as an address entered on step 1 that should not need re-entry on step 3.

Re-entering information is burdensome for everyone and presents a genuine barrier for people with cognitive, memory, and motor disabilities. Each redundant entry point in a process increases the chance of error, frustration, and abandonment. People with memory impairments may not remember exactly what they entered previously and may enter inconsistent information, causing processing errors. People with attention deficits may lose focus during the tedious task of retyping information they've already provided. People with motor impairments experience physical fatigue and pain from unnecessary typing. People with learning disabilities who struggle with spelling may have successfully entered a correct value once and shouldn't be forced to attempt it again. Multi-step forms are a common source of redundant entry. Checkout flows ask for shipping and billing addresses separately. Insurance applications ask for personal details across multiple pages. Job applications require the same contact information in multiple sections. Each redundant entry increases the likelihood that a user, particularly one with a disability, will abandon the process or make errors. The cognitive cost is real. Working memory is limited, and every piece of information a user must recall and retype consumes cognitive resources that could be directed toward understanding the task, making decisions, or verifying their entries.

The criterion requires that information previously entered by the user, or provided to the user by the system, during the same process is either auto-populated or available for selection. The implementation approach depends on the specific scenario: **Shipping and billing addresses:** ```html <!-- Step 2: Billing address with "same as shipping" option --> <fieldset> <legend>Billing Address</legend> <label> <input type="checkbox" id="same-address" checked> Same as shipping address </label> <!-- Fields auto-populated from shipping step, editable if checkbox unchecked --> <label for="billing-street">Street</label> <input type="text" id="billing-street" value="123 Main St"> </fieldset> ``` **Multi-step forms that reference earlier data:** ```html <!-- Step 3: Confirmation page auto-populates from earlier steps --> <p>Sending confirmation to: <strong>user@example.com</strong></p> <p> <a href="#step1">Edit email address</a> </p> ``` **Review pages that need corrections:** When a user returns to a previous step to correct an error, all previously entered data should be preserved. The user should only need to change the specific field that needs correction. **Search refinement:** If a user performs a search and then wants to modify the search, the previous search terms should be present in the search field for editing. **Acceptable methods for preventing redundant entry:** - **Auto-population.** Pre-fill fields with previously entered values. This is the most common and user-friendly approach. - **Selection.** Provide a dropdown or radio buttons that let the user select previously entered values. For example, "Use shipping address" as a billing address option. - **Persistent data.** Keep form data in the session so that navigating back to a previous step shows the previously entered values. **Exceptions to the criterion:** - **Essential re-entry.** When re-entering information serves a critical purpose, such as confirming an email address or re-typing a password for security verification. - **Security.** When previously entered information should not be stored or displayed for security reasons, such as re-entering a credit card CVV. - **Information that has become invalid.** If previously entered information is no longer valid (e.g., a session has expired), asking the user to re-enter it is acceptable. **Implementation best practices:** - Store form data in the session or application state throughout multi-step processes. - When a form spans multiple pages, preserve all data when users navigate between steps. - Provide "same as" options for common duplicate fields like billing/shipping addresses. - Pre-populate fields with known information and allow users to edit if needed. - Do not clear form fields when validation errors occur. Preserve user input and highlight only the fields that need correction.