Skip to main content
a promotional graphic telling you that PCI Compliance is no longer an annual exercise and that continuous monitory must be built in
accessiBe's $1M FTC Fine Is a Vendor Oversight LessonAssistive Technologies
5 min readFor GRC Leaders

accessiBe's $1M FTC Fine Is a Vendor Oversight Lesson

The U.S. Federal Trade Commission has fined accessiBe $1 million for false advertising and for compensating reviewers without disclosing sponsorship. accessiBe sells a product claiming to make websites more compatible with the screen readers blind people rely on. This penalty highlights a crucial lesson for your team: a vendor's marketing claims aren't proof of compliance, and your organization bears the risk when accepting them as such.

Why These Mistakes Keep Happening

Accessible Procurement often goes through marketing, IT, or a general vendor management queue. Few in that chain can test claims against WCAG, so they accept what's presented: a polished sales deck, reviews, a badge. AI-driven tools intensify this pull. A script promising remediation without code changes sounds like a cost-saving measure, tempting under budget pressure.

No one in that process verifies claims. The mistakes below stem from this gap.

Mistake 1: Treating Vendor Claims as Conformance Evidence

Why It Happens: Claims come in forms teams expect from compliance documents: confident, specific, and professionally designed. Without a standard for evidence, "makes your site WCAG compliant" gets filed alongside actual test results.

Consequence: The FTC action focused on advertising claims that didn't hold up. If you relied on those claims, you're left with a purchase order and a risk register entry citing unverifiable information. That's a weak position under ADA Title III or any demand letter.

Fix: Define what evidence your organization accepts. An Accessibility Conformance Report based on the Voluntary Product Accessibility Template is a start, not an end. Require it to identify the WCAG version tested, methods used, and Assistive Technology involved. Then run your own Conformance Testing on a sample of pages before and after deployment.

Mistake 2: Relying Solely on AI for Remediation

Why It Happens: Automated tools can detect some WCAG failures, and AI-driven overlays can alter code Assistive Technology runtime. Leaders might conclude that detection plus automatic fixing equals resolution. However, many failures need human judgment: whether alt text is meaningful, whether focus order makes sense, whether a custom widget exposes the right WAI-ARIA roles and states.

Consequence: You get a dashboard claiming issues are resolved while real users still encounter barriers. Your audit trail shows a known risk handled with an unverified control.

Fix: Treat AI output as a draft needing validation. Pair automated scanning with Screen Reader Testing and keyboard-only testing by people who use Assistive Technology regularly. Document who reviewed what, and when. Where AI makes a change, test it.

Mistake 3: Trusting Reviews and Testimonials Without Checking Sponsorship

Why It Happens: Peer reviews seem independent. A page of five-star ratings from named reviewers reads as market validation, and few procurement checklists ask who paid for the praise.

Consequence: The FTC found that accessiBe compensated reviewers without disclosing sponsorship. If your vendor selection relied on that material, your due diligence rested on paid endorsements. Even if no one challenges your decision, it's hard to defend in front of your board or an auditor.

Fix: Add disclosure questions to your vendor questionnaire. Ask whether reviewers, case study participants, or endorsers received compensation or incentives. Weight evidence from your own testing and from references you source independently. Seek input from disabled users and accessibility practitioners with no commercial tie to the vendor.

Mistake 4: Letting Marketing Language Flow Into Your Own Public Statements

Why It Happens: Once a tool is deployed, teams naturally repeat the vendor's framing. The accessibility statement says the site is "fully accessible" or "WCAG compliant" because that's what the product page said.

Consequence: You've turned a vendor's claim into your own representation. If testing contradicts it, you've created exposure that didn't exist before you wrote the sentence. The FTC's focus on advertising accuracy is a reminder that public claims about accessibility are statements regulators and plaintiffs can read.

Fix: Write accessibility statements from your test results. Use precise language such as Partial Conformance where that's the truth, name the WCAG version and level, list known issues, and provide a working contact path for feedback. Have legal or compliance review any phrase that asserts full conformance.

Mistake 5: Skipping Contractual Accountability

Why It Happens: Accessibility clauses often get dropped to close deals quickly, or they're written so loosely that they bind no one. Teams assume a reputable-sounding vendor will stand behind its product.

Consequence: When the product underperforms, you have no remedy. You own the remediation cost, and the vendor owns nothing.

Fix: Build Accessible Procurement requirements into the contract. Specify the conformance target (for example, WCAG 2.1 or 2.2 Level AA), require the vendor to correct verified defects within a defined period, and reserve audit rights. Include a representation that marketing and sales claims about accessibility are accurate, and tie termination rights to material misstatements. Align the clauses with the standards that apply to you, whether that's ADA Title II under the DOJ Final Rule (2024), Section 508 of the Rehabilitation Act, or the European Accessibility Act. ADA Title II

Prevention Checklist

Use this as a pre-purchase and annual review gate for any accessibility product or service:

  • Define what evidence of conformance you accept, and write it into procurement policy under your Accessibility Governance program.
  • Obtain an Accessibility Conformance Report and verify its scope, WCAG version, and test methods.
  • Run independent Conformance Testing, including Screen Reader Testing, before signing and after deployment.
  • Ask vendors to disclose any compensation or incentives tied to reviews, testimonials, and case studies.
  • Validate AI-generated fixes with human testers; never treat automated output as final.
  • Draft your accessibility statement from your own test results, not vendor copy.
  • Include accuracy representations, remediation timelines, and audit rights in contracts.
  • Assign a named owner for vendor accessibility claims and review them on a set schedule.
  • Record your due diligence so you can show an auditor or regulator how you evaluated the claim.

The FTC's action makes one thing plain: the burden of verification sits with the buyer. Build the process that carries it.

Green background, the words "The Biggest AI Security Risk Isn’t the Model. It’s the Agent." A robot drawing. A button for "Get the Free Guide."

You Might Also Like