Minnesota ADA website lawsuits are not a one-off against a household brand. They are a repeatable filing model that pairs ADA Title III with the Minnesota Human Rights Act, names major retail sites, and asks for a detailed accessibility programme (audit, policy, training, WCAG 2.1 Level AA and ongoing testing) rather than a class payout.
That model made fresh headlines in September 2026. On 15 September 2026, Dalton v. Groupon, Inc., No. 0:26-cv-04014, was filed in the U.S. District Court for the District of Minnesota. Open Class Actions reported on 20 September that the complaint alleges groupon.com is inaccessible to screen reader users and that the same plaintiff filed 139 comparable cases in that district in 2025, plus roughly twenty more in the month before Groupon.
This guide is written by accessibility testers who audit retail sites for a living. It is not legal advice. It explains what Minnesota ADA website lawsuits mean for online retailers, what these complaints typically ask companies to do, and a practical preparedness checklist grounded in WCAG and assistive-technology testing.
Minnesota ADA Website Lawsuits At A Glance
- 120: ADA website lawsuits filed in Minnesota from January to June 2026, up 42.86% from 84 a year earlier (Source: EcomBack 2026 mid-year report (opens in a new tab))
- 139: Comparable cases the plaintiff behind Dalton v. Groupon filed in the District of Minnesota in 2025 alone (Source: Open Class Actions (opens in a new tab))
- 24.25%: Share of all U.S. ADA website lawsuits in H1 2026 (496 of 2,045) filed against sites that already had a widget installed (Source: EcomBack 2026 mid-year report (opens in a new tab))
- $0: Class payout: the cases are pleaded as Rule 23(b)(2) injunctive classes, with no fund, claim form or deadline (Source: Open Class Actions (opens in a new tab))
Choose Your Next Step
Most retail teams start with a free call to work out what a Minnesota-style complaint would test on their site. If you already have audit findings or want your developer on a live session, the $100 one-hour technical consultation is the better fit. Fixed prices for testing are on our pricing page (the $500 Quick Audit and the $2,000 Complete Audit), and our ecommerce and retail accessibility page shows how we test storefronts.
Free 30-Minute Call
Best for: retail and e-commerce teams who have seen these filings, or just received a demand letter, and want to know where their storefront stands
A first conversation with our founder about your site, your critical shopping path and what a manual audit would cover. No prep needed. We are accessibility testers, not lawyers, so keep counsel involved in any legal questions.
Book a free 30-minute call (opens in a new tab)
Free Starting-Point Scan (Free scan)
Best for: a quick first look at one page before you talk to anyone
AccessibilityScore.in (opens in a new tab) runs a free axe-core scan of a single public page and flags common code-level issues. Treat it as a starting point: the narration and menu problems pleaded in these complaints need manual screen reader testing to confirm.
Scan a page for free (opens in a new tab)
Already Have A Complaint? (Guide)
Best for: teams holding a demand letter or a filed complaint
Our ADA lawsuit remediation guide covers what to do next: preserve evidence, baseline with manual testing, fix shared templates first and document every change for counsel.

