• Success Criterion 3.3.7
  • Conformance level A

No Option to Reuse a Previously Entered Value on Later Steps

3.3.7 — Redundant Entry

Scenario

Setting

A government tax-filing portal

What’s wrong

Cross-page processes where selecting a previously provided option isn't offered (no dropdown of prior entries).

Example 

<!-- Schedule A already has a dependent: 'Maya Chen, SSN 123-45-6789' -->
<label for="dep-name">Dependent name</label><input id="dep-name">
<label for="dep-ssn">Dependent SSN</label><input id="dep-ssn">
<!-- Schedule C offers no way to select a previously entered dependent -->

Why it matters

A filer claiming the same dependent on a second schedule has to retype a sensitive SSN by hand, risking a transcription error on a legal document.

How to test

Look for a dropdown or shortcut offering previously entered options on a later step: if selecting a prior entry isn't offered at all, it fails.

How to fix

Offer a selectable list of previously entered values instead of forcing manual retyping on every schedule.

<label for="dep-select">Dependent</label>
<select id="dep-select">
  <option value="maya-chen">Maya Chen (already on file)</option>
  <option value="new">Add a new dependent</option>
</select>

Outcome

The filer selects their dependent from a list instead of retyping a Social Security number a second time.

Who is affected

People with cognitive and motor disabilities for whom retyping a long identification number is both slow and error-prone.

Learn more

Related scenarios