Search the plugin directory for “accessibility” and you get pages of results with very different promises. One says it scans your posts. Another adds a skip link. A third puts a little wheelchair icon in the corner and says your site is now compliant. They are all called a WordPress accessibility plugin, but they do completely different jobs.
This post sorts them into kinds, explains what each kind can and cannot do, and shows how to judge one before it goes on a live site. We name plugins only by type here on purpose: features and ownership change, and the questions below will still apply next year.
Three kinds of WordPress accessibility plugin
Almost every plugin in this space falls into one of three groups. Knowing which group you are looking at tells you most of what you need to know.
| Kind | What it does | Good for | Where it stops |
|---|---|---|---|
| Checker | Scans posts and pages and lists likely problems in the dashboard | Finding missing alt text, empty links, skipped headings, low contrast as you write | Cannot judge meaning, keyboard behavior or screen reader experience |
| Targeted helper | Changes specific markup or styles, such as adding a skip link or restoring focus outlines | Patching known gaps in a theme you cannot easily edit | Fixes only what it was written for; can conflict with the theme |
| Overlay or toolbar | Adds a widget with font, contrast and other controls, often with automatic “repairs” | Very little that browsers and devices do not already offer | Does not fix the underlying code; widely criticized by disabled users |
Checker plugins: a second pair of eyes for editors
A checker reads the HTML of each post and tests it against built-in rules. When an editor saves a post, it might warn that an image has no alt text, a link says only “here,” or the page jumps from an H2 straight to an H4. Some also scan the whole site on a schedule and show a list of issues by page.
That earns its place. Most content problems are small and repetitive, and catching them while the editor is still on the page is far easier than finding them in an audit months later.
What a checker cannot do is understand what it is looking at. It sees that alt text exists, not whether “photo” describes a chart of your opening hours. It cannot press Tab through a dropdown menu, or hear that a screen reader announces “button” three times with no name. And it usually scans post content better than the header, footer and plugin output around it. We go into how to read those warnings, and which ones are often false alarms, in our post on using an in-dashboard accessibility checker.
Things to look for in a checker
- It explains each warning in plain words and links it to a WCAG success criterion.
- It lets you mark an item as reviewed, so real issues do not get lost among false positives.
- It can check pages built by your page builder, not only the classic content area.
- It does not slow the editor down noticeably on long posts.
Targeted helpers: small fixes for known gaps
The second kind changes the front end in narrow, predictable ways. Common examples include adding a skip-to-content link, putting back a visible focus outline the theme removed, removing redundant title attributes, adding underlines to links in body text, or adding labels to the default search form.
These can be a sensible stopgap when the theme is otherwise fine and you cannot edit it directly. A focus outline restored by a small plugin is better than no focus outline.
The risk is that you stack patches on top of each other without knowing what each changes. Two plugins both injecting a skip link gives you two skip links. A helper that forces underlines may fight your page builder’s button styles. Over time the site becomes harder to reason about, and an update to either the theme or the helper can undo the fix silently.
Our advice: use a helper for a gap you have identified, write down what it fixes, and treat it as temporary if the same fix can be made properly in a child theme later.
Overlays and toolbars: why we do not recommend them
The third kind is the one most heavily marketed. An overlay adds a script and usually a floating button. Visitors can open a panel to change font size, contrast or spacing, and the vendor often claims the script detects and repairs problems automatically.
The trouble is that the problems that stop people are in your site’s structure: a menu that cannot be opened by keyboard, a form field with no label, a checkout that loses focus. A script running after the page loads cannot reliably understand and rebuild those. Meanwhile, many disabled people already use their own settings, screen readers and browser zoom, and some report that overlays interfere with those tools.
Disability advocates and many practitioners have criticized overlays publicly, sites using them have still been sued, and in 2025 the FTC took action against one overlay vendor over misleading claims. We cover the background in our explainer on how accessibility overlays work and what they miss. If you already have one installed, our accessibility overlay alternative page describes how we replace it with real fixes.
What no plugin can do for you
Even the best plugin setup leaves a list of work that needs a person. This is not a flaw in any particular plugin. It is the nature of the problems:
- Deciding what an image means. Only someone who knows why the image is there can write useful alt text, or decide it is decorative.
- Testing with a keyboard. Someone has to press Tab, Enter, Space and Escape through menus, popups, sliders and forms.
- Listening with a screen reader. NVDA on Windows and VoiceOver on Mac or iPhone show whether controls have sensible names and whether updates are announced.
- Checking zoom and reflow. Zooming to 400 percent shows whether content stays readable without sideways scrolling.
- Fixing plugin output you cannot configure. A booking calendar built without keyboard support needs code changes or a replacement, not another plugin.
- Writing clearly. Plain instructions, useful link text and honest error messages are editorial work.
So the realistic role of plugins is support: a checker to catch content slips, perhaps one helper to cover a theme gap. The main work is still fixing the theme, the plugins people interact with, and the content itself, in roughly the order our guide on making a WordPress site accessible sets out.
How to judge any accessibility plugin before installing it
Whatever kind of WordPress accessibility plugin you are considering, run through these checks first. None of them needs technical skill, and they save a lot of cleanup later.
- Read the claim carefully. A plugin that says it helps you find issues is describing a checker. A plugin that promises legal compliance is making a claim no plugin can back up.
- Look at what it changes on the front end. Does it add a script, a floating button, or new markup to every page? Know before it goes live.
- Check maintenance. When was it last updated? Does the developer answer support questions? An abandoned plugin is a security and compatibility risk as well.
- Install on a staging copy first. Test the pages your visitors actually use with the keyboard before and after.
- Write down why it is there. A one-line note in your plugin list (“restores focus outline removed by theme”) stops the next person from deleting it blindly or adding a duplicate.
If your plugin list has grown over the years, our routine for auditing the plugins on a WordPress site is a good way to find which ones still earn their place.
So which are the best accessibility plugins for WordPress?
People ask for a list of the best accessibility plugins for WordPress, and the honest answer is that “best” depends on the job. For editors, a well-maintained checker that explains its warnings is worth having. For a theme with one or two specific gaps, a small helper can bridge the time until a proper fix. For making the site work for disabled visitors, no plugin is a substitute for testing and fixing the site itself.
A useful test: if a plugin removed tomorrow would leave your site exactly as accessible as before, it was a reporting tool. If removing it would bring back barriers, those barriers are still in your code and are worth fixing at the source when you can.
Frequently asked questions
Will an accessibility plugin make my WordPress site ADA compliant?
No plugin can do that. The ADA does not certify plugins, and the barriers that stop people usually sit in the theme, forms and content. A checker helps you find issues and a helper can patch a few, but real progress comes from fixing the site, testing it by keyboard and screen reader, and recording what was done. A lawyer handles any legal questions.
Should I install more than one accessibility plugin?
Usually one checker is plenty, plus at most a small helper for a specific known gap. Several plugins that change the front end can conflict, for example by adding two skip links or overriding each other’s focus styles. Keep a short note of what each one does so nobody stacks duplicates later.
Are free accessibility plugins good enough?
Price is not the dividing line. A free, well-maintained checker that explains its warnings can be as useful as a paid one, and a paid overlay still cannot fix your code. Judge any plugin by what kind it is, how recently it was updated, and what it changes on the front end.
Can a plugin fix my page builder’s accessibility problems?
Some helpers target specific page builder gaps, such as missing labels on toggles or focus styles on buttons, and can help. Many builder problems come from how pages were assembled, such as headings chosen by size or icon-only buttons, so they need changes to the pages themselves. Test the result rather than trusting the description.
If you would like someone to review your plugin list and fix the problems plugins cannot reach, our WordPress accessibility service covers the theme, plugins and content together. For the wider context, start with our ADA website accessibility help.
Next in this series: Accessibility Ready WordPress Themes: What the Tag Means
