Insights
Accessibility Widgets for Nonprofits After the AccessiBe Fine
If you run a nonprofit website, you have probably encountered the pitch. Paste one snippet, the email says, and your site becomes accessible. You are protected from lawsuits. Your visitors are served. Problem solved.
That pitch is now a federal trade matter.
In April 2025, the FTC approved a final consent order requiring accessiBe, the largest accessibility overlay vendor, to pay $1 million for deceptive marketing claims. The complaint alleged that accessWidget, accessiBe’s AI plug-in, did not in fact make customer websites WCAG-compliant despite the company’s claims. The order also covered accessiBe’s practice of deceptively formatting paid third-party reviews to appear as independent endorsements.
The accessibility community had been documenting the category’s overclaiming for years. The Overlay Fact Sheet, signed by over 800 digital accessibility professionals, lays out the technical and ethical problems with automated overlays in detail.
This piece is for nonprofit website managers trying to figure out what to do next. It is also about what to ask before installing any third-party accessibility utility, including EasyNav.
What the FTC’s fine actually addresses
The fine targets two specific failures.
The first is automated compliance. A script that loads after your page cannot reliably fix fundamental HTML problems. It cannot make a form keyboard-accessible if the underlying code lacks focus states. It cannot accurately describe a complex image if no human ever wrote alt text. And it can actively interfere with the assistive technology that blind and motor-impaired users have spent years configuring.
The second is the marketing pattern. AccessiBe was not fined for building an imperfect product. The company was fined for selling a product whose claims it could not support, and for backing those claims with paid endorsements presented as independent. That is a buyer-protection issue, and the FTC treated it the same way it treats any other deceptive marketing case.
Both failures matter for nonprofits. If your website cannot serve a screen reader user, no widget makes it so. If a vendor tells you otherwise, the FTC has now established that this kind of claim can be treated as deceptive marketing.
The second population overlays are actually for
There is one population where reading comfort tools genuinely help: people who do not have specialized assistive technology and are not going to install any.
The older donor whose vision has shifted just enough that 14-pixel body copy is hard to read. The volunteer checking your event hours on a phone in bright sun. The dyslexic adult who never got a diagnosis. The patient at home recovering from a migraine reading your eligibility instructions. These visitors do not file complaints. They close the tab.
For a deeper case on this audience and why a hospitality overlay is structurally different from a compliance overlay, see The Foundation and the Overlay and We Read the Overlay Fact Sheet.
Five questions to ask before installing any accessibility widget
Whether you are looking at AccessiBe, UserWay, EqualWeb, EasyNav, or anything else, these are the questions worth asking before you paste a script tag into your site.
1. Does the widget modify ARIA on your existing elements? Overlays that inject ARIA roles or labels can disrupt the carefully tuned workflows of screen reader users who could navigate your site before the widget arrived. The answer should be no.
2. Does it attach document-level keyboard listeners? If a widget intercepts keydown events globally, it can trap keyboard focus and override native browser or assistive-technology shortcuts. The answer should be either no, or scoped to a single key (such as Escape, only when the widget’s own panel is open).
3. Does it claim automated WCAG compliance or legal protection? After the FTC ruling, treat any vendor making this claim with extreme skepticism. A widget cannot substitute for accessible markup, and any vendor selling it that way is now in a different regulatory environment than they were a year ago.
4. Does it track visitor behavior or drop tracking cookies? Nonprofits often serve people whose web activity is genuinely sensitive: medical patients, legal aid clients, domestic violence survivors. Verify that the widget does not log per-visitor behavior, store visitor identifiers, or share data with third parties.
5. Does its layout live inside a Shadow DOM? This browser-enforced boundary is the only reliable way to ensure a third-party widget’s CSS cannot accidentally leak into your site or conflict with your existing styles.
How EasyNav answers these questions
EasyNav is a reading comfort widget. It gives visitors a small set of controls (text size, contrast, line spacing, dyslexia-friendly font, reading guide) and saves their preferences in their own browser.
ARIA on existing elements: untouched. EasyNav adds its own elements with their own ARIA roles. It does not modify yours.
Keyboard listeners on the host: exactly one, scoped to the Escape key, and only when the EasyNav panel is open, to dismiss it.
Compliance claims: none. EasyNav does not claim to make your site WCAG-compliant. If your underlying code has accessibility failures, EasyNav does not mask them.
Visitor tracking: none. No cookies, no tracking identifiers, no per-visitor logs. If you enable analytics in your dashboard, EasyNav counts anonymous panel opens, never which controls were used or by whom. Most users leave analytics off.
Shadow DOM: yes, with mode: 'open'. The widget’s UI is encapsulated by the browser. Feature effects like high contrast are applied via visitor-scoped CSS that is removed when the visitor turns the feature off.
For the full technical write-up, see We Read the Overlay Fact Sheet. For a complete privacy walkthrough including network behavior, see What Data Does EasyNav Collect.
We offer nonprofit pricing. If standard nonprofit pricing is still out of reach for your organization, reach out at hello@easynav.io.
The honest recommendation
If your nonprofit website has fundamental accessibility failures (missing alt text, broken keyboard navigation, unlabeled form fields), the answer is to fix those at the source. No widget substitutes for that work. The FTC ruling makes it clearer than ever that you cannot buy your way out of doing it.
If your site is fundamentally sound and you want to give your everyday visitors a way to adjust how they read it, a scoped reading comfort tool is a reasonable addition. Just make sure whichever one you choose stays out of the way of the people who already have their own.