Multi-step processes already demand attention, memory, and effort. For many users, being asked to re-enter the same information turns a manageable task into a frustrating one. Success Criterion 3.3.7 (Redundant Entry) is part of WCAG’s Input Assistance guidelines. These criteria focus on reducing errors, effort, and cognitive strain when users fill out or complete tasks.
This criterion removes unnecessary memory demands during a task by ensuring users do not have to recall and retype information they have already provided.
WCAG Success Criterion
3.3.7 Redundant Entry (Level A)
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 when:
- Re-entering the information is essential
- The information is required to ensure security
- The previously entered information is no longer valid
What This Criterion Requires (In Plain Terms)
If completing a task requires the user to remember information they already provided earlier in the same flow, the criterion is failed.
Instead, the website must:
- Reuse that information automatically, or
- Make it easily reusable without relying on memory
This applies during one continuous activity, such as:
- Checkout
- Registration
- Applications
- Multi-step forms
It does not require remembering information after the user leaves the task.
WCAG Context: Why This Is in 3.3.x
The 3.3 Input Assistance guidelines focus on helping users:
- Avoid errors
- Recover from errors
- Complete tasks without unnecessary effort
Redundant Entry specifically addresses memory burden, which disproportionately affects users with cognitive, learning, and motor disabilities,but also impacts everyone under fatigue or stress.
What “Same Process” Means
A process is a single task with a clear goal.
Example (used throughout this article):
An online checkout flow with multiple steps: cart, address, delivery, review, confirmation.
A process:
- Can span multiple pages
- Can include third-party services (e.g., payment providers)
A process ends when:
- The task is completed
- The session is closed
- The user navigates away and returns later
This criterion does not require persistence across visits.
Why This Matters
Remembering information is work.
For users with:
- Cognitive or learning disabilities
- Short-term memory difficulties
- Attention fatigue
- Motor impairments (voice input, switch access)
…being forced to recall previously entered information increases:
- Error rates
- Task abandonment
- Repeated corrections
- Frustration and fatigue
Removing redundant entries directly improves task completion.
Why Browser Autocomplete Is Not Enough
Browser autocomplete:
- Is controlled by the user, not the website
- Is inconsistent across devices and environments
- May be disabled or unavailable
- Is not reliably accessible
WCAG requires the content itself to make prior information available during the process.
Relying on browser features alone does not meet this criterion.
Acceptable Ways to Avoid Redundant Entry
“Available to select” is intentionally flexible and may include:
- Pre-filled inputs that can be edited
- A checkbox such as “Billing address same as shipping address”
- A selector that reuses earlier values
- Visible text that the user can copy into a field
- A toggle that populates fields on demand
The requirement is not how; it is that memory is not required.
How Redundant Entry Impacts Assistive Technology Users
Redundant entry disproportionately affects users who rely on assistive technologies:
- Screen reader users must re-navigate long forms to re-enter information
- Speech input users must re-dictate exact values, often verbatim
- Switch users experience exponential time costs for repeated entry
What feels like a minor inconvenience visually can become a task-stopper.
Common Ways Teams Get This Wrong
- Clearing fields after validation errors
- Asking users to retype identifiers already provided earlier
- Treating browser autofill as sufficient
- Showing previous information but not allowing reuse
- Forcing re-entry “for consistency” with no valid exception
If users must remember what they already entered, the criterion is not met.
Valid Exceptions
Redundant entry is allowed only when:
Essential to the activity
Examples:
- Memory or recall games
- Exercises where remembering is the point
Required for security
Examples:
- Confirming a newly created password
- Sensitive authentication steps
Information is no longer valid
Examples:
- Expired address details
- Time-sensitive or context-dependent values
These exceptions should be justified, not assumed.
What This Criterion Does Not Require
- Storing information between sessions
- Remembering passwords
- Persisting data across unrelated tasks
- Eliminating all repeated fields everywhere
It targets unnecessary repetition, not legitimate validation or security needs.
Example (Running Scenario: Checkout)
During checkout:
- The user enters a billing address
- A validation error occurs on a later step
- The form reloads
Passing behaviour:
- The billing address remains filled in
- The user can review and edit it
Failing behaviour:
- The billing address is cleared
- The user must retype it from memory
How This Is Evaluated in Accessibility Audits
In practice, auditors will:
- Complete a multi-step process
- Trigger validation errors
- Verify that previously entered data remains available
Clearing fields after errors is one of the most common failures of this criterion.
Relationship to Other Input Assistance Criteria
- 3.3.1 Error Identification — tells users something is wrong
- 3.3.3 Error Suggestion — explains how to fix it
- 3.3.4 / 3.3.6 Error Prevention — protects against consequences
- 3.3.7 Redundant Entry — reduces memory load during tasks
Each criterion addresses a different breakdown point in real workflows.
Wrapping Up
Redundant Entry is a Level A requirement because unnecessary memory demands block basic task completion.
If users must remember information they already provided earlier in the same process, the experience fails this criterion. By reusing information or making it easy to reuse, you reduce errors, frustration, and abandonment while making tasks achievable for more users.
