AI Accessibility Widgets After the FTC's accessiBe Order

In April 2025 the Federal Trade Commission finalized an order requiring accessiBe, which sells an AI accessibility widget for websites, to pay $1 million. The FTC's complaint said accessiBe claimed its "one line of code" would make a website compliant with the Web Content Accessibility Guidelines (WCAG), and that the claim was false or unsubstantiated. accessiBe agreed to the order without admitting or denying the allegations.

The plan the complaint describes cost "$49 monthly or $490 annually". accessiBe's cheapest plan today is $490 a year, aimed at "Family-owned business and Entrepreneurs".

The order gets misread in two opposite directions.

• "Widgets are illegal now, or using one makes you liable." No. The order governs accessiBe's advertising. It doesn't mention the Americans with Disabilities Act at all, or customers' own obligations under it. Customers appear only as buyers accessiBe must warn before they pay, and as possible refund recipients.
• "There's no federal accessibility rule for business websites, so there's nothing to worry about." Also no. The Justice Department has no regulation setting detailed web standards for businesses, but it says the ADA applies to what they offer online. Plaintiffs filed 3,117 website accessibility lawsuits in federal courts in 2025, by the count of a law firm that defends businesses; other trackers count differently.

A widget doesn't make your site compliant, and the absence of an official standard doesn't make it safe. It means there's no safe harbor.

We read the FTC's complaint and order, the Justice Department's rules, guidance and court filing, the statute, and the lawsuit reports named below, on 10 September 2026, and re-read the vendor pages and the attorney's-fees section on 14 September. This isn't legal advice, and we aren't lawyers. If you've received a demand letter, a lawyer licensed where the claim was filed, or would be, is the next step.

What the FTC said the widget couldn't do

The FTC's case is a detailed public record of an AI accessibility widget measured against its own marketing. From the complaint, which states allegations accessiBe neither admitted nor denied:

• The promise. "One line of code" made a site compliant "with 30% of WCAG's requirements immediately", with the rest within 48 hours, and the widget kept it compliant "by re-scanning the website every 24 hours".
• What stayed broken. Barriers on sites running the widget included "missing or inaccurate alt text for key images", a missing focus indicator, keyboard traps, "incorrect headings; and problems with menus, buttons, and tables".
• What it didn't fix unless you paid more. "Unless additional services are purchased", it didn't make accessible "documents, PowerPoint, Excel, Word, PDF, audio, video, certain graphic image files, embedded" content.
• The testing. "No automated testing tool alone can determine if a website meets" accessibility standards, and "accessiBe's own testers identified errors on nearly all websites tested."
• The reviews. The complaint also charged accessiBe with running "advertisements disguised as" independent reviews. In one case, it said, accessiBe "paid $1,900 for the review and approved it prior to its publication". In some instances, it said, accessiBe asked the reviewer to remove any designation that the review was "sponsored".

What the final order, issued in April 2025, requires:

• Payment: accessiBe "must pay to the Commission $1,000,000."
• Claims: no saying an automated product "can make any website compliant with WCAG" or "can ensure continued automatic compliance with WCAG over time" without "competent and reliable evidence".
• Disclosure: before a buyer pays, disclose that the product "will not correct barriers on third-party web domains or subdomains that may be part of the overall user experience, unless those domains also use the product". That's a booking page or checkout hosted somewhere else.
• Reviews: no presenting paid reviews as independent opinions.

It doesn't ban selling or using widgets.

As of 14 September 2026, accessiBe's homepage calls its product "Expert-driven. AI-powered." and sells "WCAG 2.2 AA-based remediation for legal compliance". Its pricing page lists "Comprehensive Litigation Support" from the $1,490-a-year Growth plan up, and manual testing from the $3,990-a-year Scale plan up. The $490 plan includes neither. Whether the compliance claims are substantiated isn't something we can judge from outside.

No official standard is not the same as no risk

The 2024 federal web rule isn't about your business. The Justice Department's April 2024 rule says it plainly: "Title II of the ADA, which this rule addresses, applies to State and local government entities." It requires those governments' websites and apps to meet "the WCAG 2.1 Level AA success criteria". The department had decided to "pursue separate rulemakings addressing web accessibility under titles II and III", and title III, the part covering businesses open to the public, had no web regulation as of September 2026 (we couldn't open the federal regulatory agenda to check for a pending one). In April 2026 an interim final rule gave governments another year: April 26, 2027 for larger entities, April 26, 2028 for smaller ones.

