ADA Compliance for Ecommerce Websites

Online retailers face more ADA accessibility lawsuits than any other industry — by a wide margin. Roughly 35 to 40 percent of all federal ADA web cases filed each year target ecommerce sites, with another large share landing in California state court under the Unruh Civil Rights Act. The reason is structural: an inaccessible online store directly prevents a disabled consumer from completing a transaction, which is the strongest possible evidence of discrimination under Title III of the ADA. This guide covers exactly why ecommerce gets targeted, what violations plaintiff attorneys cite most often, and what remediation actually costs.

This page is informational and is not legal advice. ADA, federal regulations, and state-law obligations vary by jurisdiction and business type — consult qualified counsel for case-specific guidance.

Why courts treat ecommerce sites as public accommodations

The legal foundation for ecommerce ADA exposure was set in the Ninth Circuit's decision in Robles v. Domino's Pizza (2019). The court ruled that Title III of the ADA applies to websites and mobile apps that have a sufficient nexus to a physical place of public accommodation. The Supreme Court declined to hear Domino's appeal, effectively cementing the rule across the Ninth Circuit and influencing courts nationwide.

For ecommerce specifically, even sites with no physical storefront have been held subject to Title III. The Eleventh Circuit ruled in Gil v. Winn-Dixie (2017) that a grocery chain's website was a place of public accommodation because it was tightly integrated with the in-store experience. The First Circuit went further in Carparts Distribution Center v. Automotive Wholesaler's Association (1994) and treated internet-only services as covered. Courts in the Second and Seventh Circuits have taken increasingly broad views as well. The result is a patchwork where most ecommerce companies face real exposure regardless of their physical footprint, and plaintiff firms specifically target circuits with the most favorable case law.

The ten elements ecommerce plaintiffs almost always cite

Demand letters and complaints in ecommerce ADA cases follow a recognizable pattern. Plaintiff attorneys use automated scanners that flag the same categories of violations again and again, then paper a complaint with the most actionable items. The list below covers what shows up in roughly nine out of ten ecommerce demand letters filed in 2025-2026:

1. Product images without descriptive alt text.Plaintiffs will count each unlabeled product image as a separate violation, which is how complaints reach 50-200 listed issues even on small catalogs.
2. Search inputs and filter controls without labels.Faceted navigation (size, color, price filters) is frequently built with custom components that lack proper ARIA labeling.
3. Add-to-cart buttons announced as "button" with no context. Icon-only buttons need an accessible name.
4. Cart and checkout forms with missing or programmatically disconnected labels. Address inputs, card number fields, and shipping selectors are often the worst offenders.
5. Modal dialogs without focus management.Quick-view product modals, size guides, and login/signup dialogs frequently trap or misroute keyboard focus.
6. Inaccessible image carousels and product galleries.Auto-rotating carousels without pause controls violate WCAG 2.2.2; many also lack keyboard navigation.
7. Color contrast failures on sale prices, badges, and CTAs. Light gray text on white, light text on gradient backgrounds, and low-contrast "limited" badges are routine findings.
8. Custom dropdowns, accordions, and tabs without proper ARIA roles. Collapsible product description sections are a particularly common failure point.
9. Inaccessible cookie consent banners. The consent overlay frequently traps focus and blocks screen reader users from reaching the actual page content.
10. PDF spec sheets and size charts that are not tagged. Furniture, electronics, and apparel sites routinely link to image-only or untagged PDFs that screen readers cannot parse.

Platform-specific failure patterns

Shopify stores are vulnerable through their theme layer. Most Shopify themes pass automated scans on a blank install but break the moment merchants add custom Liquid sections, third-party apps, or alter the cart drawer. The Shopify-recommended Dawn theme is reasonably accessible by default, but stores using older themes (Debut, Brooklyn, Venture) or heavily modified custom themes routinely accumulate dozens of violations.

