WCAG 3.3.7 Redundant Entry: Do Not Ask for the Same Info Twice

What This Criterion Requires

WCAG 3.3.7 Redundant Entry is a new criterion introduced in WCAG 2.2 at Level AA. It requires that 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, unless re-entering the information is essential for security, the information is no longer valid, or the previous information is no longer relevant. This means that in a multi-step process like a checkout flow, if a user enters their name on step one, the name should be pre-filled or selectable on step two rather than requiring the user to type it again. Common examples include shipping and billing addresses in e-commerce, personal information in multi-step application forms, and account details across related form pages. The criterion recognizes that re-entering information is burdensome for all users and creates a particular barrier for users with cognitive and motor disabilities.

Why It Matters

Requiring users to enter the same information multiple times is a significant burden for users with cognitive disabilities who may have difficulty remembering what they previously entered or who make errors when re-typing information. Users with short-term memory impairments may not remember the exact information they entered on a previous step. Users with motor impairments find every keystroke effortful, and redundant data entry doubles the physical effort required. Users with dyslexia may introduce errors when re-typing information, potentially causing mismatches that lead to form submission errors. Even users without disabilities find redundant entry frustrating and time-consuming. In multi-step forms, redundant entry is a leading cause of form abandonment because users become frustrated with the process. By auto-populating previously entered data or providing it as a selectable option, websites reduce cognitive load, physical effort, error rates, and form abandonment. This is particularly important for e-commerce checkout flows where every point of friction can result in a lost sale.

Common Failures and How to Fix Them

<!-- Step 1: Shipping -->
<form>
  <label for="name1">Full Name</label>
  <input type="text" id="name1" name="shipping_name">
  <label for="email1">Email</label>
  <input type="email" id="email1" name="shipping_email">
  <button type="submit">Continue to Billing</button>
</form>

<!-- Step 2: Billing - asks for same info again -->
<form>
  <label for="name2">Full Name</label>
  <input type="text" id="name2" name="billing_name">
  <label for="email2">Email</label>
  <input type="email" id="email2" name="billing_email">
  <button type="submit">Review Order</button>
</form>

<!-- Step 2: Billing - auto-populated from step 1 -->
<form>
  <fieldset>
    <legend>Billing Information</legend>
    <label>
      <input type="checkbox" id="same-as-shipping" checked 
        onchange="toggleBillingFields()">
      Same as shipping information
    </label>
  </fieldset>
  <div id="billing-fields" hidden>
    <label for="name2">Full Name</label>
    <input type="text" id="name2" name="billing_name" 
      value="Jane Smith">
    <label for="email2">Email</label>
    <input type="email" id="email2" name="billing_email" 
      value="[email protected]">
  </div>
  <button type="submit">Review Order</button>
</form>

<h2>Home Address</h2>
<input name="home_street" placeholder="Street">
<input name="home_city" placeholder="City">
<input name="home_state" placeholder="State">
<input name="home_zip" placeholder="ZIP">

<h2>Mailing Address</h2>
<input name="mail_street" placeholder="Street">
<input name="mail_city" placeholder="City">
<input name="mail_state" placeholder="State">
<input name="mail_zip" placeholder="ZIP">

<h2>Home Address</h2>
<input id="home_street" name="home_street" placeholder="Street" autocomplete="street-address">
<input id="home_city" name="home_city" placeholder="City" autocomplete="address-level2">
<input id="home_state" name="home_state" placeholder="State" autocomplete="address-level1">
<input id="home_zip" name="home_zip" placeholder="ZIP" autocomplete="postal-code">

<h2>Mailing Address</h2>
<label>
  <input type="checkbox" id="same-address" onchange="copyAddress()" checked>
  Same as home address
</label>
<div id="mailing-fields" hidden>
  <input name="mail_street" placeholder="Street">
  <input name="mail_city" placeholder="City">
  <input name="mail_state" placeholder="State">
  <input name="mail_zip" placeholder="ZIP">
</div>

How to Test

1. Complete a multi-step process (checkout, registration, application form) and note each piece of information you enter at every step.
2. Verify that any information you entered in a previous step is auto-populated or available to select when needed again in a later step.
3. Check for common redundancy patterns such as shipping vs. billing address, repeated name and email fields, and address fields that appear in multiple sections.
4. Confirm that any required re-entry (such as re-typing a password for security confirmation) has a legitimate security or validation purpose.

CMS-Specific Guidance

This criterion commonly causes issues on these platforms:

• Shopify Accessibility Checklist
• Bigcommerce Accessibility Checklist
• Magento Accessibility Checklist
• Wordpress Accessibility Checklist
• Wix Accessibility Checklist
• Squarespace Accessibility Checklist

Further Reading

• Accessible Forms Guide
• Shopify Store Accessibility Guide
• Wcag Explained Plain English

Related WCAG Criteria

• WCAG 3.3.2
• WCAG 1.3.5