WCAG 3.3.1: Error Identification

Level A

Quick answer: When a user makes an input error, the page should clearly identify the field and the problem.

This criterion is frequently cited in US ADA lawsuits. This criterion is frequently cited in US ADA lawsuits because checkout, account registration, password reset, and coupon flows often fail silently or only use color to signal an error.

In the US, WCAG 2.2 Level AA is the de facto standard for ADA compliance. That is why this criterion matters for Shopify, WooCommerce, Magento, Wix, Squarespace, Webflow, BigCommerce, and custom storefronts selling to US consumers.

Why this criterion matters in US cases

US digital accessibility cases involving retailers and restaurants routinely center on the ability to complete transactions independently. Error identification matters because a user cannot fix a bad ZIP code, card field, or login issue if the form never explains what is wrong.

Common violations on US ecommerce sites

Checkout submits and shows only a red outline with no message.
Coupon forms say “something went wrong” without naming the invalid field.
Account signup highlights several fields but gives one generic summary.
Return-request forms fail silently after an invalid order number.

How to fix it

Name the field and describe the error next to it and in any summary.
Use programmatic invalid states such as aria-invalid when appropriate.
Keep error messages visible after validation instead of relying on toasts.
Ensure server-side and client-side validation return the same useful message.

Start with the live customer journey, not design mocks. Audit homepage, collection, product, cart, account, and checkout-adjacent flows first because those pages create both legal risk and direct revenue loss.

Code example

<label for="zip">ZIP code</label>
<input id="zip" aria-invalid="true" aria-describedby="zip-error">
<p id="zip-error">Enter a valid 5-digit ZIP code.</p>

FAQ

What is WCAG 3.3.1?
When a user makes an input error, the page should clearly identify the field and the problem.

Why does this matter for US ecommerce ADA compliance?
This criterion is frequently cited in US ADA lawsuits because checkout, account registration, password reset, and coupon flows often fail silently or only use color to signal an error.

What standard do US online stores use?
In the US, WCAG 2.2 Level AA is the de facto standard used to evaluate ADA compliance for ecommerce sites.

Check if your US store passes WCAG 3.3.1 → Free ADA Scan — Check Your US Store Now