• Success Criterion 3.3.2
  • Conformance level A

Required Input Format Never Stated Until After an Error

3.3.2 — Labels or Instructions

Scenario

Setting

A dating app's profile setup

What’s wrong

Required format not stated (date format, password rules) until after error.

Example 

<label for="password">Password</label>
<input id="password" type="password">
<!-- rules (8+ chars, 1 number, 1 symbol) only appear in the error message after a failed submit -->

Why it matters

A user typing a password has no idea what's required until after they submit and get rejected, so they retype blindly two or three times.

How to test

Try submitting a field with a specific required format (date, password) without reading any instructions: if the format is only revealed after you get it wrong, it fails.

How to fix

State the format requirement up front, tied to the field, not only inside a post-submission error.

<label for="password">Password</label>
<p id="password-hint">At least 8 characters, including 1 number and 1 symbol.</p>
<input id="password" type="password" aria-describedby="password-hint">

Outcome

The user builds a valid password on the first attempt and finishes setting up their profile.

Who is affected

People with cognitive disabilities and screen reader users who benefit most from knowing requirements in advance rather than discovering them through trial and error.

Learn more

Related scenarios