But the department says the obligation exists. Its web guidance, dated March 2022 and still on ada.gov, says "the Department has consistently taken the position that the ADA's requirements apply to all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web." It "does not have a regulation setting out detailed standards", so businesses "can currently choose how they will ensure" accessibility. WCAG is described as "helpful guidance".

And it won't say which standard is enough. In February 2026 the department objected to a proposed class settlement in a California website case, Alcazar v. Fashion Nova, Inc. (N.D. Cal. No. 4:20-cv-01434). A footnote in its filing told the court: "The United States does not endorse WCAG as the appropriate or necessary standard for the provision of auxiliary aids and services under Title III of the ADA." The same footnote says the department applied WCAG only to the settlement's own claims website, because that was the standard the plaintiff had chosen in the proposed settlement. The same filing said it "does not oppose relief that would actually make a website available to individuals who are blind or have low vision".

Taken together:

• the law applies;
• no regulation says what satisfies it;
• the agency that enforces it won't vouch for the standard everyone uses.

That gap is where private lawsuits get filed.

Who gets sued, counted by people with something to sell

Nobody neutral counts these cases. The two counts we found come from a law firm that defends businesses and a company that sells accessibility fixes, and they measure different things.

A management-side law firm's ADA blog counted website accessibility lawsuits in federal courts:

• 3,117 in 2025, "a 27% increase from 2024";
• 36% of all 8,667 federal title III suits;
• New York led; Florida had 961 and Illinois 585;
• California's federal courts had four.

The firm built the count from keyword searches of court-filing data, reviewed by hand.

UsableNet, which sells accessibility remediation, counted more than 5,000 digital accessibility suits. That total covers apps and video as well as websites, in federal courts plus New York and California state courts.

• 1,427 of its federal cases, 45%, were against companies that had already been sued.
• 64% were against companies with under $25 million in revenue. That's a long way above a one-person business, and no count we found goes lower.
• Its month-by-month figures for suits against companies using widgets add up to 1,416 in 2025.
• Its conclusion: "Accessibility widgets did not slow litigation in 2025."

UsableNet competes with widget makers, so read that conclusion with its incentive in view. Its figures show that sites with widgets still get sued. They can't show whether a widget makes a suit more or less likely, because nobody reports how many sites use one.

Where the courts are.

• The Ninth Circuit held in Robles v. Domino's Pizza, LLC (913 F.3d 898, 2019) that the chain's website and app were covered because of their "nexus" to its physical restaurants. It said it "need not decide" whether the ADA covers a physical business's site whose inaccessibility doesn't block access to the location itself.
• The Eleventh Circuit's 2021 opinion in Gil v. Winn-Dixie Stores, Inc., that websites aren't places of public accommodation, was vacated as moot that December, so it isn't law.
• An online-only business sits in territory no binding decision we found has settled. Law-firm summaries we couldn't verify at source say some circuits require a link to a physical place. Unsettled is not the same as exempt.

What a claim can cost.

• Federal remedies. The ADA's enforcement section describes injunctive relief in private title III suits: orders to make things accessible. It mentions money damages in suits brought by the Attorney General, "when requested by the Attorney General", along with civil penalties. Those penalties are now up to $118,225 for a first violation and $236,451 for a later one, after inflation adjustments.
• Attorney's fees. A separate section lets a court award "the prevailing party … a reasonable attorney's fee, including litigation expenses, and costs" (42 U.S.C. § 12205). A federal suit asking only for a fix can still cost you the other side's lawyers.
• State law adds money. California's Unruh Act makes whoever discriminates liable "for each and every offense" for actual damages, "but in no case less than four thousand dollars ($4,000)", plus attorney's fees. What counts as a separate offense for a website isn't settled in anything we read. The California case the Justice Department weighed in on was pleaded under both the ADA and Unruh.
• A bill that isn't law. New York's S3237 would require sixty days' notice before a suit over a website that "describes goods and services provided at a place of public accommodation". On our reading, that may not reach an online-only business. As of 14 September 2026 it was in committee, referred again in January 2026.

What a widget can and can't do

• W3C, which publishes WCAG: "Web accessibility evaluation tools can not determine accessibility, they can only assist in doing so." And: "Human judgement is required."

• WebAIM's 2026 scan of the top million home pages found detectable WCAG failures on 95.9% of them, up from 94.8% a year earlier. The most common:

  • low-contrast text, 83.9%;
  • missing image alt text, 53.1%;
  • missing form labels, 51%;
  • empty links, 46.3%;
  • empty buttons, 30.6%;
  • missing page language, 13.5%.

  WebAIM adds: "Absence of detected errors does not indicate that a page is accessible or conformant."

