Level
A
Since
WCAG 2.2
/ WCAG criterion

3.3.7 Redundant Entry

Information a person already entered or was given in the same process must not have to be typed again: it is filled in for them or offered to select, with a few exceptions.

/ What it requires

Typing the same address twice in one checkout, or entering an email address again on step four after giving it on step one, costs everyone time. For people with cognitive disabilities, memory impairments or limited movement it can end the task. This criterion says that information previously entered by or provided to the user, which is required again in the same process, must be either auto-populated or available for the user to select. A process is a series of user actions each needed to complete an activity, and it can run across domains, so a third-party payment step inside a checkout is in scope.

W3C leaves the method open: available to select can be a checkbox such as "Billing address same as delivery address" or a list of earlier entries, and it has to be on the same page. The autocomplete feature of browsers is not considered sufficient, because the site itself has to make the earlier entry available. Three exceptions apply: re-entry is essential, as in a memory game; the information is needed for the security of the content, such as confirming a new password that is not displayed; or the information entered earlier is no longer valid. Nothing has to be kept between sessions.

This criterion is new in WCAG 2.2 and is not part of WCAG 2.0 or 2.1.

/ How pages fail it

  • The checkout asks for the billing address after the delivery address and offers no way to copy it.
  • Step three of an application asks again for the email address the user typed on step one.
  • After a payment error the form reloads empty, and the delivery details already entered have to be typed again.
  • A multi-step insurance quote asks for the date of birth on the first screen and again, in an empty field, on the summary screen.
  • A booking hands over to a payment provider on another domain that asks again for the name and email already given, and nothing is passed across.

/ How to check it yourself

  1. Walk through each multi-step process on the site, such as checkout, registration, an application, a booking or a support request, and note every field you fill in.
  2. At each step, check whether you are asked for something you already entered, or something the site already gave you, such as an order number.
  3. Where it is asked again, check that it is filled in already or can be selected on the same page, for example with a "same as delivery address" checkbox or a list of earlier entries.
  4. Switch off browser autofill or use a private window, so that the browser does not cover up a missing implementation.
  5. For every repeat that remains, decide whether an exception applies: re-entry is essential, needed for security, or the earlier value is no longer valid.

/ How to fix it

  • Add a checkbox "Billing address same as delivery address" that copies the values, or skips the second block, when it is ticked.
  • Keep entered values in the state of the multi-step form and render them as the value of the fields when the user returns to a step.
  • After a server-side validation error, send the form back with every accepted value filled in, and clear only fields that must be cleared for security.
  • Pass known data to the next step, or to the payment provider as prefilled fields of its hosted page where the provider supports it.
  • Where a value cannot be filled in, offer it as a choice: a select of addresses used earlier in the process, or a button that inserts the previous value.

/ What our scanner checks

Our scan has no automated check for redundant entry. It reads a page as it loads and never fills in or follows a multi-step process, so it cannot know what was asked earlier. The autocomplete-missing rule, filed under 1.3.5, notices personal-data fields with no autocomplete attribute, but browser autofill does not satisfy this criterion anyway. A person goes through the forms step by step in a manual audit.

/ Who fails it, in our own measurements

The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.

One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.

/ Questions about this criterion

Does browser autofill satisfy Redundant Entry?

No. W3C says the autocomplete feature of browsers is not considered sufficient, because the site itself has to make the earlier entry available. Autocomplete attributes still help people and serve 1.3.5 Identify Input Purpose, but the form has to fill the value in or offer it to select.

Is asking for a password twice a failure of 3.3.7?

No. Security is one of the three exceptions. When a user creates a password that is not displayed, W3C allows asking for it a second time to confirm it. The other exceptions are re-entry that is essential, as in a memory game, and information entered earlier that is no longer valid.

What level is 3.3.7, and does it apply between visits?

Level A, new in WCAG 2.2. It applies within one process and adds no requirement to store information between sessions. A visitor who comes back after the session has closed, or who has navigated away, may be asked for the same details again.