Most accessibility-lawsuit stories run one direction: a customer can't use a website, and the business gets sued. This one runs backwards. An online florist bought an accessibility overlay, got sued anyway, and then sued the overlay vendor - and in February 2026, a judge said the core of that case can go forward. If you are an Ontario business owner who paid for a widget and told yourself the problem was handled, this is the case worth reading about.
Key facts
- In Bloomsybox.com LLC v. UserWay, Inc. (No. 1:24-cv-00844, U.S. District Court for the District of Delaware), an online flower retailer sued the overlay vendor whose product it had purchased (Law Office of Lainey Feingold).
- BloomsyBox bought a UserWay overlay subscription in July 2023. In December 2023 - about five months later - it was sued by a person who could not use the site (Law Office of Lainey Feingold).
- On February 13, 2026, a Magistrate Judge issued a Report & Recommendation that the key claims - negligent misrepresentation and violation of the Delaware Consumer Fraud Act - should move forward past UserWay's motion to dismiss (Law Office of Lainey Feingold).
- The Magistrate expressly noted it is "too early" to rule on whether UserWay's conduct actually violated the Delaware law. Nothing has been decided on the merits (Law Office of Lainey Feingold).
- Separately, in 2025 the FTC (Federal Trade Commission) finalized a $1 million order against accessiBe over claims its tool could make any website WCAG (Web Content Accessibility Guidelines) compliant (FTC).
So can you sue your overlay vendor?
One business is trying, and it has cleared the first hurdle. That is genuinely notable - but read what the hurdle actually was.
Surviving a motion to dismiss means a court accepted that if everything alleged turned out to be true, there would be a case worth hearing. It is not a finding that the vendor did anything wrong. The Magistrate said so directly: too early to rule on that. And a Report & Recommendation is exactly what the name says - a recommendation that a District Judge still has to adopt. BloomsyBox has won the right to keep arguing. That is the whole win so far.
The theory it gets to argue is the interesting part: that it relied on the vendor's advertising, that the advertising was not true, and that it paid money because of it. That theory rhymes with what the FTC concluded when it finalized its $1M order against accessiBe in 2025 - that a widget vendor had overstated what an automated script can do. Two different bodies, two different processes, same underlying gap between the marketing and the product.
What does this actually do for an Ontario business?
Less than it looks like, and it is worth being blunt about why.
It is a US case, in a US court, under a Delaware consumer-protection statute. An Ontario business does not get to file into that. Whatever BloomsyBox eventually wins or loses, it is not a remedy sitting on your shelf.
It is slow. Look at the timeline: bought in July 2023, sued in December 2023, vendor sued in summer 2024, first meaningful ruling in February 2026. That is more than two years to reach a decision about whether the case can continue. Meanwhile the original accessibility complaint against the florist did not pause and wait.
It does not fix the website. This is the part that matters most. Even a total victory against a vendor is money - it is not a working checkout. The person who could not use the site still could not use the site. Recovering your subscription fee does not remediate a single WCAG failure.
And it does nothing for your exposure at home. In Ontario, the AODA (Accessibility for Ontarians with Disabilities Act) has no private right of action, so the live individual route is a complaint to the HRTO (Human Rights Tribunal of Ontario) under the Ontario Human Rights Code. Your obligation under the IASR (Integrated Accessibility Standards Regulation, O. Reg. 191/11, s.14) to meet WCAG 2.0 Level AA applies to organizations with 50 or more employees, and your next ACR (Accessibility Compliance Report) is due December 31, 2026 for organizations with 20 or more employees (ontario.ca). No lawsuit against a vendor in Delaware changes any of those dates.
So the honest read: the case is a useful signal about what overlays were sold as versus what they do. It is not a plan. The 2026 litigation data already showed that 38.5% of businesses sued over an inaccessible site had a solution installed, usually a widget - BloomsyBox is simply one of those businesses with the receipts and the appetite to go after the seller.
If you have an overlay running right now, the practical move is not to plan litigation. It is to find out what a real user actually hits on your site, fix it in the source rather than patching it in the browser, and keep a dated record of what you checked and repaired. That record is the thing that holds up in front of the HRTO - and unlike a lawsuit against your vendor, it is entirely within your control.
Find out what a real user would hit on your site before a lawyer does - free Vayle Report, about 30 seconds: vayle.art. It detects overlay widgets, surfaces real WCAG failures, and tells you exactly what legally applies to your organization in Ontario. No obligation.
Vayle is a remote-first accessibility-engineering studio serving Ontario. General information, not legal advice.