• 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

Try this on a hospital's patient portal appointment scheduler: "Confirm email" style duplicates *are allowed as exception only when essential* — using them for ordinary fields (confirm address, confirm name) fails.

Why it matters

People with cognitive or motor disabilities who are harmed by retyping the same data. On a hospital's patient portal appointment scheduler, that means they can't tell what a field wants or why it failed.

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.

Outcome

With the fix in place on a hospital's patient portal appointment scheduler, they complete the form without guessing.

Who is affected

People with cognitive or motor disabilities who are harmed by retyping the same data.

Learn more

Related scenarios