- Success Criterion 3.3.7
- Conformance level A
Verification Code Required to Be Typed a Second Time
3.3.7 — Redundant Entry
Scenario
Setting
A ticket marketplace's seat-selection map
What’s wrong
Phone/verification codes requiring earlier-entered numbers to be typed again on later steps.
Example
A ticket marketplace's seat-selection map runs into this exact issue: phone/verification codes requiring earlier-entered numbers to be typed again on later steps.
Why it matters
People with cognitive or motor disabilities who are harmed by retyping the same data. In this case (a ticket marketplace's seat-selection map), they have to guess at the correct format.
How to test
Complete a step requiring a phone/verification code, then check later steps: if the same number must be typed again, it fails.
How to fix
Previously entered information must be auto-populated or selectable — never demanded again in the same process.
Outcome
Once corrected, a ticket marketplace's seat-selection map lets them complete the form without guessing.
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
- 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
- No Option to Reuse a Previously Entered Value on Later Steps