Redundant Entry

Redundant Entry is WCAG 2.2 success criterion 3.3.7 at AA level. It requires that interfaces never force users to retype information they already gave during the same transaction. Designers trigger failures when they treat each Figma artboard as a fresh start and drop blank fields for shipping address after the user typed it three steps earlier. The criterion lists exactly three escapes. Prefill the later fields automatically from the earlier data. Build a review screen that shows every previous answer in editable summary cards. Or populate a dropdown or radio group with the prior values so the user picks instead of types. The rule exists because repeated data entry spikes cognitive load. Users with dyslexia, brain fog, or limited working memory abandon at higher rates. The original Brainy Papers accessibility checklist slots this check into the post-ship phase for a reason. Marketing teams and CMS editors inject new steps months after launch and quietly reintroduce the same failure. Stripe checkout and Amazon cart flows solved this years ago by treating data as sticky the moment it is captured.

What it is not is a blanket ban on any question that looks similar to one asked before. Redundant Entry does not block password confirmation on a high-stakes bank transfer. It does not reach across separate site visits or unrelated tools. It does not apply to one-screen forms or security steps that deliberately repeat data for verification. Designers who read the criterion as zero repetition anywhere either strip useful fields or dismiss the entire rule as impractical. Both moves fail audits.

Concrete examples separate teams that ship clean experiences from teams that collect audit debt. Amazon updated their 2023 checkout so the shipping address auto-selects for billing with one checkbox. No second round of typing. The pattern has cleared billions of transactions. Google Workspace account setup captures organization details once then surfaces them as editable cards in the review step so admins tweak without backtracking. Linear built the same intelligence into workspace creation where project metadata carries forward into billing and member invites with zero re-entry. On the failure side a major UK bank reworked their mortgage portal in Q2 2025 right after the European Accessibility Act deadlines. The new multi-step form collected address and income details then presented blank fields for the exact same data in the affordability checker. No prefill, no summary cards. Accessibility consultants flagged repeated 3.3.7 violations during procurement. Remediation took six months and forced a complete rewrite of their form state architecture using a shared React context. Another train wreck appeared in a 2024 travel app where passenger names and dates of birth entered on screen one reappeared as empty inputs during seat selection. Conversion among users over 55 collapsed until the team added a review screen with pencil icons next to every summary line. Mayo Clinic updated their 2026 patient portal booking flow to pull all prior data into accordions on a single review page. Each accordion expands to the original pre-populated field on edit. Completion time dropped 28 percent and the WCAG audit came back clean.

Use Redundant Entry on every flow longer than one screen that re-collects data. Deploy it in Shopify checkouts, SaaS onboarding sequences, insurance quote tools, government service applications, and enterprise CRM setups. Call it out explicitly in design handoffs so developers wire persistent state instead of isolated components. Test it during build with keyboard navigation and screen readers like NVDA and VoiceOver. Run monthly production crawls because third-party embeds and CMS changes reintroduce the problem. Skip it for single-page forms, password creation, or any step where deliberate repetition adds safety such as confirming a wire transfer amount. Never force a review step on a three-question poll widget. Match the fix to actual user pain instead of applying the rule like wallpaper.

The best design systems document the three compliant patterns with annotated Figma variants and ready-to-use code snippets so no new form can accidentally ship redundant fields. Teams that treat the entire journey as one conversation instead of disconnected screens cut support tickets and raise completion rates. Forms stop feeling like interrogations and start feeling like competent assistants that remember what you already told them.

Stop making users repeat themselves like amnesiac data entry clerks and design forms that carry information forward like they matter.