WCAG 2.1 SC 3.3.1: Error Identification (Level A)
3.3.1 Error Identification (Level A) — what it requires, a common failure example, and how to fix it. Part of WCAG 2.1's 3.3 Input Assistance guideline under the Understandable principle.
WCAG 2.1 guidelines hub → Understandable → 3.3 Input Assistance
3.3.1 Error Identification (Level A)
Input Assistance is the guideline most directly relevant to checkout and account forms — it governs whether people can tell what a field wants, whether errors are described clearly, and whether a costly mistake (an accidental purchase, a wrong shipping address) can be caught before it’s final.
This page is educational technical reference material, not legal advice. Meeting WCAG 2.1 does not by itself determine legal compliance with the ADA or any other law — consult qualified counsel for legal risk questions.
Plain-language explanation: When a form submission has an error, the specific field(s) at fault need to be identified in text — not just with a color change or a generic banner.
Common failure: A checkout form turns invalid fields’ borders red with no text explanation of what’s wrong or which fields are affected, so a screen-reader user gets no error information at all, and a colorblind user may not see the color change either.
Remediation: Programmatically associate an error message with its field (e.g. aria-describedby pointing to visible error text) and describe the specific problem (“Zip code must be 5 digits”), not just “Invalid input.”
In this guideline — 3.3 Input Assistance: 3.3.1 Error Identification (A) · 3.3.2 Labels or Instructions (A) · 3.3.3 Error Suggestion (AA) · 3.3.4 Error Prevention (Legal, Financial, Data) (AA) · 3.3.5 Help (AAA) · 3.3.6 Error Prevention (All) (AAA)
Next: 3.3.2 Labels or Instructions (A) →
↑ Back to the Understandable overview · Full WCAG 2.1 wiki
See a sample report or check pricing — $890 one-time, $99/month for ongoing re-checks after fixes ship.
This page is educational content about technical accessibility practice, not legal advice. Meeting WCAG 2.1 does not guarantee legal compliance with the ADA or any other law. Consult qualified counsel for legal risk questions.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.