Understandable · Level A · Introduced in WCAG 2.0
WCAG 3.3.1: Error Identification
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
When an input error is detected automatically, identify the field and describe the error in text. A colored border alone does not tell users what went wrong.
A practical example
A registration form rejects a date with only a red outline. Add “Enter a real calendar date” next to the date field and associate it with that field; an error summary can also link back to the problem.
How to check it
- Submit empty, malformed and out-of-range values that the application can detect.
- Check that each affected item is identified and has a meaningful text explanation.
- Verify the error relationship in the accessibility tree and make sure the user can return to the field without losing other entries.
What can be missed
“Something went wrong” may be appropriate for an unknown server failure but is inadequate when a specific input error is known. Keep input errors distinct from service outages.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.