Published November 2, 2026
WCAG 3.3.3 Error Suggestion, Level AA
Does WCAG require suggestions when a form error is known?
Yes at Level AA when the correction is known. Success criterion 3.3.3 Error Suggestion requires that if an input error is automatically detected and suggestions for correction are known, those suggestions are provided to the user, unless that would jeopardize the security or purpose of the content. The text is in the W3C WCAG 2.2 Recommendation.
How is 3.3.3 different from identifying the error?
Success criterion 3.3.1 Error Identification (Level A) requires that the item in error is identified and described to the user in text, covered on the error identification page. 3.3.3 adds a suggestion when you already know a helpful correction. “Email is required” identifies the field. “Include an @ in the email address” or “Use MM/DD/YYYY” is a suggestion. The W3C explanation is in Understanding Success Criterion 3.3.3. Labels and format hints before submit are covered under labels or instructions. Broader form patterns are on the accessible forms page.
When is a suggestion not required?
When the correction is not known, or when providing it would jeopardize security or purpose. A failed password check typically cannot reveal a close match. A CAPTCHA or authentication step may be limited for the same reason. Accessible sign-in patterns are on the accessible authentication page.
Do color and announcements replace a suggestion?
No. A red border alone fails use of color under 1.4.1, covered on the use of color page. 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, when known, how to fix it.
Does the Title II web rule include error suggestion?
Yes. The Department of Justice rule for state and local government websites names WCAG 2.1 Level AA. That level includes 3.3.3. 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 a known format fix was never offered. 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 suggestions when a form error is known?
Yes at Level AA when the correction is known. Success criterion 3.3.3 Error Suggestion requires that if an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize security or purpose. Specification: https://www.w3.org/TR/WCAG22/#error-suggestion
Is saying “invalid” enough?
No. Identifying that a field failed is 3.3.1 Error Identification. 3.3.3 goes further when you know the fix, such as “Use MM/DD/YYYY” or a close spelling of a city name. Labels before input are 3.3.2: https://www.adasupport.org/labels-or-instructions
Must every error include a suggestion?
Only when the correction is known and providing it would not jeopardize security or the purpose of the content. A wrong password often cannot get a “did you mean” hint. Form patterns are on the accessible forms page: https://www.adasupport.org/accessible-forms
Does the Title II web rule include error suggestion?
Yes. The DOJ rule names WCAG 2.1 Level AA, which includes 3.3.3. 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