WCAG 3.3.2: Labels or Instructions
Level AQuick answer: Forms need clear labels or instructions before users interact, especially where formatting or business rules matter.
What This Means
On ecommerce sites, Labels or Instructions usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like gift-message fields have character limits that appear only after an error. or promo-code inputs lack any label besides placeholder text., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- Gift-message fields have character limits that appear only after an error.
- Promo-code inputs lack any label besides placeholder text.
- Password creation rules are hidden until form submission.
- Return forms ask for order numbers with no example format.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Provide persistent labels and task guidance before the user submits.
- Explain required formats, limits, and dependencies close to the field.
- Do not rely on placeholders as the only instruction source.
- Update app blocks and embedded forms that commonly drop visible labels.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
<input placeholder="Promo code">
<!-- After -->
<label for="promo">Promo code</label>
<input id="promo" name="promo">FAQ
What is WCAG 3.3.2?
Forms need clear labels or instructions before users interact, especially where formatting or business rules matter.
How does WCAG 3.3.2 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with gift-message fields have character limits that appear only after an error. and promo-code inputs lack any label besides placeholder text. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 3.3.2 violations?
Start by auditing the live storefront, then Provide persistent labels and task guidance before the user submits.; Explain required formats, limits, and dependencies close to the field.; Do not rely on placeholders as the only instruction source.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 3.3.2 → Free ADA Compliance Scan