Understandable · Input Assistance

WCAG 3.3.7 Redundant Entry

WCAG 3.3.7 Redundant Entry explained: do not make people type the same information twice in one process. Exceptions, checkout examples and how to test.

3.3.7 Level A Added in WCAG 2.2 Needs manual review

Illustration: a form icon, with WCAG 3.3.7 and Redundant Entry
Table of contents

WCAG 3.3.7 Redundant Entry is a Level A success criterion, added in WCAG 2.2. This page is part of the WCAG 2.2 success criteria guide. It explains the rule in plain English, who it helps, what passing and failing code look like, and how to test it by hand and with AccessBell, a website accessibility monitoring tool. AccessBell is not an overlay.

What WCAG 3.3.7 Redundant Entry requires

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.

That sentence is the heart of the criterion. The exceptions and notes are in the WCAG 2.2 Recommendation and the Understanding document for 3.3.7 Redundant Entry.

What WCAG 3.3.7 means in plain English

WCAG 3.3.7 Redundant Entry is new in WCAG 2.2 and it is Level A. In a single process, such as checkout or a multi-step application, do not make someone retype information the site already has. Fill it in, or let them pick it from what they entered. A shipping address that has to be typed again as the billing address fails, unless a checkbox can copy it.

Three exceptions are in the criterion. Re-entry is allowed when it is essential, when it is there for security, or when the earlier value is no longer valid. Asking someone to type a password again to confirm it can be essential. Asking for the same email on step 1 and step 3 of a checkout, with no way to reuse it, is not.

Who WCAG 3.3.7 helps

People with cognitive disabilities and memory difficulties, people using switch or voice input for whom every extra field is slow, and anyone on a phone who mistypes a long address. The W3C’s reason for adding it is that some people cannot reliably remember what they entered a step earlier.

Pass and fail examples

Fail Step 3 asks for the email again, with no prefilled value and no way to select the one from step 1.
<label for="email-again">Confirm your email by typing it again</label>
<input id="email-again" name="email_again" type="email" autocomplete="off">
Pass The billing address can be copied. The person does not type it twice.
<label>
  <input type="checkbox" checked>
  Billing address is the same as shipping
</label>

How to test WCAG 3.3.7

  1. Walk the whole process once: checkout, booking, or account creation. Write down every field.
  2. Mark any field that asks for something already provided in that process. Email, name, phone and address are the usual repeats.
  3. Confirm the second ask is either prefilled or selectable (a “same as shipping” control, a dropdown of entered values). A placeholder that shows the old value but still requires typing does not pass.
  4. If the repeat is a security check or a confirmation that is essential, note why, and do not treat it as a failure.

Testing WCAG 3.3.7 with AccessBell

A website accessibility monitoring tool sees one page at a time. It cannot tell that an email field on step 3 repeats step 1. AccessBell will not mark 3.3.7 pass or fail from a single-page scan. Walk the process. Use the scan for the labels, errors and names on each step.

Check your site for this with a free scan of one public page. AccessBell is a website accessibility monitoring tool, not an overlay.

Common failures on Shopify, WordPress, Wix and Squarespace

These are patterns in how the builders work. They are not counts from AccessBell scans. Where a platform hosts the screen, a merchant may not be able to change it, and an unscanned page is not a pass.

Shopify

Checkout is a hosted flow, and a merchant often cannot add a “same as shipping” control inside it. What you can check is the theme’s own multi-step flows: wholesale applications, gift options and custom forms that ask for the email twice. The Shopify checker scans a public page. The store checklist places 3.3.7 on checkout. Do not treat a page the scanner could not change as a pass.

WordPress

WooCommerce and form plugins repeat billing and shipping fields. Turn on “ship to a different address” so the billing address is the default, and avoid a second email field that is empty. Multi-page Gravity-style forms should carry values forward. Review the flow, then scan a step with the WordPress checker.

Wix

Stores, bookings and custom forms are the processes to walk. The side cart and some app pages are on the wizard’s “does not support” list in the Wix checklist, so a wizard score does not cover this. Prefill or offer a choice when a later step needs the same details. The Wix checker still helps with labels on the page you can load.

Squarespace

A custom form split across blocks, or a checkout that asks again for a detail the account already holds, is the case to test. Squarespace’s form guidance is in the Squarespace checklist. If you cannot prefill a hosted checkout field, do not add a second copy of that question in a block you do control.

Level and conformance

Level A, added in WCAG 2.2, under Input Assistance. Because it is Level A, every WCAG 2.2 conformance claim includes it, including Level A, AA and AAA. It does not apply across separate visits. “The same process” means the task the person is in now. The W3C summary is on What’s New in WCAG 2.2.

Conforming at Level AA means meeting every Level A and Level AA criterion that applies, not only the ones labeled AA. See the WCAG 2.2 conformance requirements. This page explains the technical rule. It is not a legal opinion. Read the disclaimer.

Related WCAG criteria

Every criterion is listed in the WCAG 2.2 success criteria guide.

Frequently Asked Questions

What level is WCAG 3.3.7 Redundant Entry?

Level A. It was added in WCAG 2.2. Level AA and AAA targets include every Level A criterion, so they include 3.3.7.

Does a “type your email again” field fail 3.3.7?

It fails when the site already has the email from earlier in the same process and the person must retype it with no prefilled value and no selection. A security check that is essential can be an exception. A normal checkout confirmation usually is not.

Does 3.3.7 apply to a form the person abandoned and came back to later?

The criterion is about the same process, not a later visit. Information that is no longer valid is also an exception. A new order does not have to reuse an address from a different order if that address may have changed, but offering it as a choice is the better pattern.

Sources

This page explains a technical standard and is not legal advice. See our disclaimer.

About the Author

Anton StewartAuthor

Contributor, AccessBell

Anton Stewart writes and reviews accessibility guides for the AccessBell blog, checked against the W3C standards and other primary sources.

Check your site for WCAG 3.3.7

The free scan checks one public page for 3.3.7 Redundant Entry and the other rules an automated test can see. AccessBell is a website accessibility monitoring tool, not an overlay. The main report is a one-time Domain Audit. Pro keeps the site monitored.

Pro is a 3-day free trial, then $29 per domain per month or $199 per year. You add a card at checkout and are not charged until the trial ends. Cancel before then and you will not be charged. A Page Report is $19 for one page.