Resource guide
3.3.7 Redundant Entry
Users must not be required to re-enter information they have already provided in the same process.
By Calling All Minds·Last updated April 2026
Success criterion
Conformance level
Essential baseline — must meet for any compliance.
Added in WCAG 2.2
What it means
New in WCAG 2.2, this criterion addresses a common frustration: being asked to enter the same information twice in the same process. For users with motor or cognitive disabilities, this is more than just annoying, it is a genuine barrier.
If a user has already provided information earlier in a process, the system must either auto-populate it later, or provide a way for the user to select or confirm the previously entered value without retyping it.
In practice
Pre-fill the billing address from the delivery address in a checkout flow. Provide a checkbox 'Billing address same as delivery address'.
Do not ask users to enter their email address twice for confirmation. If you need to confirm, use a password-style check that verifies accuracy rather than requiring retyping.
In multi-step forms, carry forward information already collected and allow users to review rather than re-enter it.
Common failures
- Checkout that asks for name, then asks for name again in the billing section
- Registration form that asks for email twice for confirmation purposes without any alternative
- Multi-step application form that asks for the same information in two different sections
The tricky parts
Security-critical inputs like passwords may legitimately require re-entry for confirmation. This exception is narrow: it must be for genuine security reasons, not convenience or a design choice.
AXS Audit
AXS Audit checks your site against 3.3.7 and flags issues your team can act on straight away. It covers criteria that automated scanners often miss.
