Updated October 14, 2026
Yes, accessiBe works with WordPress. You install the “Web Accessibility by accessiBe” plugin from the WordPress plugin directory, connect your accessiBe account, and its accessibility widget appears on your site.
What it can’t do on its own is make a website accessible or compliant. In April 2025, the U.S. Federal Trade Commission finalized an order that bars accessiBe from claiming its automated product makes any website WCAG-compliant without evidence. We still use accessiBe with some clients, as one layer of a wider accessibility plan. This post explains what it does, what it doesn’t, and what else a WordPress site needs.
Key Takeaways
- accessiBe installs on WordPress through an official plugin and adds an accessibility widget to every page.
- An overlay gives visitors display options, but it doesn’t fix your site’s code, content or documents.
- No automated tool can guarantee WCAG, AODA or ADA compliance. The FTC’s 2025 order against accessiBe makes this point directly.
- In Ontario, private and non-profit organizations with 50 or more employees must make their public websites meet WCAG 2.0 Level AA.
- Real accessibility comes from an audit, code fixes, accessible content and regular checks. An overlay can sit on top of that work, not replace it.
How accessiBe Works on WordPress
accessiBe’s main product is accessWidget, a script that loads on each page of your site. On WordPress, you add it with the official plugin, or by placing the script in your theme or in Google Tag Manager.
Visitors see an accessibility button. Opening it lets them adjust things like text size, contrast, spacing and cursor size, or choose a preset profile for a common need. accessiBe says the widget also makes automated adjustments in the background for screen reader and keyboard users. How well those adjustments work depends on how your site is built.
On our own site, accessiBe loads after the rest of the page has finished loading. That keeps it from slowing down what visitors see first.
What an Accessibility Overlay Can’t Do
An overlay works on top of a page as the browser loads it. Many accessibility problems sit deeper, in the way the site is built or written. An overlay can’t:
- Fix code at the source: missing form labels, buttons built from plain page elements, menus that trap keyboard users, or focus that jumps around the page.
- Write meaningful alt text: a tool can describe an image, but only you know why the image is there.
- Caption your videos or describe what happens in them.
- Make PDFs and other documents accessible.
- Keep your content clear: plain language, logical headings, and link text that makes sense on its own.
- Prove compliance: that depends on how your whole site meets the standard, tested by people.
Some people who use screen readers also turn overlays off, because they prefer their own assistive technology settings. Your site needs to work well for them without the widget.
What the FTC Order Means for Your Business
In January 2025, the FTC alleged that accessiBe’s claims that accessWidget could make any website WCAG-compliant were false or unsupported. It also said accessiBe presented reviews and articles about its product as independent when they weren’t. The final order, approved in April 2025, requires a $1 million payment and bars those claims unless accessiBe has evidence to back them.
The lesson for business owners is simple. Be careful with any plugin, product or agency that promises instant compliance. Accessibility is ongoing work, and the responsibility stays with the website owner. An earlier version of this post repeated compliance claims like these, and we’ve corrected it.
Accessibility Rules for Ontario and Canadian Websites
AODA (Ontario)
Since January 1, 2021, under the Integrated Accessibility Standards Regulation, Ontario private-sector and non-profit organizations with 50 or more employees must make their public websites, and web content posted after January 1, 2012, meet WCAG 2.0 Level AA. Live captions and pre-recorded audio descriptions are exempt. These organizations also file accessibility compliance reports with the province.
Accessible Canada Act (Federally Regulated Businesses)
The federal Accessible Canada Act covers the Government of Canada and federally regulated industries such as banking, telecommunications, interprovincial transportation and broadcasting. Most other businesses fall under provincial laws, like the AODA in Ontario.
WCAG 2.2: The Current Standard
Ontario’s rules name WCAG 2.0, but the current version is WCAG 2.2. Building to WCAG 2.2 Level AA covers the older versions and prepares your site for future updates.
This is general information, not legal advice. Check the regulation or ask a lawyer about your own situation.
How We Approach WordPress Accessibility
We treat accessibility as part of building a good website, alongside speed and SEO. Our process has five steps:
- Audit: automated scans plus manual testing with a keyboard and a screen reader, against WCAG 2.2 Level AA.
- Fix the code: theme templates, forms, menus, colour contrast and focus states, directly in WordPress.
- Fix the content: headings, alt text, link text, captions and documents, with simple guidelines your team can follow.
- Add accessiBe if it helps your visitors: as an optional layer of display options, never as a compliance claim.
- Check regularly: new pages, plugins and updates can bring new issues, so we re-test after major changes.
Does Accessibility Help SEO?
Accessibility and SEO overlap. Clear headings, descriptive link text, alt text, readable layouts and fast pages help people who use assistive technology. They also help search engines and AI tools understand your content.
Google doesn’t use an accessibility score as a ranking factor, but it does reward pages that are easy to use and understand. Our SEO services in Toronto cover accessibility, speed and structure together.
Frequently Asked Questions
Does accessiBe work with WordPress?
Yes. Install the “Web Accessibility by accessiBe” plugin from the WordPress plugin directory, sign in to your accessiBe account, and the widget appears on your site. You can also add its script through your theme or Google Tag Manager.
Will accessiBe make my website AODA or WCAG compliant?
No tool can guarantee that on its own. Compliance depends on your site’s code, content and documents, tested against the standard. An overlay can help some visitors, but you still need an audit and fixes.
Does an accessibility widget slow down my website?
It adds a script to every page. Loading it after the main content, as we do on our own site, keeps the impact on page speed low.
What WCAG level does Ontario require?
WCAG 2.0 Level AA for the public websites of Ontario organizations with 50 or more employees, with exceptions for live captions and pre-recorded audio descriptions.
Want help making your WordPress site accessible? Contact us and we’ll take a look at your site.
