--- title: "Redundant Entry" url: "https://barrierefreihochzwei.de/en/wcag/3-3-7-redundant-entry" language: "en" description: "WCAG 3.3.7 requires information already given in a process to be auto-populated or selectable – learn how to spare people from entering the same data twice." published: "2025-01-01T08:00:00+01:00" updated: "2026-10-15T09:42:00+02:00" --- # Redundant Entry Don’t ask twice – forms that think ahead. - **Erfolgskriterium:** 3.3.7 - **Prinzip:** Understandable - **Konformitätsstufe:** Level A - **Erklärung beim W3C:** [www.w3.org/WAI/WCAG22/Understanding/redu...](https://www.w3.org/WAI/WCAG22/Understanding/redundant-entry.html) Success criterion 3.3.7 # 3.3.7 Redundant Entry Level AUnderstandable Don’t ask twice – forms that think ahead. ## 1. What is the goal of this criterion? Sound familiar? You’re filling in a multi-page application form and suddenly the system asks for your address again – even though you entered it three pages earlier. Or, when ordering online, you have to type your address as both the delivery and the billing address, even though they’re identical. For people with cognitive disabilities or memory difficulties, this is more than just annoying – it can be the reason they abandon a process. So the goal of WCAG Success Criterion 3.3.7 is clear: you shouldn’t have to type in information you’ve already entered in a process all over again. Instead, it’s auto-populated or offered for you to select. The criterion is new in WCAG 2.2 and sits at Level A. ## 2. What exactly does it require? Specifically, it’s about processes such as checkouts, application forms or registrations. If you’ve already entered a piece of information there – or it was shown to you during the process, such as a reference number – and it’s needed again later in the same process, it must be: - **auto-populated**, or - **available to select**, e.g. via a “Delivery address same as billing address” checkbox, a list of addresses already entered, or as text on the same page that you can select and copy into the field. Important: the selectable data must be on the same page – ideally visible and right next to the input field. The browser’s own autocomplete doesn’t count, because the website itself has to provide the data. **Exceptions** only apply when: - re-entering the information is essential (e.g. in a memory game) - the information has to be entered again for security reasons (e.g. confirming a newly created password that isn’t shown in plain text) - the previously entered information is no longer valid Also: the criterion refers to the same process. You don’t have to store data from previous sessions. A process can run across several domains, though – so a third-party payment provider in your checkout is in scope. A simple example: when placing an order, you enter your email address for your customer account. Later in the checkout, you’re asked for a contact email – your existing address should be pre-filled or offered for selection here. ## 3. Why does it matter for accessibility? Imagine you find it hard to remember information and need to fill in a complex form. You painstakingly enter your details, and three steps later the system asks for the same information again. Without help, you have to go back, find the data and type it in again – or give up in frustration. Avoiding redundant entry supports accessibility because it: - takes the load off people with memory difficulties or cognitive disabilities - reduces mental effort for everyone - cuts down on errors because already validated data is reused - spares people with motor impairments from repeated typing - supports people in stressful situations And last but not least: it makes forms more pleasant for everyone – including people without disabilities who are simply in a hurry or juggling other tasks. ## 4. How to meet the criterion The good news: modern form systems already offer plenty of ways to avoid redundant entry. Here are some proven tips: **Implement auto-population:** - Keep input available across the steps of a process, e.g. in the server-side session or in `sessionStorage` - Pre-fill fields with information that’s already been entered - Offer a “Use the same address” checkbox for delivery and billing addresses - Show previously used input as suggestions in later steps **Provide options to select:** - Create select lists of previous entries (e.g. addresses already entered) - Use radio buttons for recurring decisions - Offer features like “Copy from previous entry” - Don’t clear fields that were already filled in when a submission fails **Technical implementation:** - Set `autocomplete` attributes so browsers can help fill in forms (see [Identify Input Purpose](https://barrierefreihochzwei.de/en/wcag/1-3-5-identify-input-purpose)) – but don’t rely on that alone for 3.3.7; provide the data within your application - Mind data protection: only keep information for as long as the process lasts - Test the behaviour when the page is reloaded and when using the browser’s Back button **What to avoid:** - Storing sensitive data longer than necessary - Showing completely empty fields when information is requested again - Building complicated workarounds where simple pre-filling would do For login processes, [Accessible Authentication (Minimum)](https://barrierefreihochzwei.de/en/wcag/3-3-8-accessible-authentication-minimum) also applies. ## 5. Why this criterion matters for businesses With Success Criterion 3.3.7, too, accessibility isn’t an end in itself – it brings tangible benefits for your business. ### 1. Fewer drop-offs People are less likely to abandon complex forms if they don’t have to enter the same information several times. Less friction means more completed orders, sign-ups and applications. ### 2. Better customer experience Forms that “think ahead” and sensibly reuse data already entered come across as professional and well thought out. That increases satisfaction and builds trust in your digital services. ### 3. Lower support costs Less frustration means fewer support requests about abandoned forms or problems filling them in – and less work for customer service. On the legal side: 3.3.7 is new in WCAG 2.2. The harmonised standard EN 301 549, which the European Accessibility Act and its German implementation, the Barrierefreiheitsstärkungsgesetz (BFSG), rely on, currently refers to WCAG 2.1 Level AA for web content – so 3.3.7 isn’t explicitly required there yet. As a Level A criterion with big benefits for checkout and application flows, you should still implement it. This section is general information, not legal advice. ## 6. The success criterion in the W3C’s words > **Success Criterion 3.3.7 Redundant Entry (Level A)** > > 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. > > Except when: > > - re-entering the information is essential, > - the information is required to ensure the security of the content, or > - previously entered information is no longer valid. In short: whatever you’ve already entered or been given in the same process is pre-filled or offered for selection – unless re-entry is essential, security-related, or the old information is no longer valid. **Official explanation from the W3C** The W3C explains every success criterion in depth – with intent, examples and techniques. [Understanding 3.3.7](https://www.w3.org/WAI/WCAG22/Understanding/redundant-entry.html) ## More criteria from “Understandable” [ 3.1.1 Level A ### Language of Page So screen readers find the right voice. ](https://barrierefreihochzwei.de/en/wcag/3-1-1-language-of-page) [ 3.1.2 Level AA ### Language of Parts When websites become multilingual. ](https://barrierefreihochzwei.de/en/wcag/3-1-2-language-of-parts) [ 3.1.3 Level AAA ### Unusual Words When jargon becomes a barrier. ](https://barrierefreihochzwei.de/en/wcag/3-1-3-unusual-words)