Compliant e-Commerce Solutions
What actually holds up under ada scrutiny
compliant e-commerce solutions: what actually holds up under ada scrutiny
compliant e-commerce solutions: what actually holds up under ada scrutiny
In 2023, 4,605 federal website accessibility lawsuits were filed in the United States, according to UsableNet’s annual report. A large share targeted online retail. Apparel, food service, home goods, beauty brands. The pattern isn’t random. E-commerce sites are interactive. They take money. They run on JavaScript-heavy themes. When something breaks for a screen reader or keyboard user, it usually breaks at checkout.
If you run an online store, “compliant e-commerce solutions” isn’t a marketing phrase. It’s risk management. It’s also basic usability.
This is about what actually holds up when a demand letter arrives. Not what passes a free scan.
what “compliant” means for online stores
The legal framework starts with the Americans with Disabilities Act of 1990. Title III applies to private businesses open to the public. Courts have repeatedly said websites tied to retail activity fall under that umbrella.
In 2019, the U.S. Supreme Court declined to review Robles v. Domino’s Pizza. The Ninth Circuit had already ruled that Domino's Pizza had to make its website and app accessible because they connected to physical locations. That left the lower court decision in place.
The Department of Justice has not published detailed technical web regulations for private businesses. Instead, settlements and consent decrees often reference WCAG 2.0 or 2.1 Level AA from the World Wide Web Consortium.
In April 2024, the U.S. Department of Justice finalized a rule requiring state and local governments to meet WCAG 2.1 Level AA under Title II. That rule does not directly govern private e-commerce, but it signals where enforcement thinking sits.
So compliant e-commerce solutions usually mean this in practice: design and build your store to meet WCAG 2.1 Level AA and test it with real assistive technology.
That’s the baseline.
Online stores are more complex than brochure sites. They have:
Product grids.
Variant selectors.
Filters and sorting tools.
Cart drawers.
Checkout forms.
Payment integrations.
Account dashboards.
Each of those layers can fail.
The most common lawsuit issues I see in complaints:
Unlabeled “Add to Cart” buttons.
Color-only sale badges.
Filter menus that open on hover but not with keyboard.
Cart drawers that trap focus.
Error messages that say “Invalid” without context.
CAPTCHAs without audio alternatives.
PDF invoices that are not tagged for screen readers.
None of these are rare. They show up weekly.
In one 2023 complaint filed in the Southern District of New York, the plaintiff described trying to purchase a $79.99 jacket. The size selector used a custom dropdown that could not be opened with keyboard controls. The plaintiff stated they “were unable to complete the transaction independently.” That language is typical.
The barrier wasn’t subtle. It was basic interaction.
the myth of the 95 accessibility score
Many e-commerce brands run Google Lighthouse or Axe and see a score in the 90s. They assume they’re covered.
Automated tools detect missing alt text, low contrast, and obvious ARIA mistakes. They do not simulate an entire checkout flow using NVDA, JAWS, or VoiceOver.
Deque Systems, the company behind Axe, states in its own documentation that automated testing catches only a portion of WCAG issues. Manual testing is required for full coverage.
I audited a mid-sized Shopify store in March 2024. The Lighthouse accessibility score was 94. On the surface, it looked fine.
Using NVDA with Firefox, I attempted to:
Add a product to the cart.
Open the cart drawer.
Proceed to checkout.
Enter shipping details.
The cart drawer opened visually but focus remained behind it. Screen reader users could not access the “Checkout” button. That single issue blocked all sales.
The automated scan did not flag it.
The company fixed it in two days by adjusting focus management in the JavaScript. Before that fix, a lawsuit would have been easy to file.
platform choice and accessibility trade-offs
Compliant e-commerce solutions depend partly on platform.
Shopify, WooCommerce, BigCommerce, Magento, and custom headless builds all have accessibility strengths and weaknesses.
shopify
Shopify powers over 4 million websites globally. Many themes, including Dawn, aim to meet WCAG 2.1 AA at a template level.
The benefit is consistency. Shopify controls checkout markup. That reduces risk in payment flows.
The limitation is theme customization. Third-party apps inject code. Product reviews widgets, upsell popups, subscription tools. Each can introduce accessibility issues.
I’ve seen stores with 18 installed apps. Each loaded scripts into the product page. Several broke keyboard order.
The core theme was compliant. The ecosystem wasn’t.
woocommerce
WooCommerce runs on WordPress. It’s flexible. That’s the upside and the problem.
Accessibility depends on the theme and plugin stack. A developer can build an accessible WooCommerce site. They can also build a mess.
Because WordPress is open, site owners often install low-cost themes from marketplaces. Some are not coded with accessibility in mind.
There’s no centralized checkout like Shopify. More freedom. More risk.
magento and adobe commerce
Adobe Commerce, formerly Magento Commerce, is common in enterprise retail.
Large teams can implement accessibility from the start. They also build complex custom modules.
Enterprise sites often face accessibility lawsuits because they have large traffic volume and deep product catalogs. More pages. More edge cases.
The trade-off is cost. Full accessibility audits on enterprise builds can run $25,000 to $75,000 depending on scope.
what a compliant e-commerce solution actually includes
Compliant solutions are not just themes. They involve process.
Accessible design patterns.
Accessible development standards.
Manual QA with assistive technology.
Ongoing monitoring.
Content governance.
If the product team uploads 300 new product images without alt text, the best code in the world won’t fix it.
product pages
Every product image needs descriptive alt text. Not keyword stuffing. Actual description.
“Blue cotton men’s jacket with zip front” is useful. “IMG_1234” is not.
Variant selectors must be operable by keyboard. If color swatches are clickable divs without proper roles, screen readers won’t recognize them as options.
Price changes triggered by variant selection must be announced to assistive technology. That requires ARIA live regions.
These details matter in lawsuits.
cart and checkout
Checkout is the highest-risk area.
All form fields must have programmatic labels. Placeholder text is not a label. WCAG 2.1 Success Criterion 3.3.2 addresses labels and instructions.
Error messages must:
Identify the field with the error.
Describe the issue.
Explain how to fix it.
“Invalid entry” fails. “ZIP code must be 5 digits” passes.
Focus must move logically. After submitting a form with errors, focus should land on the first error. Not at the top of the page.
Time limits, such as session expiration after 10 minutes, must provide warning and extension options.
These are specific technical requirements. Courts reference them indirectly by citing WCAG.
multimedia and product demos
If you host product demo videos, they need accurate captions. Auto-generated captions are not enough if they contain significant errors.
In 2020, Harvard and MIT settled a lawsuit over inaccurate captions on online video content. That case was under Title II, but the accessibility principle is the same.
If a product video explains assembly steps, and the captions misstate measurements, that’s an accessibility failure.
Audio-only content requires transcripts.
overlays and “one-click compliance” tools
Accessibility overlays claim to make websites compliant through a single script. They add a floating button that changes contrast or font size.
They do not fix underlying code.
Several lawsuits have named companies using overlays. In some cases, plaintiffs alleged the overlay interfered with screen readers.
The core issue is this: overlays operate at the presentation layer. If a form field lacks a label in the DOM, an overlay cannot reliably reconstruct semantic structure.
Some businesses install overlays because they cost $49 to $199 per month. A full manual remediation might cost $15,000.
The trade-off is obvious. Short-term savings. Ongoing legal risk.
real costs of non-compliance
Seyfarth Shaw’s ADA Title III litigation reports have consistently shown thousands of website accessibility lawsuits each year. In 2022, they tracked over 3,200 federal ADA Title III cases overall, many involving websites.
Settlements in e-commerce cases often range from $5,000 to $50,000 plus attorney fees. Some exceed that.
In addition to settlement payments, companies may agree to:
Hire an accessibility consultant.
Conduct annual audits.
Train staff.
Adopt formal accessibility policies.
That compliance work costs money. Doing it after litigation is more expensive.
an anecdote from a small retailer
In late 2023, I worked with a home decor store in Florida generating about $1.2 million annually online. They received a demand letter from a plaintiff who stated they could not apply a discount code at checkout using a screen reader.
The code field existed. It was hidden behind a link labeled “Click here.” That link had no ARIA-expanded state and was not announced clearly.
The plaintiff’s attorney requested $18,500 to settle plus a commitment to remediate within 90 days.
The store had run automated scans quarterly. No flags on that issue.
We fixed the markup in under three hours. The legal negotiation lasted two months.
The cost difference between proactive testing and reactive settlement was significant.
accessibility governance for e-commerce
Compliant e-commerce solutions are ongoing systems, not one-time projects.
That includes:
An internal accessibility policy.
A designated staff contact.
A documented testing schedule.
Vendor accessibility review for third-party apps.
If a marketing team adds a holiday promotion banner that blocks keyboard focus, someone must catch it before it goes live.
Without governance, accessibility debt grows.
mobile accessibility and e-commerce
Mobile commerce now represents more than half of U.S. e-commerce traffic. Accessibility issues differ on mobile.
VoiceOver on iOS handles modals differently from NVDA on desktop. Touch targets must be large enough. Custom gestures can conflict with assistive features.
A mobile site might pass desktop testing but fail on iPhone.
Testing must include mobile assistive technology.
headless commerce and accessibility
Headless builds separate frontend and backend. Developers use frameworks like React or Vue to create custom storefronts.
This gives design flexibility. It also removes guardrails.
Framework components must be built with accessibility in mind from scratch. Focus management, ARIA roles, keyboard handling. Nothing is automatic.
In 2024, I audited a headless commerce build for a fashion brand. The design was visually clean. The code used divs instead of buttons for interactive elements. Screen readers did not announce them as clickable.
The fix required refactoring components across the site.
Headless commerce is not incompatible with accessibility. It just demands experienced developers.
pdfs, receipts, and post-purchase content
Compliance does not end at checkout.
Order confirmation emails must be accessible. HTML emails should use semantic markup. PDF invoices should be tagged.
An untagged PDF receipt may not be readable by screen readers. That can form part of a complaint.
Many businesses overlook this layer.
accessibility statements and feedback channels
Most compliant e-commerce sites publish an accessibility statement. It should include:
Commitment language.
Reference to WCAG 2.1 AA.
Contact method for reporting issues.
A monitored email address or phone number matters. Courts sometimes consider whether a business provides an alternative means of access.
An accessibility statement does not prevent lawsuits. It shows good-faith effort.
If a customer reports a barrier and the company ignores it, that record can appear in litigation.
limitations of full compliance
Perfect accessibility does not exist.
WCAG itself is a technical standard, not a usability guarantee. Meeting every success criterion does not guarantee every user can complete every task.
E-commerce sites integrate payment processors like Stripe or PayPal. If those third-party interfaces have accessibility gaps, the store may still face complaints.
There is also cost. Full audits, remediation, retesting, and training can cost tens of thousands for large catalogs.
Small businesses often struggle with budget. That is a real constraint.
Still, partial compliance with documented progress is better than relying on a badge from an overlay vendor.
what reduces legal exposure in practice
Manual accessibility audits at least annually.
Testing full purchase flows with screen readers and keyboard.
Training developers on semantic HTML and ARIA.
Limiting third-party scripts.
Fixing barriers documented in internal reports.
These steps appear repeatedly in settlement agreements.
Courts and plaintiffs focus on access to goods and services. If a blind user can browse products, add to cart, apply discounts, and check out independently, legal risk drops.
Automated scan scores are secondary.
search engines and accessibility
Google’s ranking systems do not require ADA compliance. There is no direct ranking boost for WCAG conformance.
However, many accessibility practices align with SEO best practices:
Alt text supports image search.
Semantic HTML improves crawlability.
Clear link text improves internal linking.
Structured forms reduce bounce rates.
Accessibility work does not harm SEO. In many cases, it improves it.
That overlap makes compliant e-commerce solutions easier to justify internally.
the bottom line for compliant e-commerce solutions
A compliant e-commerce solution is not a plugin. It is:
Accessible code.
Accessible design.
Real user testing.
Ongoing oversight.
Lawsuits arise from blocked transactions. If a user cannot buy a $49 shirt or complete a $200 order, that is exposure.
The data from UsableNet and Seyfarth Shaw shows litigation volume remains high. The cases describe workflow failures, not abstract code defects.
Automated scanners have value. They catch obvious issues. They do not replicate user experience.
If your store works with a screen reader from homepage to receipt, you have reduced the main source of complaints.
That is what compliant e-commerce solutions actually mean in 2024.