- Success Criterion 3.3.7
- Conformance level A
Form Asking for Information the User Already Entered
3.3.7 — Redundant Entry
Scenario
Setting
A telehealth app's video-visit waiting room
What’s wrong
No numbered W3C failure technique exists for this rule — it fails simply when the required feature/behavior is missing or inadequate (see the scenarios below).
Example
A telehealth app's video-visit waiting room is a good example: no numbered W3C failure technique exists for this rule — it fails simply when the required feature/behavior is missing or inadequate (see the scenarios below).
Why it matters
People with cognitive or motor disabilities who are harmed by retyping the same data. The practical effect on a telehealth app's video-visit waiting room: they can't tell what a field wants or why it failed.
How to test
Walk a multi-step process end to end: check whether any information is asked for twice with no auto-fill or 'same as' shortcut — if so, it fails.
How to fix
Previously entered information must be auto-populated or selectable — never demanded again in the same process.
Outcome
That one change on a telehealth app's video-visit waiting room means they see exactly what went wrong and how to fix it.
Who is affected
People with cognitive or motor disabilities who are harmed by retyping the same data.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Checkout Flow Requiring Shipping Address Twice
- Email Address Requested Again for No Security Reason
- Wizard That Clears Previously Entered Data When Going Back
- Resume Upload Followed by Manual Re-Entry of the Same Fields
- Verification Code Required to Be Typed a Second Time
- No Option to Reuse a Previously Entered Value on Later Steps