3.3.1: Error Identification

What it means

When users make an input error, clearly identify the error and describe it in text. Do not rely on colour alone or silent failure.

People need to know what went wrong and where.

How to fix it

• Show an error summary at the top of forms with links to each problem field.
• Mark invalid fields with aria-invalid and connect messages via aria-describedby.
• Write specific messages (“Enter a valid email”) instead of “Error”.
• Announce errors to screen readers when submission fails.

Quick examples

• Good: Submitting an empty form lists “Email is required” next to the email field.
• Bad: Invalid fields turn red with no explanatory text.
• Good: Error summary reads “There are 2 errors” with jump links to fields.
• Bad: Payment fails with a generic “Something went wrong” and no field hints.