3.3.7 Redundant Entry

What does it mean?

In a multi-step process, such as a checkout or an application form, users should not have to type the same information twice. If the data is needed again, it must be filled in automatically or be available to select, for example with a "Billing address same as delivery address" checkbox.

Exceptions: when re-entering is essential (for example in a memory game), when it is needed for security (for example confirming a new password), or when the earlier information is no longer valid. The browser's own autofill does not count as meeting the criterion; the page must provide the data itself.

Who does it help?

• People with cognitive disabilities or memory problems
• People with motor disabilities for whom typing takes effort
• Everyone who fills in long forms on a mobile phone

Common failures

• The checkout asks for the e-mail address on step 1 and again on step 3
• The billing address must be typed in full even though it matches the delivery address
• After going back to correct one field, all earlier entries in the process are empty

How we test it

• people only Manual only: nothing useful can be measured. The reviewer tests it directly.

Test question: Information already entered in the same process is filled in again or selectable, not asked twice.

A person decides every criterion. No criterion ever passes automatically.

How to fix it

<h2>Billing address</h2>
<label for="b-street">Street</label>
<input id="b-street" name="b-street">

<h2>Billing address</h2>
<label>
  <input type="checkbox" name="same-address" checked>
  Same as delivery address
</label>
<!-- fields below are prefilled from step 1 and stay editable -->

The page reuses the data from the earlier step instead of asking for it again.

Practical tips

• Keep entered data when users move back and forth between steps.

Guides and patterns on this

• Forms that everyone can completeForms are where people buy, book or give up. This guide shows how labels, required fields and error messages need to work for keyboard, screen reader and magnifier users.

Official source

Understanding WCAG 2.2 at the W3C: 3.3.7 Redundant Entry