Skip to main content
Votre navigateur est trop ancien pour afficher correctement ce site. Veuillez passer à la dernière version de Chrome, Edge, Firefox ou Safari.
Back to WCAG Database
Level AWCAG 2.2

3.3.7 Redundant Entry

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, except in specific cases.

Last reviewed: September 9, 2026

Understanding 3.3.7

This criterion, new in WCAG 2.2, reduces repetitive data entry across a multi-step process, such as a checkout flow or a multi-page application form. Repeated entry is especially burdensome for people with motor disabilities (each keystroke or tap costs effort), people with cognitive disabilities (remembering what was typed earlier), and people using alternative input methods like switch access or speech input.

How to Meet It

Auto-populate previously entered information into later steps (for example, pre-fill a billing address from the shipping address, with an option to edit), or offer a selectable option such as a "Same as shipping address" checkbox instead of requiring re-typing. Exceptions apply when re-entry is essential: for example, re-entering a password to confirm a sensitive change, when the prior information is no longer valid, or when re-entry is required for security.

Code Examples

INCORRECT
<!-- Step 1: Shipping --> <input name="shipping_address" />
<!-- Step 2: Billing --> <input name="billing_address" />
<!-- User must retype the identical address with no option to reuse it -->
CORRECT
<!-- Step 2: Billing -->
<label><input type="checkbox" id="same-as-shipping" onchange="copyShippingToBilling(this.checked)"> Same as shipping address</label>
<input name="billing_address" id="billing_address" />

Frequently Asked Questions

Does having to re-enter a password to confirm a sensitive account change violate this criterion?

No. WCAG 2.2 explicitly exempts cases where re-entry is necessary to ensure security, such as re-confirming a password before changing account details or payment information.

Related Success Criteria

3.3.1 Error Identification3.3.2 Labels or Instructions3.3.3 Error Suggestion3.3.4 Error Prevention (Legal, Financial, Data)

Quick Facts

  • Criterion3.3.7
  • LevelA
  • IntroducedWCAG 2.2

Automate Compliance

AccessiSight automatically scans and identifies 3.3.7 issues in your codebase.

Try Scanner Free