- Success Criterion 3.3.7
- Conformance level A
Email Address Requested Again for No Security Reason
3.3.7 — Redundant Entry
Scenario
Setting
A community forum's discussion thread
What’s wrong
Email/username asked again mid-process for non-security reasons.
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
Check whether email or username is asked again mid-process for non-security reasons: 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 community forum's discussion thread, this barrier is gone for people with cognitive or motor disabilities who are harmed by retyping the same data — they reach the same outcome without extra effort.
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
- Form Asking for Information the User Already Entered
- Checkout Flow Requiring Shipping Address Twice
- 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