WCAG 3.3.3 Error Suggestion

WCAG 2.2 success criterion 3.3.3, Error Suggestion, is a Level AA requirement: error messages suggest how to fix the input.

Read the criterion in the W3C Recommendation, WCAG 2.2 (opens in a new tab).

How BearScan checks it

Error messages suggest how to fix the input

Checked automatically: clicks through the page. Severity: medium. Telling a user only that a field is 'invalid' leaves people with cognitive or visual disabilities guessing, and many abandon the form.

An approximation: Up to four forms per page are submitted empty and then with a wrong value (an email without an @, letters in a phone number) in a browser that stops every write, so the messages seen are the ones the page's scripts and the browser's validation show before anything would be sent. A form whose only field is an email address is sent once, to its own site, with a value that is not an address. Forms with a password, a payment card or a file are never submitted. A form made only of selects and checkboxes with nothing required cannot be filled in wrongly and is not applicable. Each message that appears is read by a decisions model (TypeSafe's Jev) for whether it says what is wrong or what to enter; one that only says something failed, with 80% certainty, fails. A message the browser itself writes is accepted. A form that is checked only by its server shows nothing, and is reported for review with that reason.

How to fix it. When validation fails and the fix is known, say it in the error: "Enter the date as DD/MM/YYYY", "Password needs at least 12 characters". Do not do so where it would weaken security.

All WCAG 2.2 criteria · Next: 3.3.4 Error Prevention (Legal, Financial, Data)

Questions

Is WCAG 3.3.3 required by the ADA?

The ADA doesn't name a technical standard for businesses, but the Justice Department's 2022 guidance points businesses to WCAG, and its 2024 rule for state and local governments adopted WCAG 2.1 Level AA, which includes 3.3.3.

Can an automated tool check WCAG 3.3.3?

Mostly. BearScan checks it automatically (clicks through the page). A clean result still isn't proof every page passes, only the pages scanned.

How do I fix a WCAG 3.3.3 failure?

When validation fails and the fix is known, say it in the error: "Enter the date as DD/MM/YYYY", "Password needs at least 12 characters". Do not do so where it would weaken security.