By platform · WordPress
What Breaks on WordPress, and What a Plugin Cannot Fix
WordPress core is in decent shape. Your site is core plus a theme somebody sold you, plus a builder, plus fourteen plugins, and that stack is where the barriers come from.
Last reviewed August 30, 2026
For the owner or agency running a WordPress site who wants to know what to install and what to fix.
Start with the good news, because it changes where you look. WordPress core is in reasonable shape. The accessibility team has worked on the admin, the editor and the default themes for years, and the current default theme carries the accessibility-ready tag.
Your site is not WordPress core, though. It is core plus a theme somebody sold, plus a page builder, plus a dozen plugins that arrived one at a time over three years. Every one of those layers outputs markup that nobody reviewed against anything. That is the actual shape of the problem, and it is why the answer to "which plugin fixes this" is almost always "none of them".
What breaks on WordPress
The failures we find most often on this platform, and the rule each one breaks.
Page builder markup
Elementor's own heading and button widgets output real elements, and its containers accept semantic tags, so the usual accusation is unfair to them. What goes wrong is everything around those widgets. Layout wrappers stay as divs, add-on packs ship their own markup, and an editor picks a heading level because it looks the right size on screen. The outline a screen reader hears is one nobody designed.
1.3.1 Info and Relationships
Theme color palettes
Themes are sold on how they look in the demo, and light gray body text on white photographs beautifully. It fails 4.5:1 the day it ships, on every page at once, because it arrived as a setting rather than a mistake. That cuts the other way too. One setting fixes it everywhere.
1.4.3 Contrast (Minimum)
Slider and carousel plugins
Most of them autoplay with no pause control, and a lot of them cannot be operated from the keyboard at all. That is our own audit experience rather than a published survey, and it is the most consistent finding we have on this platform.
2.2.2 Pause, Stop, Hide
What a designer did to your form plugin
Contact Form 7's default is better than fine. Every field is wrapped in a visible label, the name and email fields carry autocomplete tokens, and validation messages go into a polite live region while the visual error tip is hidden from screen readers so nothing gets read twice. Then a designer strips the labels for placeholders because the form looks cleaner without them, and the plugin that shipped accessible stops being accessible. Look at what was done to the default, not at the default.
3.3.2 Labels or Instructions
Media library alt text
WordPress gives every image an alt text field and enforces nothing at all. Most libraries we audit have the majority of it blank, and that is a long afternoon of work rather than a technical problem.
1.1.1 Non-text Content
Cookie and popup plugins
They load last, land on top of everything, and often cannot be dismissed with the keyboard. A banner that traps focus is worse than a banner that annoys people, because the visitor cannot get past it to reach anything underneath.
2.1.2 No Keyboard Trap
The plugin question, answered
Search for a WordPress accessibility plugin and you will get two kinds of result. Only one of them is honest about what it does.
Testing plugins tell you what is wrong and leave the fixing to you. Overlay plugins claim to do the fixing for you. The first kind is worth installing this afternoon. The second is the thing this whole site argues against, and on WordPress it is by far the more popular of the two.
Equalize Digital Accessibility Checker
A checker that runs inside the WordPress editor and reports on each post or page as you write it, with more than 40 automated checks in the free version.
- What it does
- It puts findings in front of the person creating the content, before publishing, which is the cheapest moment there is to fix anything. It now applies one-click fixes for some issues too, including skip links, focus outlines and missing form field labels.
- What it cannot
- It is an automated checker, so it covers the machine-checkable rules only. It can tell you alt text is missing and never that it is wrong. Its own description says it will not make your website fully accessible on its own, and that real accessibility takes automated scans plus manual review plus remediation. It also generates an accessibility statement, and a generated statement is a conformance claim published under your name, so read every word before you leave it up.
WP Accessibility
A long-standing free plugin that patches specific known theme problems rather than pretending to solve the category.
- What it does
- It adds a skip link, prompts for alt text, removes duplicated title attributes, restores keyboard focus outlines and labels the standard WordPress form fields. It also searches your media library for images with no alt text, which is exactly the tool the second step below asks you for.
- What it cannot
- It patches symptoms in the theme, and it says so itself. Its own description states that it is not intended to make your site compatible with any accessibility guidelines and cannot correct every problem by a long shot. It will not touch your page builder's output or your content.
Editor and block plugins
Block libraries and editor extensions that output real headings, buttons and lists by default.
- What it does
- Choosing components that produce semantic markup prevents the problem rather than patching it, and prevention is the only approach that survives your next fifty pages.
- What it cannot
- It will not repair the pages you have already built, and swapping block libraries on a live site is a project of its own.
Elementor's Web Accessibility plugin (once One Click Accessibility)
The most-installed accessibility plugin in the WordPress directory, past 500,000 active installs, bundling three separate things. A checker, a visitor-facing toolbar, and an accessibility statement generator.
- What it does
- The checker half is a genuine editor-side check in the same family as the two above it, and it covers a long list of issues while you are still building the page.
- What it cannot
- The toolbar half is an overlay, and the statement generator publishes a conformance claim in your name before anybody has tested anything. Elementor's own listing says the plugin is not intended to completely make your website legally compliant and recommends working with qualified accessibility professionals. Its rating splits almost evenly between five stars and one star, which tells you people are having very different experiences with it.
Overlay widgets (accessiBe, UserWay, AudioEye and the rest)
A script you paste into your template that draws a toolbar for visitors and claims to repair your pages automatically as they load.
- What it does
- The toolbar half is real. Bigger text, higher contrast, adjusted spacing and a reading guide are preferences some visitors use, and the field's own reference document on overlays says a non-trivial array of accessibility problems can genuinely be repaired this way.
- What it cannot
- It does not change the markup your server sends, and the categories it handles worst are the ones that decide whether a site works at all. Text alternatives, form labels and error handling, and keyboard access. More than 5,000 US digital accessibility lawsuits were filed in 2025, and the firm that compiles that dataset reads the filings the same way every year, which is that widgets do not materially reduce legal risk. Our overlays page has the documented record.
What to actually do
- Run the free 10-page scan first, so you are looking at the whole site rather than the one page you happened to have open.
- Search your media library for images with no alt text, using WP Accessibility's media search, and start with the images on your busiest pages.
- Check your theme's colors in the contrast checker. Body text, link text and button labels first, because those three appear on every page you have.
- Tab through the site with your mouse pushed out of reach. Popups, menus and sliders are where it breaks, and you will know inside a minute.
- Submit one of your own forms with a deliberate mistake in it. Look for a visible label on every field, a message that says what to fix, and focus landing on the problem rather than back at the top.
- Run the heading checker on your main templates to see the outline a screen reader user would be navigating by.
On themes and templates
If you are choosing a theme, that is the biggest single decision on this page, because the theme's markup is what you will be living with on every page for years. Open the theme's own demo, put the mouse down, and try to use it. Themes in the WordPress.org directory tagged accessibility-ready have passed a review against a published set of requirements, which is a genuinely useful filter, and WordPress is careful to say what the tag does not mean. Accessibility-ready does not mean the theme meets WCAG at Level AA. It means the theme clears the minimum the theme review team set. No theme can honestly be sold as WCAG conformant anyway, because WCAG measures content and a theme is not content until your words go into it.
One honest limit
No plugin makes a WordPress site accessible. The barriers live in your theme's markup, your builder's output and your own content, and those are the three places a plugin cannot reach into and rewrite. What a good plugin does is tell you where they are, in front of the person who put them there. That is worth having and it is not the same thing.
Keep reading
Other platforms
WordPress
We test all 55 WCAG 2.2 A and AA rules on your WordPress site, with an expert review and a real blind screen-reader user on your key journeys. Every finding screenshotted and mapped to its fix. $499, report in 5 business days.