[Back to 3 Understandable index](index.html)

# 3.3.1 Error Identification

- Level: A
- Guideline: 3.3 Input Assistance
- Principle: 3 Understandable

## What it is

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.

## How to test

- Check: 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.
- Use the sufficient techniques below as acceptable methods when applicable.

## Sufficient techniques (W3C)

- G83: Providing text descriptions to identify required fields that were not completed
- ARIA2: Identifying a required field with the aria-required property
- ARIA21: Using aria-invalid to Indicate An Error Field
- SCR18: Providing client-side validation and alert
- PDF5: Indicating required form controls in PDF forms
- ARIA18: Using aria-alertdialog to Identify Errors
- ARIA19: Using ARIA role=alert or Live Regions to Identify Errors
- G84: Providing a text description when the user provides information that is not in the list of allowed values
- G85: Providing a text description when user input falls outside the required format or values
- SCR32: Providing client-side validation and adding error text via the DOM
- PDF22: Indicating when user input falls outside the required format or values in PDF forms

## Advisory techniques (W3C)

- G139: Creating a mechanism that allows users to jump to errors
- G199: Providing success feedback when data is submitted successfully

## Resources

- WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#error-identification
- Understanding: https://www.w3.org/WAI/WCAG22/Understanding/error-identification.html
- Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#error-identification

[Back to 3 Understandable index](index.html)