What Happened in Dalton v. Groupon
According to Open Class Actions’ Groupon case page, the complaint was filed on 15 September 2026 against Groupon, Inc. It alleges that groupon.com is not fully and equally accessible to people who are blind or have low vision and who use screen reader software, in violation of Title III of the Americans with Disabilities Act (42 U.S.C. § 12181 et seq.) and the Minnesota Human Rights Act.
The barriers described are allegations. No court has found Groupon liable, no class has been certified, and these Minnesota ADA website lawsuits are not structured to pay class members. Open Class Actions is explicit: the class is pleaded under Rule 23(b)(2) for injunctive relief, not individual damages.
The alleged issues, as summarised by Open Class Actions, map neatly onto WCAG success criteria. Anyone who has run screen reader accessibility testing on a retail site will recognise them:
| Alleged barrier | What a manual test checks | Related WCAG 2.1 criteria |
|---|---|---|
| Unclear link and button purpose | Each link and button announces what it does, even out of context in a screen reader links list | 2.4.4 Link Purpose, 4.1.2 Name, Role, Value |
| Confusing screen reader narration | Content is read in a logical order, with headings, lists and regions exposed as structure | 1.3.1 Info and Relationships, 1.3.2 Meaningful Sequence |
| Menus a screen reader does not recognise | Navigation and menu buttons expose their role and expanded state, and work with the keyboard | 2.1.1 Keyboard, 4.1.2 Name, Role, Value |
| Missing text equivalents for important images | Product, deal and promo images carry alt text that says what a sighted shopper would learn | 1.1.1 Non-text Content |
| Information conveyed only through visual cues | Prices, sale states and errors are not shown by colour, shape or position alone | 1.4.1 Use of Color, 1.3.3 Sensory Characteristics |
Groupon is also not isolated. Between mid-August and mid-September 2026, Open Class Actions reports the same plaintiff filed against Nike, H&M Fashion USA, Marc Jacobs, Sportsman’s Warehouse, iHerb, Untuckit, Rhone, VEJA, Proper Cloth, Paul Fredrick, Impressions Vanity, Johnnie-O, Messika USA, Marubeni America and others, then Groupon. The common thread is a consumer-facing retail website.
For definitions, see our glossaries on ADA Title III and web accessibility lawsuit. For national trends, see our 2026 ADA website lawsuit statistics.
Why Minnesota: ADA Title III Plus the MHRA
Title III of the ADA does not authorise damages for private plaintiffs in these website cases. A successful Title III plaintiff generally seeks an injunction and attorney’s fees, which is one reason many federal accessibility suits resolve around remediation commitments rather than consumer payouts. Minnesota changes the negotiating picture, because the complaints add a state-law claim:
| Question | ADA Title III claim | Minnesota Human Rights Act claim |
|---|---|---|
| Law | 42 U.S.C. § 12181 et seq. (federal) | Minnesota Statutes chapter 363A, public accommodations (§ 363A.11) |
| Damages for the plaintiff | Not available to private plaintiffs | Sought, together with a damages multiplier |
| Other relief asked for | Injunction and attorney’s fees | A civil penalty payable to the State of Minnesota, not to class members |
| Who else enforces it | U.S. Department of Justice | Minnesota Department of Human Rights, alongside private lawsuits |
| Effect on the class | Rule 23(b)(2) injunctive class either way: no fund, no claim form | Changes settlement leverage without changing what class members get |
That combination helps explain why filings cluster in the District of Minnesota even when defendants are national brands headquartered elsewhere. EcomBack’s 2026 mid-year ADA website lawsuit report counts 120 ADA website lawsuits in Minnesota in January to June 2026, up 42.86% from 84 in the same period of 2025, which makes it the most active state outside the four traditional leaders (Illinois, California, New York and Florida).
That does not mean every filing will succeed. It does mean retail operators should treat Minnesota as a high-attention venue and prepare for complaints that seek both federal and state-law remedies.
Minnesota ADA Website Lawsuits and the Frost v. Lion Brand Ruling
Venue matters for another reason too. Three points from recent Minnesota case law shape how these complaints are argued:
What Frost v. Lion Brand held
In early 2025 the District of Minnesota held that a stand-alone retail website is a “place of public accommodation” under Title III.
- Outcome: the retailer’s motion to dismiss was denied (see Ogletree’s summary of the ruling).
- Facts: the plaintiffs, who are legally blind, alleged the site did not work with screen readers.
Keep it in proportion
A district court decision is a signal, not settled law.
- Eighth Circuit: the appeals court covering Minnesota has not decided whether websites are covered.
- Split courts: other federal courts disagree about sites without a physical store, and a district ruling does not bind other judges.
- Next step: ask counsel how it applies to your business.
The standing fight
Defendants often argue that a visitor who browsed and left suffered no concrete injury.
- Groupon complaint: quotes a Minnesota federal judge who rejected that argument from the bench in an earlier case against Wilson Sporting Goods, per Open Class Actions.
- Steger v. Franco (8th Cir. 2000): cited to argue a plaintiff may seek relief for barriers beyond the ones personally encountered.
- Not uniform: courts have split on standing, so outcomes vary case by case.
What it means outside Minnesota
You do not need a Minnesota office to be named in the District of Minnesota.
- Reach: Ogletree reads Frost as a message to any business whose goods or services are available to online shoppers in Minnesota, wherever it is based.
- Evidence: a manual audit of your shopping path gives counsel facts before a complaint does.
- Start here: see how we test storefronts on our ecommerce and retail accessibility page.

