- Success Criterion 3.3.3
- Conformance level AA
Correction Suggestions Wrongly Withheld From a Non-Security Field
3.3.3 — Error Suggestion
Scenario
Setting
A music streaming app's playlist screen
What’s wrong
Suggesting corrections that violate security exception boundaries misunderstood in reverse — i.e., *withholding* suggestions for non-security fields citing "policy".
Example
<span class="error">Invalid input</span> Why it matters
People with cognitive disabilities and anyone stalled by vague validation messages.
How to test
Check whether correction suggestions are being withheld from non-security fields citing a security exception that doesn't actually apply to them: misapplied withholding fails.
How to fix
The error message must tell the user how to fix the problem — the expected format, range, or valid options.
<span class="error">Enter a year between 1990 and 2026</span>Error text should suggest the fix — the expected format or valid range — not just flag that something's wrong.
Outcome
On a music streaming app's playlist screen, this barrier is gone for people with cognitive disabilities and anyone stalled by vague validation messages — they get the same result as anyone else here.
Who is affected
People with cognitive disabilities and anyone stalled by vague validation messages.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Rejected Input With No Guidance on How to Fix It
- Invalid Entry Message With No Hint at the Expected Format
- Rejected Date Entry With No Explanation of the Expected Format
- Rejected Password With No List of the Unmet Requirements
- Taken Username With No Suggested Alternatives Offered
- Rejected File Upload With No Stated Size or Type Limits