Skip to main content
Accessibility.com, LLC
Category: WCAG Principles and Conformance

Redundant Entry

Also known as: WCAG Success Criterion 3.3.7, SC 3.3.7
Simply put

Redundant Entry is a web accessibility guideline that aims to reduce how often users are asked to re-type information they have already provided during the same process, such as filling out a multi-step form. Instead of making someone enter the same details twice, the information should be auto-populated or made available for the user to select. This helps people who may find repetitive typing difficult, tiring, or error-prone.

Formal definition

Redundant Entry is WCAG Success Criterion 3.3.7, a Level A criterion added in WCAG 2.2. It requires that 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, rather than requiring manual re-entry. The criterion includes exceptions: it does not apply when re-entering the information is essential (for example, a password re-entry for security or memory-testing purposes), when the information is required to ensure the security of the content, or when the previously entered information is no longer valid. It also does not apply across sessions. As a WCAG technical guideline published by the W3C, conformance addresses this specific input-assistance requirement and does not by itself guarantee overall usability or legal compliance; manual and assistive technology testing are generally needed to evaluate real-world accessibility.

Why it matters

Repetitive data entry creates a disproportionate burden for many users. People with cognitive disabilities may struggle to recall information they entered on a previous step, and re-typing the same details increases the chance of introducing errors. Users with motor disabilities, or those who rely on assistive technology, may find repeated manual entry physically tiring and time-consuming. By reducing redundant entry, a process becomes faster, less error-prone, and less cognitively demanding for a broad range of users.

Redundant Entry was added as a Level A success criterion in WCAG 2.2, reflecting the W3C's recognition that input assistance is a foundational, rather than optional, part of accessible form and workflow design. Because it is a Level A criterion, it sits among the most widely adopted baseline expectations for accessible content and is commonly included in conformance targets alongside other Level A and AA criteria.

As with all WCAG success criteria, meeting SC 3.3.7 addresses a specific requirement but does not by itself guarantee overall usability or legal compliance. WCAG is a set of technical guidelines published by the W3C, not a law; whether and how it applies in a given legal context depends on the applicable authority, regulation, or settlement. Organizations should treat conformance as one component of accessibility work and consult qualified legal counsel for guidance specific to their obligations.

Who it's relevant to

UX Designers and Product Teams
Designers shaping multi-step forms, checkout flows, and application processes should identify points where users are asked to repeat information and design mechanisms, such as auto-population, selectable prior values, or "same as above" options, to eliminate unnecessary re-entry within a process.
Front-End Developers
Developers implement the auto-population and selection behaviors that satisfy SC 3.3.7, while also handling the criterion's exceptions, such as password confirmation fields or cases where prior data is no longer valid. They should ensure that pre-filled or selectable values are exposed correctly to assistive technology.
Accessibility Engineers and QA Testers
Because automated tools detect only a portion of accessibility issues, testers evaluating Redundant Entry typically rely on manual walkthroughs of each process to confirm that previously entered information is available and to verify whether an exception legitimately applies.
Compliance Officers and Legal Counsel
Those tracking WCAG conformance targets should note that SC 3.3.7 is a Level A criterion introduced in WCAG 2.2. Whether it forms part of an organization's obligations depends on the applicable authority and any governing regulation, guidance, or settlement, and this material is not a substitute for legal advice.

Inside Redundant Entry

Success Criterion 3.3.7 (Redundant Entry)
A WCAG success criterion added in WCAG 2.2 at Level A. It generally requires that information a user previously entered, or that was provided to them, be either auto-populated or available for the user to select, rather than requiring the user to re-enter it within the same process.
Scope: same process
The criterion applies to information requested more than once in the same user process, such as a multi-step form or checkout flow. It does not extend indefinitely across unrelated tasks or sessions.
Acceptable methods of avoiding re-entry
Conformance is commonly met by auto-populating previously entered data or by allowing the user to select it (for example, a 'same as billing address' option) instead of manually retyping it.
Documented exceptions
Re-entry is permitted when it is essential (such as re-entering a password for security or memory testing), when the information is no longer valid, or when re-entering is required to ensure the security of the content.
Benefit to users
Reducing redundant entry generally supports users with cognitive and memory-related disabilities, users of assistive technology, and users with mobility limitations for whom repeated data entry is burdensome.

