JOURNAL / PRODUCT DESIGN

Never make people type the same thing twice

WCAG 2.2 Redundant Entry asks products to prefill or offer what people already told them in the same process. What it requires, its exceptions and how to keep a confirmation without retyping.

· 5 MIN READ · Blanche Agency
Engraving-style illustration of an open carbon-copy duplicate book, its top sheet curled back over a sheet of carbon paper to reveal the same faint lines already copied beneath.
Original AI-created conceptual illustration; exact Blanche logo composed separately. · Blanche Agency · aiBLANCHE / 2026

INTRODUCTION

Step one of a checkout asks for your address. Step three asks for your billing address, in a blank form, as if the first answer had evaporated. Most teams know this is irritating. Fewer treat it as what it is: a design decision that moves work from the product's memory to the person's, and one that an accessibility standard now names directly.

This piece is for founders, product managers and designers who own multi-step forms, checkouts and applications. The argument is simple. If your product already has an answer, asking for it again should be the exception you can defend, not the default you inherited from how the database is structured.

What the standard actually requires

WCAG 2.2, a W3C Recommendation first published in October 2023 and updated on 12 December 2024, added Success Criterion 3.3.7, Redundant Entry, at Level A, the baseline level. In plain terms: information that a person has already entered, or that was provided to them, and that is needed again in the same process must be either filled in automatically or available for them to select.

There are three exceptions. Re-entry is allowed when it is essential, as in a memory game. It is allowed when it is needed for security, such as confirming a newly created password that is hidden as you type. And it is allowed when the earlier information is no longer valid.

The W3C's Understanding document fills in details product teams tend to get wrong:

  • Browser autofill does not count. The product has to supply the earlier answer or avoid asking again.

  • “Available to select” can be simple. A checkbox such as “billing address is the same as delivery”, a drop-down that offers the earlier value, or the value shown on the same page so it can be copied.

  • The scope is one process, not your whole relationship with the customer. It does not require storing data between sessions, but a third-party step inside the process, such as a payment provider, is in scope.

  • Errors are part of it. When a submission fails, the values already entered should not be cleared.

Why it matters beyond compliance

The W3C frames the benefit around people with cognitive and memory disabilities, for whom recalling and retyping earlier answers is a real barrier, and around people using switch control or voice input, for whom every field is costly. That alone is a reason to care.

There is also a plain product reason. Each repeated question is a small signal that the system is not listening. Each retyped value is another chance for a typo that then has to be caught somewhere else, often by your support team. Redundant entry is rarely the result of a decision anyone made. It usually comes from a structure: the shipping module and the billing module were built separately, or the third step belongs to another team's service.

The serious counterargument

There is a fair case for asking again. People move. Phone numbers change. An address entered for a quote three steps ago may not be the right one for an invoice. Re-asking is sometimes a deliberate check, and data protection teams are rightly wary of carrying personal data further through a flow than necessary.

The standard already accommodates most of this. Information that is no longer valid can be requested again. And the W3C notes that the criterion has no privacy exception, while warning that a careless implementation could expose more personal data than before. The better answer to “we need to confirm it” is rarely a blank field. It is the earlier value, shown and editable, with a clear question: is this still right? That keeps the check and removes the retyping.

A worked example

A hypothetical rental application, not a client case. Step one collects the applicant's name, email and current address. Step four, the reference check, asks for “address for correspondence”. Step six, run by a separate payment provider for the deposit, asks for a billing address.

  • Step four becomes a choice: “Use my current address” is preselected, with “Use a different address” beside it.

  • Step six passes the address to the payment provider, or offers the same choice there. If the provider cannot accept it, the earlier address is displayed on the page so it can be selected or copied.

  • A failed card payment returns to the form with everything still filled in, except the fields the provider must clear for security.

  • A final check answers page, as the GOV.UK Design System recommends, shows each answer with a Change link, so the confirmation happens once, at the end, where people expect it.

How to audit a journey this week

  • Walk your longest form end to end and highlight every field whose answer the product already has.

  • For each one, choose a fix: prefill it, offer it as a choice, or show it for confirmation.

  • Pay special attention to boundaries between services and vendors. That is where redundant entry hides.

  • Check what happens after an error, and whether entered values survive.

  • Add the right autocomplete values as well, so browsers can help with first-time entry. That supports Identify Input Purpose (1.3.5), but it does not replace anything above.

Remembering within a session is the floor. If your journey spans several visits, also consider how people return to unfinished work and how a session timeout preserves what they typed.

Sources checked on 18 November 2026: W3C WCAG 2.2 Recommendation and its Understanding documents for 3.3.7 and 1.3.5, and the GOV.UK Design System check answers pattern.

KEEP THINKING

Keep reading.

More ideas on building better brands and digital products.

Product design

Pages, “load more” or infinite scroll: decide by what people do next

Product design

Every drag needs a second way to move

View all articles