WCAG 3.3.7 Redundant Entry

What WCAG 3.3.7 Requires

Information the visitor already entered earlier in the same process should not need to be re-entered manually; it should be auto-populated or selectable, unless re-entry is essential.

How to Test It by Hand

Complete a multi-step form and check whether previously entered information (like a shipping address reused for billing) must be retyped.

Common Failures

• A checkout flow asks for the same address twice with no "same as shipping" option.

Testing WCAG 3.3.7 With AccessBell

This criterion depends on meaning or context, so it needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it is not missed.

Run a free scan to spot issues on your own pages.

Related Criteria in Input Assistance

• 3.3.1 Error Identification (Level A, WCAG 2.0)
• 3.3.2 Labels or Instructions (Level A, WCAG 2.0)
• 3.3.3 Error Suggestion (Level AA, WCAG 2.0)
• 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA, WCAG 2.0)
• 3.3.5 Help (Level AAA, WCAG 2.0)
• 3.3.6 Error Prevention (All) (Level AAA, WCAG 2.0)
• 3.3.8 Accessible Authentication (Minimum) (Level AA, WCAG 2.2)
• 3.3.9 Accessible Authentication (Enhanced) (Level AAA, WCAG 2.2)

Frequently Asked Questions

What does WCAG 3.3.7 require?

Information the visitor already entered earlier in the same process should not need to be re-entered manually; it should be auto-populated or selectable, unless re-entry is essential.

Can AccessBell test WCAG 3.3.7 automatically?

Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.

What level is WCAG 3.3.7?

Level A, added in WCAG 2.2.

Sources

• W3C: Understanding 3.3.7 Redundant Entry (opens in a new tab)
• W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)

This page explains a technical standard and is not legal advice. See our disclaimer.