The 2025 TestParty Guide to WCAG 3.3.7 – Redundant Entry (Level A)

Why did the user abandon their checkout? Because the form asked them to type their shipping address three times—and they weren't that into the product.

WCAG 3.3.7 Redundant Entry ensures that users don't have to re-enter information they've already provided within the same process. This Level A criterion, introduced in WCAG 2.2, reduces cognitive load, prevents errors, and makes multi-step forms accessible to everyone—especially people with cognitive disabilities, motor impairments, or anyone using a mobile device.

Table of Contents

• What WCAG 3.3.7 Requires
• Why This Matters
• Quick Implementation Guide
• Common Mistakes to Avoid
• How to Test for WCAG 3.3.7
• How TestParty Helps
• FAQs

What WCAG 3.3.7 Requires

WCAG 3.3.7 requires that when information has already been entered or provided by the user in the same process, it must be either:

• Auto-populated in subsequent steps, or
• Available for the user to select (e.g., from a dropdown, checkbox, or saved data)

Users should never have to type the same information twice unless there's a valid exception.

Key exceptions where re-entry is allowed:

• Essential for the process: Confirming a password or email address for security purposes
• Security requirement: Re-authenticating for sensitive transactions
• Information no longer valid: Data has changed or expired since initial entry

What content is affected:

• Multi-step forms (checkout, registration, applications)
• Wizards and onboarding flows
• Any process where users move between pages or sections
• Information that appears in multiple contexts (billing vs. shipping address)

Why This Matters

Re-entering the same information is frustrating for everyone, but it's a significant barrier for people with cognitive disabilities, memory impairments, or motor disabilities who find typing difficult or exhausting.

Legal and compliance context:

WCAG 3.3.7 is a Level A requirement, making it mandatory for ADA compliance, Section 508 conformance, EN 301 549 (European standard), and the European Accessibility Act. Organizations that fail to meet Level A criteria face legal risk and exclude users from completing critical tasks like purchasing products, applying for services, or accessing benefits.

Business impact:

Form abandonment costs ecommerce businesses billions annually. Redundant entry increases cognitive load, slows completion time, and drives users away—especially on mobile devices where typing is cumbersome. Fixing this improves conversion rates, customer satisfaction, and reduces support costs.

Quick Implementation Guide

1. Auto-populate fields with previously entered data

When users move between steps, carry forward information they've already provided. Use session storage, form state management, or backend persistence.

<!-- Step 1: User enters email -->
<input type="email" id="email" name="email" value="" required>

<!-- Step 3: Email auto-populated from Step 1 -->
<input type="email" id="confirm-email" name="confirm-email" 
       value="user@example.com" readonly>
<p>Confirming order for: user@example.com</p>

2. Offer "same as" options for related data

Provide checkboxes or buttons that copy information from one field set to another.

<label>
  <input type="checkbox" id="same-as-shipping">
  Billing address same as shipping address
</label>

3. Use browser autocomplete attributes

Leverage HTML autocomplete to help browsers and assistive technologies pre-fill common fields.

<input type="text" name="name" autocomplete="name">
<input type="email" name="email" autocomplete="email">
<input type="tel" name="phone" autocomplete="tel">

4. Preserve data across sessions when appropriate

For authenticated users, save profile information (addresses, preferences) so they don't re-enter it in future sessions.

5. Show previously entered data for review

Display a summary of entered information before final submission, allowing users to confirm without re-typing.

Relevant WCAG techniques:

• G221: Provide data from a previous step in a process

Common Mistakes to Avoid

Clearing fields between steps

Don't reset form data when users navigate backward or move to a new section. Preserve their input throughout the entire process.

Forcing re-entry of addresses

Asking users to type their shipping address, then type it again for billing (without a "same as shipping" option) violates this criterion.

Not persisting data on validation errors

If a user submits a form and gets an error, all their previously entered information should remain populated. Making them start over is both a 3.3.7 violation and a conversion killer.

Ignoring authenticated user data

If a user is logged in and you have their address, phone number, or payment method on file, don't make them type it again. Pre-populate or offer it as a selectable option.

How to Test for WCAG 3.3.7

Manual testing checklist:

• Walk through multi-step processes: Complete registration, checkout, or application flows and note every field you're asked to fill out
• Check for auto-population: Verify that information entered in early steps appears automatically in later steps
• Test "same as" functionality: Ensure checkboxes or buttons that copy data (e.g., billing = shipping) work correctly
• Navigate backward: Go back to previous steps and confirm your data is still there
• Trigger validation errors: Submit incomplete forms and verify all valid data persists after error messages appear

What automated tools catch:

Automated scanners can detect missing autocomplete attributes and flag forms that don't use standard patterns, but they cannot fully test this criterion. Automated tools don't navigate multi-step processes or evaluate whether data persists across steps.

What requires human judgment:

