ADA compliance for ecommerce, fixed where it actually breaks
If you sell online, ADA compliance for ecommerce isn’t optional risk management — it’s the difference between a store every shopper can buy from and one that quietly turns away customers and invites a lawsuit. Curbcut makes online stores genuinely accessible by remediating the code behind your product pages, cart, and checkout to WCAG 2.1 Level AA. No widget, no overlay — real fixes that hold up to screen-reader testing and legal scrutiny.
Ecommerce is the single most-sued category in web accessibility. The reason is simple: online stores are public accommodations, and they’re built from complex, interactive components that break in exactly the ways assistive technology can’t tolerate.
Why ecommerce is the #1 lawsuit target
Under ADA Title III, businesses open to the public must be accessible — and courts and the DOJ have repeatedly applied that to websites. Thousands of ADA web accessibility lawsuits are filed each year in the US, and retail and ecommerce sites consistently top the list. Serial plaintiffs and their firms scan for stores with obvious barriers, then send a demand letter or file suit.
Online stores are uniquely exposed because:
- They have more interactive surface area than a typical brochure site — filters, swatches, carts, and checkouts.
- They process transactions, so a blocked checkout is a direct, demonstrable harm.
- They’re easy to test at scale, so a plaintiff can find dozens of failing stores in an afternoon.
For the legal landscape and how the lawsuit wave plays out, see our pillar on ADA website lawsuits. This page isn’t legal advice — for your specific exposure, talk to an attorney.
Where online stores fail WCAG 2.1 AA
The POUR principles — Perceivable, Operable, Understandable, Robust — map directly onto the parts of a store that break most. Here’s where we find the most blocking issues during an accessibility audit.
| Store area | Common failure | What it blocks |
|---|---|---|
| Product images | Missing or generic alt text | Screen-reader users can’t tell products apart |
| Filters / faceted search | Custom controls with no ARIA roles or state | Keyboard and screen-reader users can’t refine results |
| Color/size swatches | Unlabeled buttons, no selected state announced | Users can’t tell what they picked |
| Add-to-cart & quantity | Non-focusable buttons, no status announcement | Keyboard users can’t add items |
| Mini-cart / drawer | Focus not trapped, no close announcement | Focus gets lost behind the overlay |
| Checkout forms | Unlabeled fields, color contrast errors, inaccessible validation | The sale fails at the last step |
Product pages and images
Every product image needs descriptive alt text that conveys what matters to a buyer — not “IMG_4821.jpg.” Decorative thumbnails should be hidden from assistive technology. Our alt text guide covers how to write it for a catalog. Price, availability, and variant changes must also be announced, not just shown visually.
Filters, cart, and checkout
Faceted filters are the most common custom-component failure on a store. They need proper roles, labels, and state so screen readers (NVDA, JAWS, VoiceOver) announce what’s selected. The cart and checkout must be fully operable by keyboard navigation alone — tab order, visible focus, and accessible error messages. Checkout is a form, so it lives or dies on label associations and contrast; see accessible forms for the patterns we apply.
Why overlays fail ecommerce specifically
Overlays (the accessiBe / UserWay / AudioEye class of widgets) promise instant compliance with one line of JavaScript. They don’t work — and they fail ecommerce hardest. An overlay can’t restructure your filter component, fix a broken cart drawer’s focus order, or write meaningful alt text for 5,000 SKUs. It sits on top of broken code while the barriers remain underneath, and stores using overlays are still sued. Courts have not accepted overlays as a defense.
Manual remediation is the only durable fix: we edit the theme, templates, and component code so the store is actually robust for assistive technology. Compare the two approaches in overlay vs. manual remediation.
Built for your platform
Most small-business stores run on a handful of platforms, and each has its own accessibility quirks at the theme and app layer:
- Shopify — theme Liquid templates, app-injected widgets, and checkout customizations.
- WooCommerce — WordPress themes and plugins that control product loops and cart behavior.
We remediate inside your stack rather than bolting something on top, so the fixes survive theme updates and stay maintainable.
What Curbcut delivers for ecommerce
- A manual + automated accessibility audit of your store against WCAG 2.1 AA (conformance levels A / AA, with AAA noted where relevant).
- Remediation of product, collection, cart, and checkout templates in your actual codebase.
- A VPAT / Accessibility Conformance Report documenting your status for buyers and procurement.
- An accessibility statement for your storefront.
- Optional ongoing monitoring so new products and theme changes don’t reintroduce barriers.
Curbcut focuses on private-sector ecommerce, but the same standards underpin Section 508 for federal contexts — the underlying technical bar is WCAG, so the framework you target rarely changes the engineering work.
Start with a free scan
The fastest way to see where your store stands is a free accessibility scan — a quick first look at the issues hurting your shoppers and raising your legal risk. From there we scope a manual audit and a remediation sprint sized to your catalog and budget.
For deeper background, the W3C Web Accessibility Initiative, ADA.gov, and WebAIM are reputable, free references — and Section508.gov covers the federal standard. Then let Curbcut do the part that actually fixes your store.