Published November 3, 2026
WCAG 3.3.1 Error Identification, Level A
Does WCAG require form errors to be identified in text?
Yes at Level A. Success criterion 3.3.1 Error Identification requires that if an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. The text is in the W3C WCAG 2.2 Recommendation.
What counts as identifying the error?
Name the field and describe what went wrong in text a person can read or hear. “Email is required” identifies the item. “Invalid” without naming the field does not. The W3C explanation is in Understanding Success Criterion 3.3.1. Labels and format hints before submit are covered under labels or instructions. Broader form patterns are on the accessible forms page.
How is 3.3.1 different from error suggestion?
3.3.1 is Level A and stops at identifying the item and describing the error in text. 3.3.3 Error Suggestion is Level AA and adds a correction when one is known, such as “Use MM/DD/YYYY”. You can meet 3.3.1 without offering a fix. The full answer for suggestions is on the error suggestion page.
Do color and toasts replace text identification?
No. A red border alone fails use of color under 1.4.1, covered on the use of color page, and it fails 3.3.1 because nothing describes the error in text. A toast that only appears visually still needs a status announcement under 4.1.3, covered on the status messages page. Neither substitutes for text that names the field and the problem.
Does the Title II web rule include error identification?
Yes. The Department of Justice rule for state and local government websites names WCAG 2.1 Level AA. That level includes 3.3.1 at Level A. Governments with a population of 50,000 or more have until April 26, 2027. Smaller governments and special districts have until April 26, 2028. Who must comply is on the Title II web rule page. A scanner can flag a missing error message. It often cannot tell that “Invalid” never named the field. A person checks that, which is why a passing score is not conformance, as covered on the scanner page. The fix belongs in the form templates, which is remediation.
Questions and answers
Does WCAG require form errors to be identified in text?
Yes at Level A. Success criterion 3.3.1 Error Identification requires that if an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. A red border alone is not enough. Specification: https://www.w3.org/TR/WCAG22/#error-identification
Is “Invalid input” enough under 3.3.1?
No. The criterion requires identifying the item in error and describing the error in text. “Email is required” or “Password must be at least 8 characters” names the field and the problem. Suggesting a known fix is a separate criterion, 3.3.3: https://www.adasupport.org/error-suggestion
Does a red border meet error identification?
No. Color alone fails 1.4.1 Use of Color, and it also fails 3.3.1 because the error is not described in text. Pair text with any color cue. Color patterns: https://www.adasupport.org/use-of-color
Does the Title II web rule include error identification?
Yes. The DOJ rule names WCAG 2.1 Level AA, which includes 3.3.1 at Level A. Governments of 50,000 or more have until April 26, 2027. Smaller governments and special districts have until April 26, 2028. Deadlines: https://www.adasupport.org/title-ii-web-rule
Related guides
Ask for a review of a specific page
Send the URL and the template you care about. The reply names the highest-risk WCAG failures and the order to fix them.
Request an audit