WCAG 3.3.1: Error Identification
Back to all WCAG criteriaOVERVIEW
Effort:
- Complexity:Easy
- Duration:Fast
Important for:
Design, Development
To WCAG:
3.3.1 Error IdentificationWhat's it about?
If an input error occurs in a form, the error must be described to the user in text form.
How to
Depending on your situation, you can implement one of the following options to meet the criterion. For a deeper dive, please refer to the linked WCAG techniques.
Display errors in text form
If a user leaves a required field empty or enters something incorrectly, an error message must be displayed in text form.
The error message should be placed close to the faulty field. It can be part of the label or displayed below the form field. If it is visually and in the code positioned below the field, it must be programmatically associated with the field. This ensures that screen reader users receive the information as soon as they navigate to the faulty field.
Options for technical association include ARIA attributes (typically aria-describedby).
Create accessible designs?
Our workshop for designers!
Learn everything you need to know as a designer to create accessible design systems for digital products and entire brands.
Learn accessibility with us?
Looking to implement WCAG best practices in your design, development, or content workflow? Book a workshop for your team or contact us directly to learn more.