What WCAG 3.3.1 Requires
When a form submission is rejected because of an input error, the error must be described in text and the specific field identified, not just marked visually.
Can AccessBell Test This Automatically?
Not fully. Like most WCAG criteria that depend on meaning or context, this one needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it never gets missed.
How to Test It by Hand
Submit a form with invalid data and confirm a text error message appears identifying exactly which field is wrong and why.
Common Failures
- An invalid field is only highlighted with a red border, with no text describing the problem.
- A generic "form has errors" message appears with no indication of which fields.
Related Criteria in Input Assistance
WCAG 3.3.1 Questions
What does WCAG 3.3.1 require?
When a form submission is rejected because of an input error, the error must be described in text and the specific field identified, not just marked visually.
Can AccessBell test WCAG 3.3.1 automatically?
Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.
What level is WCAG 3.3.1?
Level A, added in WCAG 2.0.
Sources
- W3C: Understanding 3.3.1 Error Identification (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.