Redundant Entry
Information previously entered by or provided to the user that is required again in the same process must be auto-populated, available for the user to select, or made unnecessary.
What it requires
WCAG 2.2 SC 3.3.7 reduces the burden on cognitive-disability users by eliminating "type your address again" steps in checkout. If a user has entered their email at step 1, the email cannot be required again at step 2 unless re-entry is essential (e.g., for security).
Standard exceptions: passwords, security questions, and information whose accuracy must be re-confirmed (e.g., a verification step before payment). For everything else, auto-fill from the previous step or offer a "use the same as billing" toggle.
Common Shopify failure
Custom checkout extension that requires the customer to re-enter shipping address even after they entered it at the address step. Multi-step signup form that asks for first name on step 1 and again on step 3.
How to fix it
For native Shopify checkout, this is handled by Shopify's own forms. For custom storefront checkouts and signup flows, AccessComply's form-fix agent identifies redundant fields and either auto-populates or removes them.
Merchant QA checklist
- Scan the storefront page where this pattern appears: product pages, collection pages, cart drawer, customer-account pages, and any landing page built with theme sections.
- Confirm the issue is fixed in the rendered browser output, not only in the Liquid file. Shopify section settings, app blocks, and third-party scripts can reintroduce the same 3.3.7 failure after a theme edit.
- Re-test the affected component with keyboard navigation and a screen-reader accessibility tree before publishing the theme, especially when the fix changes markup or ARIA attributes.
How AccessComply handles it
AccessComply treats WCAG 3.3.7 as a rendered-storefront issue first. The scanner checks the live DOM and computed styles, maps the finding back to the Shopify theme file that produced it, then classifies the fix as a guided partial fix. When automation is safe, the app writes the smallest theme-code change needed and keeps the original theme backup available. When merchant judgment is required, the issue is surfaced for manual review instead of pretending the page is fixed.
Primary source: W3C — WCAG 2.2 Understanding 3.3.7