Why Do Multi-Step Forms Make Users Re-enter Information? The Real Meaning of WCAG 2.2 Redundant Entry

Redundant Entry does not require a system to remember user data forever. It means that, within the same process, information the user just provided should be filled in automatically or reusable with one selection when needed again, instead of being copied manually.

“The billing address is the same as the shipping address—please enter it again.” “The applicant entered their name in step one, then has to enter it again in step three.” “The company name must be repeated on every contact form.” These flows are merely annoying for some users, but can become genuine barriers for people with memory, motor or cognitive disabilities. WCAG 2.2 added 3.3.7 Redundant Entry specifically to address this repetition within a single process.

01 The conclusion: information already entered in the same process should be autofilled or directly selectable

This success criterion focuses on avoiding re-entry, not on requiring long-term storage across sessions. Users must still be able to change autofilled content, and reasonable exceptions exist for security, necessity and stale data.

02 1. The classic pattern: same as the previous address

After a user enters a shipping address during checkout, the billing-address page should offer a “same as shipping address” option. Selecting it should reuse the data directly while allowing the fields to be expanded and edited. Do not make users copy the street, city and postal code manually.

03 2. Let users reuse shared information in multi-applicant and multi-contact scenarios

Company names, registered addresses and contact telephone numbers often repeat in corporate tender, visa, loan or insurance forms. Prefill organization-level information and ask users to enter only the fields that differ for each person. For multi-item tasks, “copy previous item and edit” also reduces effort substantially.

04 3. Autofilled information must be visible and editable

Invisible autofill may reduce typing but can silently submit stale information. Reused information should be shown clearly on the confirmation page, with an edit route. Addresses, contacts and payment information change easily, so reducing repetition must not eliminate confirmation.

05 4. Repetition is sometimes necessary, but the reason should be explainable

W3C provides exceptions to Redundant Entry for necessity, security and information that is no longer valid. Certain high-risk confirmations, for example, may require re-entry, or previous information may have expired. “That is how our back-end form works” is not necessity. Product teams should document the genuine reason for each repeated field.

06 5. Do not mechanically create repetition with confirm email fields

Many registration pages historically asked users to enter an email address or password twice to prevent typing errors. Modern designs can reduce errors more effectively through show/hide password controls, format validation, confirmation pages, copy-and-paste and verification emails, without adding cognitive and operational burden.

07 6. Going back to make an edit should not clear every subsequent step

If a user returns to step two of a multi-step form to change one field and steps three through five are all reset, that also creates a repeated-input burden. State management should retain information that remains valid and clear only content that genuinely depends on the changed field and requires reconfirmation.

08 7. Enterprise products should build reuse logic into components and data models

If every team independently implements “same as above” or “copy previous item,” the experience will be inconsistent. A design system can provide structured reuse patterns for Address, Person and Organization data. Development must define the data source, override priority and change-propagation rules.

09 Do not test only the happy path completed once

• Proceed from the first step to the last, then return to edit a middle step.
• Select “same as previous,” then deselect it.
• Change only one field after information has been autofilled.
• Complete the process with a keyboard, screen reader and browser autofill.
• After a session timeout or recovery, check which data is appropriately retained.

10 Finally: reducing repeated input respects work the user has already completed

The longer a multi-step process becomes, the more responsibility the system should assume for remembering. A strong form does not make users repeat work because of an internal data structure. It reuses known information while keeping the experience secure and confirmable. This is both a WCAG 2.2 requirement and a basic quality standard for every complex business product.

11 8. Reusing repeated information requires attention to source trust

Autofilled data may come from the user's immediately preceding input, an account profile, enterprise master data or browser autofill. The interface should ideally tell users where fields came from, especially when sources disagree. High-risk information should not be overwritten silently; users should confirm it.

12 9. Do not interpret Redundant Entry as caching forms forever

Reducing repetition does not mean retaining every sensitive input indefinitely. Payment, identity and health data must still follow data-minimization and security policies. Information can be reused in memory or within the session, then cleared according to policy when the task is complete. Accessibility and privacy minimization can coexist.

13 10. Reduce repeated work in cross-device processes as well

A user may start an application on a phone and continue uploading documents on a computer. If the account system can safely restore confirmed information, it should not require entry from the beginning. If sensitive fields cannot be preserved for security reasons, explain in advance what needs to be confirmed again. Cross-device recovery is not the sole requirement of WCAG 3.3.7, but it embodies the same principle: the system should remember completed work whenever possible.

For long processes, a clear “save and continue later” option also reduces repetition caused by timeouts and device switching.

Frequently Asked Questions

Does Redundant Entry require websites to remember information across different sites?

No. It primarily concerns information the user has already provided within the same process or session.

Must autofilled fields be hidden?

No. Visible, confirmable and editable prefill is preferable because it prevents stale data from being submitted silently.

Does confirm password count as repeated input?

It may create a repeated cognitive burden. Designers should first consider show-password controls, validation and other error-prevention methods.

Can a security-sensitive process require re-entry?

If re-entry is genuinely essential to security, the criterion provides an exception, but the team should have a clear rationale.

Can a multi-step form clear later data when the user goes back?

Only when that later data genuinely becomes invalid because an earlier answer changed. Other information that remains valid should be retained whenever possible.