Redundant Entry: Don't Ask for the Same Data Twice
Also called: Re-entering information, Repeated data entry, Same as billing address
Definition
Redundant Entry is WCAG success criterion 3.3.7. Information a user already entered or was given in the same process must be auto-populated or available to select when it is needed again – unless re-entry is essential, needed for security or the information is no longer valid.
Redundant entry is when a form asks people for information they already gave a few steps earlier – the delivery address again on the billing step, the order number again on the contact page. WCAG 2.2 requires that such data is filled in for them or offered to pick. Typing everything twice costs time and is a real barrier for people who struggle to remember or to type.
What it means
WCAG 3.3.7 Redundant Entry is a Level A criterion, new in WCAG 2.2. 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.
A process is a series of user actions needed to complete one activity – a checkout, an application, a booking. It can span several domains, for example when payment runs through a payment provider. It does not cover a later visit: the criterion does not require storing data between sessions.
| Situation | Under 3.3.7? |
|---|---|
| Billing address after the shipping address in one checkout | Yes – offer "same as shipping" or fill it in |
| Search term on the results page of the same search | Yes – keep it in the search field |
| Form sent back with an error | Yes – keep what people entered |
| Confirming a newly created password | No – security exception |
| Card details that have expired | No – no longer valid |
| A memory game where recall is the point | No – re-entry is essential |
W3C names who benefits: people with cognitive disabilities and short-term memory difficulties, and people with mobility impairments using switch control or voice input, who need less text entry.
Examples
<fieldset>
<legend>Billing address</legend>
<input type="checkbox" id="same" name="same" checked>
<label for="same">Same as shipping address: 12 Main Street, Springfield</label>
<!-- Address fields appear only if the box is unchecked -->
</fieldset>The checkbox reuses the shipping address with one click. Showing the address in the form label lets people confirm it without going back. When the box is unchecked, the fields appear – ideally pre-filled so only the difference has to be changed.
Offer "same as shipping", carry earlier answers into later steps, keep all entries when a form shows an error message, and let people pick from data shown on the page.
Clear the form after a failed submit, ask for the email address again on the confirmation step, or make people retype an order number the site already showed them.
How to check redundant entry
Questions
What is redundant entry in WCAG?
It is success criterion 3.3.7, Level A, new in WCAG 2.2. If a process needs the same information twice, the second time it must be filled in automatically or offered for the user to select.
Does redundant entry apply to my checkout?
Yes, if the checkout asks for data already given earlier in the same purchase, such as the billing address after the shipping address. A "same as shipping" checkbox is a common solution.
Do I have to save data for the next visit?
No. The criterion only applies within one process. W3C states that information does not have to be stored between sessions or after the user leaves.
Is asking to confirm a password a redundant entry failure?
No. Re-entry for security is an exception, for example re-validating a newly created password that is not displayed. For logins, accessible authentication applies.
Related terms
Accessible Authentication: Logins Without Memory Tests
Accessible Authentication (Minimum) is WCAG success criterion 3.3.8. No step of a login may require a cognitive function test – remembering a password, transcribing a code, solving a puzzle – unless an alternative, a helping mechanism or an allowed exception is available.
Read definition: Accessible Authentication: Logins Without Memory TestsForm Labels: Clear Labels and Instructions
Form labels are the visible texts that name what a form field expects, such as “Email address”. WCAG 3.3.2 requires labels or instructions wherever content asks for user input, including formats and required fields.
Read definition: Form Labels: Clear Labels and InstructionsError Suggestion: Help Users Fix Form Errors
Error suggestion means that when a website detects an input error and knows how it could be corrected, it offers that correction to the user. WCAG 3.3.3 requires it at Level AA, unless it would jeopardize security or the purpose of the content.
Read definition: Error Suggestion: Help Users Fix Form ErrorsInput Purpose: Autocomplete for Personal Data
Input purpose is WCAG success criterion 1.3.5 Identify Input Purpose: the purpose of each input field that collects information about the user can be programmatically determined, for example with the HTML autocomplete attribute.
Read definition: Input Purpose: Autocomplete for Personal Data