- 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
The waiting room asks the patient to re-type their name, date of birth, and insurance ID even though they entered all three during account registration minutes earlier in the same session.
Example
<!-- Re-asks for name/DOB already entered earlier in the same session --> Why it matters
People with cognitive or motor disabilities who are harmed by retyping the same data.
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.
<input type="text" name="dob" value="1990-04-12" readonly><button>Use saved info</button>Information already provided earlier in a process should auto-populate or be selectable, not re-typed from scratch.
Outcome
On a telehealth app's video-visit waiting room, this barrier is gone for people with cognitive or motor disabilities who are harmed by retyping the same data — they no longer have to work around this.
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