WooCommerce stores present a different problem: the underlying WordPress accessibility depends entirely on the theme and plugin stack. Page builders like Elementor and Divi generate non-semantic markup that is hostile to screen readers unless the merchant explicitly enables their accessibility features. WooCommerce's default cart and checkout forms are reasonably labeled, but custom checkout plugins frequently break those labels.

Magento and Adobe Commerce sites typically have larger violation counts because they tend to host bigger catalogs with more custom development. The Luma theme has known accessible navigation but many merchants run heavily customized themes built against an older Magento version. Decoupled Magento storefronts (PWA Studio, Vue Storefront) require careful ARIA work because single-page applications frequently fail to announce route changes.

BigCommerce, Squarespace Commerce, and Wix Storestend to fall in the middle. Their default templates handle the basics, but their visual editors make it easy for non-technical merchants to introduce contrast failures, unlabeled icons, and decorative images that should have been marked decorative.

What ecommerce remediation actually costs

Real cost depends on three factors: store size (number of unique page templates, not products), platform, and how much custom development sits on top of the platform. Here is what we see across actual remediation engagements in 2025-2026:

These ranges assume real code remediation, not the installation of an overlay widget. Overlays cost $50-$500 per month and have been ruled insufficient for ADA compliance by federal courts including in Murphy v. Eyebobs and Sullivan v. Studio Direct. Settlement agreements increasingly prohibit overlay-only remediation.

How to audit your own ecommerce site

A real audit covers three layers: automated scanning, manual keyboard testing, and screen reader testing of the critical paths. Automated tools catch only 30-50 percent of WCAG failures, but they catch the same things plaintiff attorneys scan for, so they are the right starting point.

1. Run an automated WCAG 2.1 AA scan on these specific URL patterns: homepage, a category page, a product detail page, the cart, the checkout (each step), the search results page, and the account/order history pages. These cover the transactional path that plaintiffs almost always cite.
2. Navigate the entire purchase funnel using only the keyboard (Tab, Shift+Tab, Enter, Space, arrow keys). If you cannot reach a button or your focus disappears, that is a violation.
3. Test the checkout with a screen reader (NVDA on Windows, VoiceOver on macOS). Pay specific attention to whether form errors are announced and whether the submit button is clearly labeled.
4. Verify color contrast on prices, "sale" badges, disclaimers, fine print, and CTA hover states using a tool like Stark or Colour Contrast Analyser.
5. Audit any PDFs you link to (size charts, spec sheets, warranties) for proper tagging and reading order.

The accessibility-conversion connection

ADA compliance is usually framed as legal risk management, but for ecommerce the conversion impact often matters more. Click and Forrester research shows that about 16 percent of US adults have a disability that affects how they use websites — vision, motor, cognitive, or auditory. Inaccessible sites lose those customers entirely. The CDC puts the disability community's spending power at over $490 billion annually. Inaccessible checkouts disproportionately harm conversion among older shoppers (who have higher average order values) because age- related vision and motor changes overlap heavily with the failures plaintiffs cite.

Search ranking is a smaller but real factor: Google's Lighthouse accessibility score is a documented Core Web Vitals input, and several of the WCAG criteria (semantic markup, heading hierarchy, image alt text, descriptive link text) are also direct on-page SEO inputs. Sites that achieve genuine WCAG 2.1 AA compliance typically see modest organic traffic gains as a side effect.

What to do today

If you have not run an audit on your store in the last six months, do it now. The vast majority of ecommerce demand letters cite issues that are detectable with automated tools, so a real scan tells you within 60 seconds whether you have obvious exposure. Once you have a violation list, prioritize the cart and checkout flow first — that path drives most of the legal risk and most of the abandoned-cart conversion losses. Customer-facing product detail pages come next, then the homepage and category pages.

Avoid overlay widgets. They do not provide compliance, they interfere with assistive technology, and several have themselves been the subject of class action lawsuits. If a vendor pitches you an "instant ADA compliance" JavaScript widget, the answer is no.