WCAG for Ecommerce
WCAG 3.3.2 Labels — Every Input Needs a Label
Users need labels and instructions that explain what information each input expects before they start typing.
For D2C teams, this is not just a standards question. It is a revenue-path question. When a WCAG criterion fails on a product page, filter interface, or checkout form, it creates both customer friction and legal exposure.
What this means in plain English
Users need labels and instructions that explain what information each input expects before they start typing.
On ecommerce sites, this criterion matters because shoppers are rarely reading one clean article. They are evaluating products, interacting with filters, switching variants, reviewing shipping promises, and moving through forms under time pressure. When the underlying accessibility rule breaks, the buying journey breaks with it.
Why it matters for ecommerce
Shipping forms
payment details
gift message fields
subscription opt-ins
ADA complaints against online stores usually do not focus on abstract theory. They focus on failed tasks: a user cannot understand a product image, cannot interpret a discount, cannot complete a form, or cannot recover from an error. That is why even one overlooked success criterion can create outsized legal and commercial risk.
How to check if you comply
Manual test
Tab through forms and confirm each field is announced with a clear label and any required instructions before submission errors appear.
Automated test
Automated scanners catch many missing labels, but custom components and floating-label patterns still need manual verification.
How to fix violations
Pair each form input with a visible label, keep instructions close to the field, and avoid relying on placeholder text alone.
<label for="phone">Phone number</label>
<input id="phone" type="tel" />The best fix is usually at the component level. If the problem lives in a reusable product card, accordion, swatch selector, or form field, repair the shared component once instead of chasing the same violation page by page.
Common mistakes stores make
- Placeholder-only fields
- labels visually hidden without reason
- instruction text far from input
- checkboxes with tiny unlabeled hit areas
These mistakes recur because ecommerce teams optimize for speed, visual merchandising, and third-party integrations. Accessibility gets treated as cleanup work instead of release quality, so the same defect reappears with every new campaign or theme update.
Why this matters legally
In 2025, 8,667 ADA lawsuits were filed across federal and state courts. Plaintiff firms do not need every WCAG failure to build pressure. They only need enough reproducible barriers to show that disabled shoppers cannot access the same buying journey. That makes criteria like WCAG 3.3.2 Labels — Every Input Needs a Label commercially and legally material, not academic.
Related reading
FAQs
Can placeholders count as labels?
No. Placeholders disappear, often have low contrast, and do not provide the same programmatic support as labels.
What forms fail most often?
Email capture, checkout address fields, and embedded app forms are very common offenders.
Do optional instructions matter?
Yes. If a format or rule matters, users should know it before submitting the form.