7 Lessons at a Glance
| Lesson | What it means for a retail site | Where to go next |
|---|---|---|
| 1. Complaints are allegations | Treat a filing as a testing brief, not a verdict | ADA lawsuit remediation guide |
| 2. Plaintiffs file at scale | Expect repeat reviews; one cleanup without process will not last | 2026 lawsuit statistics |
| 3. Relief sought is a programme spec | Audit, policy, owner, training, vendors, deadlines, testing | Accessibility audit services |
| 4. Retail is the pattern match | Product grids, promos, finders and checkout get tested first | Ecommerce and retail accessibility |
| 5. Overlays are no shield | Budget for code fixes, not a toolbar | Overlay replacement |
| 6. Manual testing is in scope | Keyboard, screen reader and disabled-user sessions | Keyboard testing guide |
| 7. Prepare before you need it | A 10-step checklist mapped to the relief sought | Jump to the checklist |
Lesson 1: Complaints Are Allegations, Not Findings
The first lesson from Minnesota ADA website lawsuits is discipline about language. A filing is a plaintiff’s account of what happened on a particular visit. Open Class Actions stresses that none of the companies named in this wave has been found liable based on these complaints alone.
Treat the complaint as a risk signal and a testing brief, not a public verdict. Preserve the site as it was, document fixes, and commission a manual audit so counsel can separate real barriers from disputed ones. See our ADA demand letter glossary for the vocabulary that often appears before a filing.
Lesson 2: The Same Plaintiff Can File at Scale
Open Class Actions reports that the same plaintiff filed 139 cases in the District of Minnesota in 2025 and roughly twenty more in the month before the Groupon complaint. That pattern matches what accessibility teams already know about serial plaintiff activity nationally: a relatively small number of filers drive a large share of website cases.
EcomBack’s mid-year 2026 data adds national context: 2,045 ADA website lawsuits from January through June 2026 (+1.54% vs 2025), with Illinois leading, Minnesota fifth, and just 30 plaintiffs filing more than half (50.61%) of all cases. The takeaway for retailers: assume a consumer site can be reviewed repeatedly, and that a one-time cleanup without process will not survive the next review.
Lesson 3: Read the Relief Sought as a Programme Spec
For operators, the most useful part of Minnesota ADA website lawsuits is not the brand name in the caption. It is the injunctive relief template. Open Class Actions summarises what the Groupon complaint asks for, and it reads like an accessibility operating model:
| What the complaint asks for | Timing | What it looks like in practice |
|---|---|---|
| Accessibility audit | Within 90 days | A time-boxed manual baseline of the live site (ADA and Section 508 audit) |
| Written digital accessibility policy | Posted in the site header, as pleaded | A short, truthful policy with a working contact route |
| Corrective action strategy | Circulated to executives and contractors | A prioritised fix plan (accessibility remediation) |
| Staff training | Within 12 months | Role-based sessions for content, design and engineering (training workshops) |
| Named staff member | Ongoing | One owner accountable for the policy, with budget and escalation rights |
| Vendor contracts requiring WCAG 2.1 Level AA | For third-party work that touches the site | Accessibility clauses in agency, app and theme contracts |
| All published pages accessible | Within 18 months | Purchase-blocking barriers first, then templates, then content debt |
| Ongoing testing | Monthly automated scans, quarterly manual testing by disabled end users | Testing built into release (monitoring and governance) |
That last item is the one we emphasise in every programme review. Daily deals and seasonal campaigns reintroduce barriers unless accessibility lives in release. W3C WCAG 2.1 Level AA is the conformance target named in the pleadings Open Class Actions describes. For new work we recommend WCAG 2.2 Level AA: it is backward compatible with 2.1 and adds criteria such as Target Size and Focus Not Obscured that matter on product grids and checkout. To see what an audit hands over, open our sample audit report.

