Ready Means Not Asking Twice: Redundant Entry at Checkout

WCAG 2.2 criterion 3.3.7 says information already entered must be carried forward, not re-typed. Where stores violate it, and the checkout fixes that follow.

A customer creates an account with her address, confirms it on the order, and then the returns portal asks her to type the same address again to print a label. Each re-ask is small. Together they are a pattern WCAG 2.2 now names directly: Success Criterion 3.3.7, Redundant Entry, Level A.

The criterion is short and practical. Information previously entered by or provided to the user that is required again in the same process must be auto-populated or available for the user to select, with narrow exceptions for security and for information that is no longer valid. This post maps where stores break it, including one place, re-entering a password, where the exception genuinely applies, and one, the shipping address, where it almost never does.

The flows that break it

Shipping then billing is the classic case, largely solved by 'same as shipping' defaults, though stores still ship checkout themes where the checkbox exists and the autofill silently fails on mobile. The live failures today are at the edges of checkout: gift message forms that re-ask for the recipient the customer just entered as the shipping contact, account creation offered after an order that re-asks for the email the order already used, and returns and warranty flows that start from a blank page despite an order number that identifies everything.

Autocomplete attributes are the companion fix. Names, addresses, and payment fields carrying correct autocomplete tokens let browsers and password managers do the carrying, which serves users with memory and motor disabilities and, not coincidentally, every tired person checking out on a phone at midnight.

The exceptions, read narrowly

Re-entering can be required where it is essential, where security demands it, or where the earlier information is no longer valid. Confirming a password on a new account and re-authenticating before a sensitive change are the honest examples. 'Our form was built that way' is not on the list, and neither is 'the returns platform is a different vendor'. The criterion binds the user's experience of the process, not your procurement history.

There is a readiness angle here beyond conformance. Every redundant field is measurable friction: stores A/B test removing a field and celebrate the conversion lift, then leave the same redundancy standing in returns, where it costs support contacts instead of orders and so never gets a test.

A readiness pass in one sitting

Walk the full circle as one user: buy something, create the account when offered, change the address, return the item. Write down every field you typed twice. That list is the finding. Most stores produce four to seven entries, most are configuration or template work, and closing them is a visible improvement you can describe in an accessibility statement without exaggeration.

Related reading: Getting a Store Ready for the European Accessibility Act: Dates, Scope, and Evidence, Accessible PDF Invoices, Receipts, and Order Documents for Online Stores, Accessible Loyalty Points and Rewards Dashboards.

Frequently asked questions

What does WCAG 3.3.7 require exactly?

Within a single process, information the user already entered or provided must not have to be entered again: it should be auto-populated or offered for selection. Exceptions cover cases where re-entry is essential, needed for security, or where the original information is no longer valid.

Is asking for a password twice a violation?

Generally no. Re-entering or confirming credentials falls under the security and essential exceptions. The criterion targets ordinary information such as names, addresses, emails, and order details being demanded repeatedly across a flow.

Does 3.3.7 apply across separate visits?

It is scoped to a process, not to all time. But account holders reasonably experience checkout, account, and returns as one relationship, and carrying known information forward across those flows is the readiness practice the criterion points at, even where a strict reading stops at the session.

How do autocomplete attributes relate to redundant entry?

They are the mechanism that makes not asking twice possible when a form must be shown. Correct autocomplete tokens let the browser supply name, address, and contact details accurately, which supports 3.3.7 and the separate 1.3.5 Identify Input Purpose criterion at Level AA.