• 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 

<!-- step 2: phone verified with code 483920 -->
<label for="confirm-code">Re-enter your verification code</label>
<input id="confirm-code">
<!-- step 5, checkout: the same code is required again before payment -->

Why it matters

A buyer picking seats for a concert has to dig up a text message and retype the same code a second time just to pay.

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

Once a code is verified earlier in the same process, remember that state and never ask for the same code again.

<!-- verified state from step 2 is stored in the session -->
if (session.phoneVerified) {
  skipVerificationStep();
}

Outcome

The buyer moves straight from seat selection to payment without hunting for the same code twice.

Who is affected

People with cognitive and memory disabilities who find retrieving and retyping the same short-lived code twice especially error-prone.

Learn more

Related scenarios