Lesson 4: Retail and E-Commerce Sites Are the Pattern Match
The mid-August to mid-September defendant list spans apparel, outdoor retail, supplements, deals platforms and jewellery. The claim model works against any operator whose site is alleged to block screen reader users. Product grids, promo modules, location finders and deal carousels are where narration and keyboard failures show up in our audits, which is why Minnesota ADA website lawsuits keep landing on retail storefronts. Our ecommerce and retail accessibility work starts with exactly those components.
If you run on Shopify, treat the platform as context, not cover. EcomBack counts 952 of the 2,045 national ADA website lawsuits in H1 2026 (46.55%) against Shopify stores, up from 32.42% a year earlier, and lifestyle, fashion and apparel sites drew 565 (27.63%). We cover merchant-side failure modes in Is Shopify ADA Compliant? and our Shopify accessibility audit. The Minnesota wave is about any consumer storefront that can be tested with assistive technology.
Lesson 5: Overlays Are Not a Minnesota Shield
Nearly a quarter of mid-year 2026 ADA website lawsuits (24.25%, or 496 of 2,045 filings) targeted sites that already had an accessibility widget installed, according to EcomBack. Widgets adjust presentation at run time; they do not reliably fix missing names, keyboard traps, or inaccessible checkout-adjacent components.
In April 2025, the FTC finalised an order requiring overlay vendor accessiBe to pay $1 million. See our article on accessibility overlays and ADA lawsuits, and our overlay replacement service if a widget is already on your store. For Minnesota ADA website lawsuits, budget belongs in code, content, process and people, not in a toolbar that leaves barriers in place.
Lesson 6: Manual Testing With Disabled Users Is Explicitly in Scope
The Groupon complaint’s pleaded testing regime (monthly automated scans plus quarterly manual testing by disabled end users) matches what experienced programmes already do. Automated tools catch only a portion of WCAG issues; our automated accessibility testing guide explains where they stop. They cannot judge alt-text accuracy, deal-carousel narration, or whether a locations map works without vision. A practical test stack for teams watching Minnesota ADA website lawsuits:
| Layer | What it covers | When to run it |
|---|---|---|
| Critical path | Home, listing, product or offer, cart and checkout, account, search, location finder, contact | Define once, review each quarter |
| Automated baseline | Contrast, missing labels and empty alt attributes | Monthly, and on every release |
| Keyboard-only pass | Focus order, visible focus, traps in menus, modals and carousels (see our manual keyboard accessibility testing guide) | Each release that touches templates |
| Screen reader testing | NVDA, JAWS, VoiceOver and TalkBack on real shopping flows | Quarterly, and after redesigns |
| Disabled end-user sessions | Real shoppers completing real tasks | On a recurring cadence (quarterly, as pleaded) |
| Regression | Promo modules, new apps and theme updates, which reintroduce debt fastest | After every major release or campaign |
Lesson 7: Build the Preparedness Checklist Before You Need It
Here is a practical checklist we give retail teams when Minnesota is on their risk map. Adapt it with counsel; this is accessibility programme guidance, not legal advice.
| Priority | Action | Why it maps to Minnesota ADA website lawsuits |
|---|---|---|
| 1 | Commission a manual WCAG 2.1 AA audit of the live critical path | Matches the 90-day audit ask and gives counsel facts |
| 2 | Name an accessibility owner with budget and escalation rights | Matches the “named staff member” ask |
| 3 | Publish a truthful accessibility statement with a working contact route | Supports policy and customer feedback loops |
| 4 | Write a digital accessibility policy and socialise it with product, marketing, and vendors | Matches the written policy and corrective strategy asks |
| 5 | Put WCAG 2.1 Level AA into vendor and agency contracts | Matches the vendor-contract ask |
| 6 | Train content, design, and engineering within a 12-month plan | Matches the training ask |
| 7 | Fix purchase-blocking barriers first, then theme-wide issues, then content debt | Supports the 18-month published-pages horizon |
| 8 | Schedule monthly automated scans and quarterly manual / disabled-user testing | Matches the ongoing testing ask |
| 9 | Re-test after campaigns, theme updates, and new apps or widgets | Stops accessibility from decaying between audits |
| 10 | Do not install an overlay as your primary response | Widget-equipped sites still made up 24.25% of H1 2026 suits |
For scoped help, book a free 30-minute call (opens in a new tab) to talk through where your storefront stands, or book the $100 technical consultation if you already have findings or want your developer on a live session. When you are ready for test evidence, the $500 Quick Audit or the $2,000 Complete Audit on our pricing page gives counsel the facts. If you already have a demand letter, involve counsel immediately and use a manual audit as the factual backbone.

What These Suits Mean for Shoppers, and What They Do Not
Open Class Actions is blunt: class members in this Minnesota model should not expect a payout. Title III does not provide damages, the MHRA civil penalty (if awarded) goes to the state, and Rule 23(b)(2) is built for injunctive relief. The potential consumer benefit is a site that works with assistive technology, which blind and low-vision shoppers deserve. Executives should not confuse Minnesota ADA website lawsuits with cheque-mailing class actions. The pressure is remediation and programme maturity.