WCAG 3.3.7: Redundant Entry
Level AQuick answer: Users should not have to re-enter information the store already knows within the same process unless it is essential.
What This Means
On ecommerce sites, Redundant Entry usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like checkout asks for billing address again even after selecting 'same as shipping'. or account recovery asks for email on every step after sign-in confirmation., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- Checkout asks for billing address again even after selecting 'same as shipping'.
- Account recovery asks for email on every step after sign-in confirmation.
- B2B wholesale forms repeat company name across multiple steps.
- Returns portals request order number and email again on the confirmation screen.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Reuse previously entered values and allow confirmation instead of retyping.
- Prefill known data in multi-step flows and keep it editable.
- Explain clearly when re-entry is required for security or legal reasons.
- Map backend process steps so data survives page refreshes and redirects.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
<input name="email">
<input name="confirmEmail">
<!-- After -->
<input name="email" autocomplete="email">
<p>We will use your existing email for updates.</p>FAQ
What is WCAG 3.3.7?
Users should not have to re-enter information the store already knows within the same process unless it is essential.
How does WCAG 3.3.7 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with checkout asks for billing address again even after selecting 'same as shipping'. and account recovery asks for email on every step after sign-in confirmation. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 3.3.7 violations?
Start by auditing the live storefront, then Reuse previously entered values and allow confirmation instead of retyping.; Prefill known data in multi-step flows and keep it editable.; Explain clearly when re-entry is required for security or legal reasons.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 3.3.7 → Free ADA Compliance Scan