# Stop Making Shoppers Type the Same Address Twice: WCAG 3.3.7

Source: https://accesswatchhq.com/blog/2026-11-11-redundant-entry-3-3-7-checkout-retype.html

November 11, 2026

*The shopper typed their shipping address on step two of checkout. On step four, the review screen asks for it again, in empty fields. They type it a second time, from memory, on a phone, while the bus moves. One typo and the order ships to the wrong street. WCAG 2.2 has a Level A criterion for this exact annoyance, 3.3.7 Redundant Entry, and it is one of the two new Level A criteria in the standard.*

## The rule and its three exceptions

The text is short. 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. Three exceptions apply: re-entering the information is essential, the information is required to ensure the security of the content, or previously entered information is no longer valid. The W3C understanding document gives the worked example every storefront already knows: a billing address same as shipping checkbox. That checkbox is the pattern, and most sites get it subtly wrong.

The exceptions are narrow on purpose. Essential means the re-entry is inherent to the task, and the document's own example is a memory game that would be pointless if previous answers were pre-filled. Security covers a password that should not be auto-displayed, and typing a new password twice to confirm it, since the system itself cannot validate an unseen string. No longer valid covers an expired card or a changed address. Confirm-email-address fields are explicitly exempted as essential re-entry. None of those exceptions covers asking for a shipping address twice because the review screen was built as a separate form.

## The checkout spots that fail it

The review step is the most common failure. A multi-step checkout collects the address on one screen and then presents a blank address block on the review screen for editing, with no values carried over. A review screen that repeats contact fields for editing is not a failure if the earlier values are already present or easy to select. It is a failure when the fields are empty and the shopper has to retype. The same failure shows up in account creation after checkout, where the shopper who just gave their email and address is asked for both again to create an account, and in guest checkout flows that ask for a phone number on one step and demand it again for delivery updates.

The fix is technique G221, provide data from a previous step in a process. Carry the values forward and pre-fill them, or offer them as a selectable option: a checkbox for same as shipping, a list of earlier entries to pick from. Either one satisfies the criterion. What does not satisfy it is leaving the fields blank and trusting the browser to fill them.

## What autofill does not do

This is the part teams get wrong most often. Browser autofill does not satisfy 3.3.7. The understanding document is explicit: the autocomplete feature of browsers is not considered sufficient because it is the content, the website, that needs to provide the stored information. Autofill is a browser feature the user may have off, may have cleared, or may never have set up. The site has to make the earlier entry available itself. Test it the way the criterion does: walk the longest multi-step form on the site, note any field that asks for data already entered earlier in the same process, and if there is no pre-fill and no select-from-previous, that is a failure. For the authentication side of the same checkout, see [accessible authentication and the end of the puzzle test](https://accesswatchhq.com/blog/2026-11-10-accessible-authentication-3-3-8-no-puzzle.md), and for the focus side, [what 2.4.13 demands of your outline](https://accesswatchhq.com/blog/2026-11-10-wcag-2-2-focus-appearance-2-4-13.md).

## Frequently asked questions

### Does 3.3.7 apply between visits, or only inside one checkout?

Only inside one process. The criterion adds no requirement to store information between sessions. If the shopper comes back tomorrow, the site may ask again. Inside a single checkout, it may not.

### Is asking for the email twice a failure?

Confirm-email-address fields are explicitly exempted as essential re-entry, because the system cannot validate an unseen string any other way. The exemption covers the confirmation field, not the whole form asking for the address again.

### Does browser autofill satisfy 3.3.7?

No. The W3C understanding document says browser autocomplete is not sufficient, because the content itself has to provide the stored information. The site must pre-fill the field or offer the earlier entry as a selectable option.

### What is the simplest fix for a checkout that fails this?

Carry the values forward. Pre-fill the review screen with what the shopper already entered, and add a billing address same as shipping checkbox. That is technique G221, and it is usually a state-passing change, not a redesign.