WCAG 2.2 – Criterion 3.3.7 – Redundant entry (Level A)

Today, we’re diving into a criterion from WCAG 2.2 that almost slipped by us! It’s 3.3.7 – Redundant entry (Level A). This one doesn’t get much attention in Polish accessibility discussions. Let’s try to understand what the W3C organization meant by it! 🙂

You’re probably familiar with those complex forms where you’re required to repeatedly enter the same information, like in your annual tax statement. Or maybe in the 800+ application or just during your everyday online shopping? “Enter income,” “Provide child’s PESEL number,” “Home address,” “Shipping address”… how many times? Exactly.

WCAG 3.3.7 Redundant entry

Criterion 3.3.7 requires website and mobile app creators to suggest information that users have already provided. Helpful, right? The principle is simple but brilliant – “Enter once, use multiple times.”

How can this be done?

• Allow users to copy previously entered information – for example, by implementing a copy button (remember to provide context for the button – “Copy” – who/what?).
• Allow users to select previously saved data in their user profile – like choosing one of several addresses. This could be a dropdown list, but there are many options. @allegro is a great example. There, you can choose from previously provided addresses or, of course, add a new one. 🙂
• Use the autocomplete attribute correctly, which will suggest the appropriate data to users.
• Implement a checkbox – for example, “Same address as above,” “PESEL – Zuzanna Kinaoloczyk”, which simply confirms the user’s choice.

However, keep in mind that this criterion also considers security issues. We need to use it wisely, ensuring that no sensitive data or passwords fall into the wrong hands. Let’s be mindful of this when creating our digital products.