• Success Criterion 3.3.7
  • Conformance level A

Email Address Requested Again for No Security Reason

3.3.7 — Redundant Entry

Scenario

Setting

A community forum's discussion thread

What’s wrong

Email/username asked again mid-process for non-security reasons.

Example 

<!-- user is logged in as jordan@example.com -->
<label for="contact-email">Your email</label>
<input id="contact-email">
<!-- the report-a-post form asks for email again for no security purpose, it's just a copied template field -->

Why it matters

A logged-in member reporting a post has to look up and retype their own email address for a form that already knows who they are.

How to test

Check whether email or username is asked again mid-process for non-security reasons: if so, it fails.

How to fix

Pre-fill any field the system already knows from the logged-in session, unless re-entry is a genuine security requirement.

<!-- user is logged in as jordan@example.com -->
<label for="contact-email">Your email</label>
<input id="contact-email" value="jordan@example.com">

Outcome

The member submits the report in one step, without hunting down their own email address.

Who is affected

People with cognitive disabilities and screen reader users who find unnecessary retyping of known information an avoidable barrier.

Learn more

Related scenarios