Goal
Reduce repeated data entry for users.
Success Criterion · WCAG 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 where re-entering the information is essential, the information is required to ensure the security of the content, or previously entered information is no longer valid.
Level AWCAG 2.2Understandable3.3 · Input Assistance
Copy button ready
What to do
Avoid requiring users to re-enter information they already provided; reuse or auto-populate it unless essential.
Why it matters
Repeated entry increases cognitive load and effort, especially for users with memory, attention, or motor disabilities.
Success criterion
What WCAG 3.3.7 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
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 the security of the content, or the previously entered information is no longer valid.
Intent
Why WCAG created this requirement
- Redundant entry increases errors and drop-off.
- Auto-population and selection reduce cognitive and motor effort.
- Exceptions: essential, security, or no longer valid.
Benefits
Who gains when you pass
- Users with cognitive disabilities avoid memory burdens.
- Users with motor impairments reduce typing effort.
- All users complete multi-step flows faster and with fewer errors.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may abandon long processes when forced to retype the same info.
Users may introduce inconsistencies or typos on re-entry.
Exception guidelines
Use the WCAG 3.3.7 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Essential
Re-entering is essential to the process.
Requirement
Only when truly essential.
Security
Re-entry required to ensure security.
Requirement
Justify security needs; don’t use as a blanket excuse.
Not valid
Previously entered information is no longer valid.
Requirement
If info can change (e.g., availability), re-entry may be required.
Overview
Within a multi-step process, don’t make users type the same information again (like address or email). Auto-fill or provide a selection. Exceptions exist for security and validity reasons. This is a WCAG 2.2 Level AA addition.
- Carry forward values between steps and allow editing rather than re-entry.
- Use saved profile data where appropriate and let users choose.
- For security, re-entry may be needed (e.g., password) but must be justified.
Reference: All summaries and highlights originate from Understanding WCAG 3.3.7 and the W3C quick reference.
Fast facts
- Conformance level
- Level A
- WCAG version introduced
- WCAG 2.2
- Principle
- Understandable
- Guideline
- 3.3 · Input Assistance
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Address reuse
Pass
Shipping address is reused for billing with a checkbox and editable fields.
Fail
User must retype full address on the next step.
Security exception
Pass
Password must be re-entered to confirm critical change (justified).
Fail
Email must be retyped “for security” with no real need.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document data persistence strategy for multi-step flows.
- Capture evidence of auto-populated fields across steps.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Identify multi-step flows requiring repeated data entry.
- Auto-populate fields with previously entered values and allow editing.
- Provide selection mechanisms (choose saved address) instead of retyping.
- Document security/essential exceptions for required re-entry.
- Preserve values across navigation and session interruptions where feasible.
Testing ideas
Prove conformance with evidence
- Complete multi-step flows and verify repeated information is prefilled or selectable.
- Verify users can edit prefilled values without losing progress.
- Confirm exceptions are limited and justified (e.g., password confirmation).
Related success criteria
More from Input Assistance (3.3)
WCAG 3.3.1Error IdentificationLevel AWCAG 3.3.2Labels or InstructionsLevel AWCAG 3.3.3Error SuggestionLevel AAWCAG 3.3.4Error Prevention (Legal, Financial, Data)Level AAWCAG 3.3.5HelpLevel AAAWCAG 3.3.6Error Prevention (All)Level AAAWCAG 3.3.8Accessible Authentication (Minimum)Level AAWCAG 3.3.9Accessible Authentication (Enhanced)Level AAA