Understandable / 3.3 Input Assistance
3.3.1Error Identification
Level AWhen an input error is automatically detected, identify the specific field and describe the error in text. Relying on color or an icon alone fails users who cannot perceive color differences or use a screen reader. Note that automatic error detection is not itself required -- this criterion only kicks in once a site chooses to detect errors.
Note
A detailed commentary for this success criterion is not yet available. In the meantime, this page lists related patterns, techniques, and links to the normative sources.
Related Techniques
Specific implementation techniques for meeting this success criterion. This site doesn't include the full text, so follow the links to the original W3C documents.
Sufficient Techniques(11)
Show all (11)
- ARIA2: Identifying a required field with the aria-required property(opens in a new tab)waic.jp(opens in a new tab)
- ARIA18: Using aria-alertdialog to Identify Errors(opens in a new tab)waic.jp(opens in a new tab)
- ARIA19: Using ARIA role=alert or Live Regions to Identify Errors(opens in a new tab)waic.jp(opens in a new tab)
- ARIA21: Using aria-invalid to Indicate An Error Field(opens in a new tab)waic.jp(opens in a new tab)
- G83: Providing text descriptions to identify required fields that were not completed(opens in a new tab)waic.jp(opens in a new tab)
- G84: Providing a text description when the user provides information that is not in the list of allowed values(opens in a new tab)waic.jp(opens in a new tab)
- G85: Providing a text description when user input falls outside the required format or values(opens in a new tab)waic.jp(opens in a new tab)
- PDF5: Indicating required form controls in PDF forms(opens in a new tab)waic.jp(opens in a new tab)
- PDF22: Indicating when user input falls outside the required format or values in PDF forms(opens in a new tab)waic.jp(opens in a new tab)
- SCR18: Providing client-side validation and alert(opens in a new tab)waic.jp(opens in a new tab)
- SCR32: Providing client-side validation and adding error text via the DOM(opens in a new tab)waic.jp(opens in a new tab)
Normative References
- Success Criterion 3.3.1 Error Identification — WCAG 2.2(opens in a new tab)The normative requirement text.
- Understanding Error Identification — W3C(opens in a new tab)Official guidance on intent, examples, and techniques.