• Whether information requested in multiple steps is truly the same data
• Whether exceptions (security, essential re-entry) are appropriately applied
• Whether "same as" options are provided where expected
• The overall user experience of data persistence across a process

How TestParty Helps

TestParty's AI-powered platform helps teams identify, fix, and prevent WCAG 3.3.7 violations across multi-step forms and complex user flows.

What TestParty detects:

TestParty's automated scanning analyzes form structures, multi-page flows, and session state management to flag potential redundant entry issues:

• Forms missing autocomplete attributes on standard fields (name, email, address, phone)
• Multiple instances of the same field across a process without auto-population logic
• Checkout and registration flows that don't offer "same as" options for related data sets
• Forms that clear user input on validation errors or backward navigation
• Missing session persistence for authenticated user data

TestParty's DOM and source code analysis identifies patterns that commonly lead to redundant entry violations, surfacing them in your dashboard with severity ratings and affected user flows.

How TestParty suggests fixes:

For detected issues, TestParty generates concrete, code-level remediation guidance:

• Auto-complete attributes: TestParty suggests adding appropriate autocomplete values to form fields based on their labels, names, and context
• State management patterns: For frameworks like React, Vue, or Angular, TestParty recommends form state libraries and patterns to persist data across steps
• "Same as" UI components: TestParty provides code snippets for checkboxes or buttons that copy data between related field sets (e.g., billing/shipping)
• Session storage implementation: Guidance on using sessionStorage, cookies, or backend persistence to maintain user input across page loads

All AI-generated suggestions are reviewed by your development team or TestParty accessibility specialists before being committed, ensuring fixes align with your application architecture and business logic.

Developer workflow integration:

TestParty integrates directly into your development lifecycle to catch redundant entry issues before they reach production:

• CI/CD gates: Block merges when new forms are introduced without proper data persistence or autocomplete attributes
• Pull request annotations: Flag redundant entry risks at the line level when developers modify multi-step forms or checkout flows
• IDE integration: Real-time feedback as developers build forms, suggesting autocomplete attributes and state management patterns
• Pre-commit hooks: Validate that form data structures include persistence logic before code is pushed

This shift-left approach prevents regressions and ensures new features meet WCAG 3.3.7 from the start.

Ongoing monitoring:

TestParty continuously monitors your site for redundant entry compliance:

• Flow-based testing: TestParty simulates user journeys through multi-step processes, verifying that data persists across steps
• Regression detection: Alerts when code changes introduce new redundant entry violations in previously compliant flows
• Audit-ready reports: Track 3.3.7 compliance over time with detailed reports for legal, procurement, or accessibility audits
• Ecommerce-specific monitoring: For Shopify, WooCommerce, and headless storefronts, TestParty tracks checkout flow compliance as themes and plugins are updated

TestParty's dashboards give product and engineering leaders visibility into where redundant entry issues exist, how they're trending, and which user flows need attention.

Because multi-step forms often involve complex business logic and backend integrations, TestParty provides embedded guidance explaining why each issue matters and how it affects users with disabilities. This helps teams make informed decisions about prioritization and implementation.

FAQs About WCAG 3.3.7

What is WCAG 3.3.7 in plain language?

WCAG 3.3.7 Redundant Entry means users shouldn't have to type the same information twice in a single process. If they've already entered their email, address, or phone number, the system should remember it or let them select it—not make them type it again.

Is WCAG 3.3.7 required for ADA compliance?

Yes. WCAG 3.3.7 is a Level A criterion, which is the baseline for ADA compliance. Courts and regulatory bodies expect websites and applications to meet all Level A and AA criteria, making redundant entry compliance legally required for most organizations.

Does "same as billing address" count as compliance?

Yes. Providing a checkbox or button that copies the shipping address to billing address fields satisfies WCAG 3.3.7. Users don't have to re-type the information—they can select it with a single action.

Can I ask users to confirm their email or password?

Yes, when it's essential for security or accuracy. Asking users to re-enter their password or email during account creation is an allowed exception because it helps prevent typos and ensures security. However, asking users to re-type their shipping address in a confirmation step (when you could just display it) would violate 3.3.7.

Does WCAG 3.3.7 apply to single-page forms?

Generally no. WCAG 3.3.7 applies to information requested multiple times within the same process—typically across multiple steps or pages. If all fields appear on a single page and are only asked once, this criterion doesn't apply. However, if a single-page form has sections that request the same data (e.g., separate billing and shipping sections), you should still provide a "same as" option.

Some TestParty features described in this article are currently under development. Visit TestParty.ai to learn more about our current capabilities and roadmap, or book a demo at TestParty.ai/book-a-demo to see TestParty in action.

Disclaimer: Some of this article was generated with Large Language Models (LLMs) and Artificial Intelligence (AI). There may be some errors and we advise you to consult with human professionals for detailed questions.