Success Criterion 3.3.7
Conformance level A

Unnecessary ‘Confirm Email’ Field Duplicated Without Real Need

3.3.7 — Redundant Entry

Scenario

Setting

A hospital's patient portal appointment scheduler

What’s wrong

"Confirm email" style duplicates *are allowed as exception only when essential* — using them for ordinary fields (confirm address, confirm name) fails.

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 for 'confirm email'/'confirm address'-style duplicate fields: these are only allowed where essential — using them for ordinary non-essential fields 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 hospital's patient portal appointment scheduler, this barrier is gone for people with cognitive or motor disabilities who are harmed by retyping the same data — they can complete the task without hitting this wall.

Who is affected