• The Justice Department's 2024 rule recorded that "Several comments expressed concerns about public entities using accessibility overlays and automated checkers". It didn't address how an entity meets the standard, so it neither approved overlays nor banned them.

• Guarantees pay; they don't fix. AudioEye's legal guarantee, as its page read on 10 September 2026, pays "up to the set coverage or the total settlement for the demand letter or lawsuit, whichever is less", and won't pay for "false positives", which it says "show that we did our work correctly". accessiBe includes litigation support from its $1,490-a-year plan up. Either may help with a claim, but neither makes the site usable, which is what the Justice Department's filing said it cares about.

An afternoon of checks instead

These follow WebAIM's most common failures and the barriers in the FTC's complaint. Automated checkers help find problems; a keyboard and your own eyes do the rest.

1. Contrast. Normal-size text needs a contrast ratio of "at least 4.5:1" against its background, and large text "at least 3:1", per W3C's criterion. Check small grey text on coloured cards; that's where ours failed.
2. Alt text. Every meaningful image gets a short description. Purely decorative images get an empty one.
3. Labels. Every form field (newsletter signup, contact form, checkout) has a label.
4. Names for links and buttons. An icon with no text needs a label a screen reader can announce.
5. Page language, set in your site builder or template.
6. Keyboard. Put the mouse away and tab through the site, including booking and checkout. You should always be able to see where you are, and never get stuck.
7. Captions on your videos, and an accessible version of anything you only offer as a PDF.
8. Third-party embeds. Booking tools and payment pages on someone else's domain are part of your customer's journey. The FTC made accessiBe tell buyers its widget can't fix them unless those domains use it too. Choose ones that are accessible themselves.
9. An accessibility contact on the site, and a dated note of what you checked. That's evidence of good faith, not a legal shield, and it's our suggestion rather than a rule.
10. If a demand letter arrives, don't ignore it, and don't assume a widget purchase resolves it. Talk to a lawyer licensed in the state where the claim was filed, or would be.

What we checked on our own site

We don't run an accessibility widget, and none of our articles recommends one. Before publishing, we ran automated checks on four pages of a local build: our home page, an article, our tools page and our newsletter page.

• What passed: each of those pages declares its language, every image on them has an alt attribute, every form field has a label, and every link and button has a name.
• What was missing: a skip link. WCAG's criterion on bypassing repeated blocks can be met other ways, but a skip link is the common one.
• One text colour failed. We computed the contrast of our colour tokens: the light grey we use for dates, prices and card details came to 4.44:1 on our card backgrounds, just under 4.5:1. The ad placeholder label was fainter still, because two transparency layers sat on top of it.

What we changed on 10 September 2026:

• that grey is slightly darker: 4.63:1 on cards and 4.93:1 on the page background, and we measured 4.63:1 on the rendered page;
• the placeholder's transparency is gone;
• every page now has a "Skip to content" link as the first thing a keyboard reaches.

Our dark theme passed on every pair we measured.

Those were automated checks and a contrast calculation. We haven't tested the site with a screen reader, and by W3C's own account, tools can't tell us the site is accessible.

The rest of the fine print

This belongs to a set of articles on the terms and rules underneath the tools a one-person business runs on:

• who owns what AI tools produce
• whether you can put client data into ChatGPT
• whose job consent is when a notetaker joins a call
• what Canva's license allows for logos and client work
• what the FTC's fake reviews rule means for AI testimonials
• what payment processors' contracts let them do with your money

---

Last reviewed 14 September 2026. Not legal advice; we are not lawyers. Read at source on 10 September 2026, with accessiBe's pricing page and 42 U.S.C. § 12205 read on 14 September: the FTC's complaint (January 2025) and final Decision and Order (issued 21 April 2025) against accessiBe, and its announcements of both; the Justice Department's title II web rule (89 FR 31320, April 2024), its interim final rule extending the dates (91 FR 20902, April 2026), its web guidance (March 2022) and its statement of interest filed 2 February 2026 in N.D. Cal. No. 4:20-cv-01434; 42 U.S.C. § 12188 and 28 CFR 85.5; the Ninth Circuit's 2019 opinion and the Eleventh Circuit's December 2021 vacatur; California Civil Code § 52; New York Senate Bill S3237; a management-side law firm's 2025 federal filing count (March 2026) and UsableNet's 2025 year-end report; WebAIM's Million report (2026); W3C's pages on evaluation tools and on contrast; and accessiBe's and AudioEye's own pages. Not read: any court decision settling whether an online-only business is covered, and the European Accessibility Act's text. No link in this article pays us; see how we make money.