WordPress Accessibility Plugin: What Actually Helps?
Information about the article

Author: Dmitry Dugarev
Search for a WordPress accessibility plugin and you get long lists. They put widgets, scanners and form plugins side by side. But these tools do very different jobs. I audit WordPress websites by hand. In this article, I sort the plugins by what they actually do.
This article is for website owners and agencies. You will learn which plugin helps with what, what it costs and where its limits are.
- No plugin makes your WordPress website accessible on its own. Even the vendors say so [1], [2], [3]. An overlay does not necessarily get you there either [4].
- Free checkers such as Accessibility Checker or Editoria11y help your editors. WP Accessibility helps with older themes [1], [3], [5].
- Checkers catch some errors while you edit. The rest needs a human reviewer [6].
- You can fix most barriers only in the theme itself. Even the author of WP Accessibility says so [1].
What a WordPress accessibility plugin can do
In WordPress, accessibility barriers come from three places:
- Content: alt text, headings, link text.
- Theme or page builder: menus, focus, colors, templates.
- Plugins: forms, cookie banners, sliders.
A plugin usually works in only one of these places. But WCAG conformance always applies to the whole page [7]. An error in the cookie banner counts just as much as an error in the theme.
Joe Dolson develops the WP Accessibility plugin. He is frank about it: most problems can only be fixed by changing the theme directly [1].
So I sort accessibility plugins into five groups:
| Type | What they do | What they cannot do | Examples |
|---|---|---|---|
| Overlays and widgets | Toolbar for font size, contrast, animation | Fix errors in the code | Web Accessibility (Ally), UserWay, accessiBe, OneTap |
| Checkers | Flag errors while you edit | Test all 55 success criteria | Accessibility Checker, Editoria11y, WP ADA Compliance Check |
| Fix plugins | Repair known weak spots in WordPress | Make up for a poor theme | WP Accessibility |
| Building blocks | Forms and cookie banners with accessibility promises | Check your settings and colors | Gravity Forms, Borlabs Cookie |
| Markup tools | Change the HTML of specific Gutenberg blocks | Find errors on their own | Semanticality™ |
Overlays and widgets: no one-click accessibility
An overlay puts a toolbar on top of your website. Visitors use it to change font size, contrast or animations, for example. The errors in your code stay where they are.
In March 2025, Germany's federal and state monitoring bodies for public-sector accessibility published a joint assessment of overlays [4]. The core message: an overlay does not necessarily make an inaccessible website accessible. Overlays can even make things worse for people who use assistive technology [4].
The assessment is aimed at public bodies. The market surveillance authorities that enforce the BFSG (Barrierefreiheitsstärkungsgesetz, Germany's implementation of the European Accessibility Act) have not issued a statement of their own. The standard is the same, though: your website itself must meet the requirements [8].
Well-known examples from the WordPress plugin directory:
- Web Accessibility (formerly Ally) by Elementor: Elementor describes it as the successor to One Click Accessibility [9]. The plugin has more than 500,000 active installations. It combines a widget with a checker and an accessibility statement generator. The basic version is free. AI fixes cost extra [2].
- Accessibility by UserWay: The plugin embeds the UserWay widget. Installing it is free. After that, you get your login details by email [10]. Paid plans start at $490 a year [11].
- Web Accessibility by accessiBe: Installing it is free, but you need an account to use the features. Plans start at 1 million. The reason was unsupported claims that the tool could make any website WCAG-compliant [12].
- WP Accessibility Helper: The plugin shows a toolbar for font size, contrast and grayscale. It has more than 10,000 active installations and comes in a free and a Pro version [13].
- Accessibility Widget by OneTap: OneTap is also a floating toolbar with font size, contrast and reading aids. The plugin has more than 60,000 active installations. Some features are only in the Pro version [14].
Elementor is honest about this. According to its own description, the plugin does not replace a thorough audit and is not meant to make your website fully compliant [2]. The Ally checker can still be useful. Elementor says it detects more than 180 common violations based on WCAG 2.1 AA [2].
A widget can help individual visitors, for example with larger text. But it does not fix any errors in your code. If your menu does not work with a keyboard, a widget will not change that. I explain in detail why overlays are not enough for the BFSG in my article on overlays and BFSG compliance.
Accessibility checkers: find errors while you edit
Checkers, also called scanners, test your pages automatically and flag errors right in the editor. You spot a missing alt text before the page goes live. These plugins mainly help your editors.
- Accessibility Checker by Equalize Digital: The plugin checks posts and pages in both the block editor and the classic editor. It runs more than 40 automated checks based on WCAG 2.2. The basic version is free. A Pro version costs extra [3].
- Editoria11y: The plugin shows hints to logged-in editors as they write. It checks content such as alt text, link text and headings. It deliberately leaves out errors in the theme and in plugins. It is free, with an optional paid supporter tier [5].
- WP ADA Compliance Check Basic: The plugin checks against WCAG 2.1, WCAG 2.2 or Section 508, whichever you choose. The free version scans up to 15 posts or pages per run with 52 checks. It does not find errors in theme files [15].
Where checkers reach their limits
The W3C is clear: no checker can test every aspect of accessibility automatically. Human judgment is needed [6]. Checkers also sometimes give wrong or misleading results [6].
Here is an example. A checker sees whether an image has alt text. It cannot see whether that text describes the image in a meaningful way. But that is exactly what WCAG 1.1.1 requires [16].
Our free BFSG check has the same limit. It checks 20 of the 55 WCAG 2.2 A and AA success criteria automatically, at least partly. The other 35 criteria can only be tested manually. For these, a person has to judge meaning, order and operability.
My advice: use a checker as a tool for your editorial team. It is no proof that your website is accessible.
Free WordPress accessibility plugins
Many good tools cost nothing. You can use these plugins for free:
- WP Accessibility: completely free [1].
- Editoria11y: free, with an optional supporter tier [5].
- Accessibility Checker: basic version free, Pro costs extra [3].
- WP ADA Compliance Check Basic: free, but limited to 15 pages per scan [15].
- Contact Form 7: free [17].
Free here means free to install. You still have to do the work on your theme and templates.
Fix plugins: repair known WordPress issues
Some plugins fix typical weak spots in WordPress and in older themes. One example is WP Accessibility by Joe Dolson. It is free and open source [1].
Among other things, the plugin can [1]:
- Add skip links.
- Set the language attribute of the page.
- Force a visible keyboard focus.
- Add labels to the WordPress form fields.
- Remove problematic tabindex values and redundant title attributes.
But the author also writes: the plugin is not meant to make your website conform to accessibility guidelines. It does not come close to fixing every problem [1].
I see WP Accessibility as a band-aid for an older theme. It is no substitute for fixing the errors in your templates. My WordPress accessibility guide shows how to tackle your theme and page builder.
Some themes in the WordPress theme directory carry the "accessibility-ready" tag. The Theme Team itself says: the tag does not mean that a theme meets WCAG at level AA. It only meets the team's minimum requirements [18].
Accessible building blocks: forms, cookie banners, sliders
Forms, cookie banners and sliders almost always come from plugins. Their code ends up directly on your page. So choose these building blocks with extra care.
Forms: Gravity Forms and Contact Form 7
Gravity Forms is a paid plugin. The basic license for one website costs $59 a year [19]. The vendor aims for WCAG 2.1 AA [20]. Since version 3.0, accessibility settings are enabled in every new form, and submit buttons are real <button> elements [21].
Gravity Forms is also clear about the limits. Your theme affects the forms, and every field needs a visible label. According to the vendor, the website owner is always responsible [20].
Contact Form 7 is free and has more than 10 million active installations [17]. Its default template wraps every field in a <label> [22]. But you can change the template freely. In my audits, I often see forms where placeholders replace the labels. Joe Dolson offers a free fix for this: the plugin "Contact Form 7: Accessible Defaults" with accessible templates [23]. I show how to test and fix Contact Form 7 in my article on Contact Form 7.
Whatever form plugin you use, test the finished form with our checklist for accessible forms.
Cookie banners: promises and reality
In September 2025, Equalize Digital tested six cookie plugins, including Complianz, CookieYes and Real Cookie Banner. The team also tested by hand with a keyboard and a screen reader [24].
The result: no banner was truly WCAG-compliant without extra work. Many had critical errors, even though they promise compliance [24]. Typical issues were missing focus management, a div instead of a real button, and problems at 400% zoom [24].
Borlabs Cookie was not part of this test. It is a paid plugin, starting at €49 plus VAT [25]. Borlabs states that it meets the requirements of WCAG 2.1 AA [25]. That is the vendor's own claim, not an independent test.
Test every cookie banner yourself with a keyboard. It appears before anything else on the page. If you cannot get into it or back out of it, it blocks the whole page [26], [27].
Sliders and carousels
I do not name a specific slider plugin. The quality depends heavily on how you set up the slider. Pay special attention to autoplay. If a slider starts on its own and runs for more than five seconds, users must be able to pause, stop or hide it [28].
Test your slider with our checklist for accessible carousels.
Semanticality™: fix Gutenberg markup without touching the theme
To be upfront: Semanticality™ is our own plugin. I mention it here because it does not fit into any of the other groups.
Semanticality™ changes the HTML output of Gutenberg blocks at render time. You set up rules for this in the block editor. For example, you swap a <div> for a <section> or add ARIA attributes. You do not touch the code of your theme or plugins.
<!-- Before: a title without semantics -->
<div class="kt-accordion-title">FAQ</div>
<!-- After: a real heading -->
<h2 id="faq-title" class="kt-accordion-title">FAQ</h2>
Semanticality™ does not find errors on its own. So you first need an audit that tells you which rules you need. The plugin only works with the Gutenberg editor, not with Elementor or Divi. For these page builders, there are separate guides: Elementor accessibility and Divi accessibility. You need basic knowledge of HTML, CSS and WCAG. Test new rules on a staging copy first. A license starts at €119 a year plus VAT.
You will find all details in the Semanticality™ documentation and on the Semanticality™ product page.
How to choose a WordPress accessibility plugin
Before you install a plugin, ask yourself five questions:
- What does the vendor promise? Reputable vendors state their limits. No checker can determine accessibility on its own [6]. If a plugin promises "100% compliance", look at it very closely.
- Where does the plugin work? In the content, in the theme or only in a toolbar on top of the page?
- Is its own output accessible? A form or cookie plugin adds its own code to your page. You have to test that code.
- Does it need an external service? UserWay and accessiBe, for example, require an account with the vendor [10], [29]. Check the data protection (GDPR) implications first.
- Is it actively maintained? On wordpress.org you can see the last update and the WordPress version it was tested with.
Test a plugin in 15 minutes
You can run this quick test on any plugin. All you need is a keyboard, a browser and a screen reader.
Use only the keyboard
Put the mouse away. Use Tab, Shift+Tab, Enter, Space and Esc. Every function must be reachable with the keyboard [26]. You must never get stuck [27].
Watch the focus
You must always see where the keyboard focus is [30]. Focus that disappears completely behind a banner is also an error [31].
Zoom to 400%
Set the browser zoom to 400%. The content must reflow without making you scroll in two directions [32]. The W3C treats 400% zoom at a width of 1280 CSS pixels as equal to a width of 320 CSS pixels [32].
Listen with a screen reader
Start NVDA on Windows or VoiceOver on a Mac. The screen reader must announce the name and role of every control, for example "Send, button" [33].
Measure contrast
Normal text needs a contrast ratio of at least 4.5:1 [34]. You can check this quickly with our contrast checker.
Is there a BFSG plugin for WordPress?
No. The BFSG has applied since June 28, 2025 [8]. If your website falls under the BFSG, your service must meet the accessibility requirements (§ 14 para. 1 no. 1 BFSG). You must also provide the information listed in Annex 3 (§ 14 para. 1 no. 2 BFSG) [8]. These duties apply to your website as a whole, not to a plugin.
Some plugins generate an accessibility statement, for example Elementor's Ally plugin and Accessibility Checker [2], [3]. That helps with the format. But the content has to be true. A statement without a real audit describes a level of accessibility that nobody knows. You can start from our accessibility statement template.
To find out whether the BFSG applies to you at all, use our EAA check. I explain what the law requires in my overview of the EAA and BFSG.
What no plugin can replace
There are two things no plugin can do for you:
- A manual review. A manual audit tests all 55 WCAG 2.2 A and AA success criteria with a keyboard, a screen reader and zoom. For every barrier, you get its location and a solution. Our sample audit report shows what such a report looks like.
- Fixes in the templates. The errors have to be fixed where they come from. That works in your existing theme or page builder, without a relaunch. If you want, I can do this for you as part of remediation.
If you first want to know where you stand, book a free initial call with me. It takes 15 minutes.
Frequently asked questions (FAQ)
Which WordPress plugin makes my website accessible?
None on its own. Even the vendors write that their plugin does not deliver full accessibility [1], [3]. Plugins help with parts of the job. You have to fix most errors in the theme [1].
Is there a free WordPress accessibility plugin?
Yes. WP Accessibility is completely free [1]. Editoria11y and Accessibility Checker have free basic versions [3], [5]. But they only find or fix some of the errors.
Is an accessibility widget enough for BFSG compliance?
No. An overlay widget does not necessarily make a website accessible [4]. I explain the reasons in detail in my article on overlays and the BFSG.
Can an accessibility checker find all errors?
No. No checker can test every aspect automatically. Human judgment is needed [6]. A checker detects missing alt text, for example, but not wrong alt text.
Disclaimer
The content of this article has been researched to the best of my knowledge and is for general information only. It is not legal advice and cannot replace individual advice from a lawyer who looks at your specific situation.
Details on plugins, prices and features are correct as of September 26, 2026. Vendors can change them at any time. I cannot guarantee that the information is accurate, complete or up to date. Any action you take based on the information provided here is at your own risk.