Common questions

Answers to the questions practitioners most commonly ask about Redundant Entry.

Does the Redundant Entry success criterion mean a site can never ask for the same information twice?
No. The criterion does not impose an absolute ban on requesting the same information more than once. It generally requires that information previously entered by or provided to the user within the same process either be auto-populated or available for the user to select, rather than requiring manual re-entry. There are recognized exceptions, such as when re-entering the information is essential (for example, to confirm a password), when the information is required for security purposes, or when previously entered information is no longer valid. Consult the W3C's published understanding documentation for the current, authoritative scope.
Is Redundant Entry a Level AA requirement that has always been part of WCAG?
No. Redundant Entry was introduced in WCAG 2.2 and is a Level A success criterion; it does not appear in WCAG 2.0 or WCAG 2.1. Because it is Level A, it is commonly treated as more foundational than AA criteria, though the level a given organization targets depends on its own policies, applicable regulations, or referenced benchmarks. Meeting this criterion is one part of conformance and does not by itself guarantee an accessible experience or legal compliance.
How can a multi-step form satisfy Redundant Entry?
A common approach is to persist information the user has already entered across steps and either auto-populate later fields or offer that information for selection, so the user does not have to type it again. For example, an address collected earlier in a checkout flow can be pre-filled or offered as a selectable option at a later shipping or billing step. Implementation details vary by platform; testing with real users and assistive technology is generally recommended alongside meeting the criterion.
What are the recognized exceptions where re-entry may still be acceptable?
The success criterion generally allows re-entry when it is essential, when required for security purposes, and when previously entered information is no longer valid. A frequently cited example of an essential case is confirming a password, where re-typing serves a distinct verification purpose. Because the precise application of these exceptions can be nuanced, refer to the W3C's understanding documentation and evaluate each case in context.
Does auto-population conflict with any other accessibility or privacy considerations?
Auto-populating fields can support Redundant Entry, but designers should weigh it against related considerations, such as security requirements and how sensitive data is handled. In some cases offering information for the user to select, rather than automatically filling it, may better balance convenience and privacy. This entry addresses the Redundant Entry criterion and is not legal or security advice; consult qualified counsel and security professionals for handling of sensitive data.
Can automated testing confirm that Redundant Entry is met?
Automated tools may flag some patterns, but they generally cannot reliably determine whether a given re-entry is essential, security-related, or otherwise excepted, since that requires understanding the process and its context. As with WCAG criteria more broadly, automated checks detect only a portion of potential issues, and manual review together with testing using assistive technology is typically required to evaluate conformance.

Common misconceptions

Redundant Entry (3.3.7) is a long-standing WCAG requirement that applies to all versions.
Redundant Entry was introduced in WCAG 2.2 and is not present in WCAG 2.0 or 2.1. Organizations targeting an earlier version would not have this criterion as an explicit requirement, though it may still be good practice.
The criterion forbids ever asking a user for the same information twice.
It applies within a single process and includes documented exceptions, such as when re-entry is essential, when the prior information is no longer valid, or when re-entry is needed for security purposes like confirming a password.
Meeting Redundant Entry means the form is fully accessible and legally compliant.
Conformance with a single success criterion does not guarantee an accessible experience or legal immunity. Broader WCAG conformance, manual and assistive technology testing, and consideration of applicable law are still needed. This is not legal advice.

Best practices

Identify multi-step processes such as checkouts, applications, and registrations, and map where the same information is requested more than once.
Auto-populate previously entered information where feasible, or provide a clear selection mechanism (for example, a 'same as' option) so users need not retype data.
Document and justify any places where re-entry is retained under a recognized exception, such as password confirmation or security-sensitive fields.
Verify behavior with manual testing and assistive technologies, since automated tools detect only a portion of issues related to this criterion.
Confirm your target WCAG version, and note that Redundant Entry (3.3.7, Level A) applies only when conforming to WCAG 2.2 or later.
Consult qualified legal counsel and current agency guidance to understand how conformance targets relate to obligations in your jurisdiction, as requirements evolve through regulation and case law.