3.3.7 Redundant Entry
Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated or available for the user to select.
What this rule means
WCAG 3.3.7 (new in WCAG 2.2) requires that when users need to re-enter information they already provided during the same process, the system either auto-fills it or makes it available to select. Users should not have to type the same information twice.
Exceptions exist for security purposes (re-entering a password to confirm), when previously entered information is no longer valid, and when the information is essential for security.
Why it matters
Re-entering information is a significant barrier for users with cognitive disabilities, motor impairments, and anyone using assistive technology. Each additional input increases the chance of error and the cognitive load on the user.
Multi-step forms that ask for the same address, name, or email multiple times create frustration and increase abandonment rates.
Related axe-core rules
There are no automated axe-core rules for this criterion.
How to test
- Complete multi-step forms and note when information must be re-entered.
- Verify that previously entered data is auto-populated or selectable.
- Check that shipping/billing address flows offer a "same as shipping" option.
How to fix
<!-- Auto-populate from previous step -->
<label for="confirm-email">Confirm email</label>
<input type="email" id="confirm-email"
value="user@example.com" readonly />
<!-- Checkbox to reuse data -->
<fieldset>
<legend>Billing Address</legend>
<label>
<input type="checkbox" id="same-address"
onchange="copyShippingToBilling()" />
Same as shipping address
</label>
<!-- billing fields -->
</fieldset>
<!-- Select from previously entered data -->
<label for="address-select">Select an address</label>
<select id="address-select">
<option>123 Main St (from Step 1)</option>
<option>Enter a new address</option>
</select>
Common mistakes
- Asking for the same email address on multiple steps of a checkout flow.
- Requiring re-entry of address when billing matches shipping.
- Not preserving entered data when users navigate back and forward in a multi-step form.