• Success Criterion 3.3.3
  • Conformance level AA

Rejected Entry With No Suggested Near-Match From a Known List

3.3.3 — Error Suggestion

Scenario

Setting

A community forum's discussion thread

What’s wrong

Search-style inputs with known valid value lists rejecting entries and not suggesting near matches while they're computable.

Example 

<label for="tag">Category tag</label>
<input id="tag" value="acessibility">
<p role="alert">Tag not found.</p>
<!-- 'accessibility' exists in the known tag list but no near match is suggested -->

Why it matters

A member who misspells a common tag gets a flat rejection instead of the one-letter correction the system could easily compute.

How to test

Enter a near-miss value in a field with a known valid list (e.g., a misspelled city name): if no near-match suggestion is offered where feasible, it fails.

How to fix

Run a simple similarity check against the known list and surface the closest match as a suggestion.

<label for="tag">Category tag</label>
<input id="tag" value="acessibility" aria-describedby="tag-error">
<p id="tag-error" role="alert">Tag not found. Did you mean "accessibility"?</p>

Outcome

The member accepts the suggested tag and their post gets categorized correctly right away.

Who is affected

People with dyslexia and other cognitive disabilities who make frequent spelling errors and benefit most from suggested corrections.

Learn more

Related scenarios