You can pick an accessible theme, write careful content, and still ship a site that fails keyboard users. The reason is often a plugin. Sliders, popups, form builders, cookie banners, and page builders all inject their own markup, scripts, and styles, and you rarely get to review that code before it goes live. This post covers the accessibility problems that show up most often in WordPress plugins and what you can do about each one.
Why Plugins Are a Blind Spot
Most site owners test their theme and their content. Plugin output tends to get a quick visual check at best. But a plugin can add a modal dialog, a carousel, or a form to nearly any page, and each of those is a component with complex keyboard and screen reader requirements. A plugin that looks polished can still be unusable without a mouse.
Responsibility also stays with you. If a plugin on your site creates a barrier, your visitors experience it as your site’s barrier, and a legal complaint will name your site, not the plugin author.
The Most Common Plugin Problems
Modals and popups that trap or lose focus
A well-built dialog moves focus inside when it opens, keeps Tab cycling within it, closes with the Escape key, and returns focus to the element that opened it. Many popup and lightbox plugins do none of this. Keyboard users end up tabbing through content hidden behind the overlay, or they can’t dismiss the popup at all.
Sliders and carousels with no controls
Auto-rotating content that can’t be paused fails WCAG 2.2.2 (Pause, Stop, Hide). Navigation arrows built from empty links or divs with click handlers give screen reader users nothing to announce. Look for a visible pause button, real button elements, and labels such as “Next slide.”
Form builders with missing labels and vague errors
Placeholder text is not a label. Some form plugins render fields with only a placeholder, or show errors in red text without associating them with the field. Check that every input has a programmatically associated label and that error messages are announced and say what went wrong.
Cookie banners and notices
Consent banners appear on every page, so one flaw affects the whole site. Common issues include buttons that can’t be reached by keyboard, banners that cover focused elements, and low-contrast text on branded backgrounds.
Icon-only buttons and links
Social share icons, search toggles, and menu buttons are often built from icon fonts or SVGs with no accessible name. A screen reader may announce only “link” or “button,” which tells the user nothing.
Overused or incorrect ARIA
Some plugins add ARIA roles and attributes that contradict the native element or never update as state changes, such as an accordion that always reports “collapsed.” Incorrect ARIA can be worse than none, because it actively misleads assistive technology.
How to Vet a Plugin Before You Install It
A few minutes of checking up front is cheaper than remediation later. Try this on a staging site:
- Unplug your mouse and complete the plugin’s main task using only Tab, Shift+Tab, Enter, Space, and Escape.
- Confirm you can always see where focus is.
- Zoom the page to 200% and check that nothing is cut off or overlapping.
- Turn on a screen reader and listen to how the component is announced.
- Check the plugin’s documentation, changelog, and support forum for any mention of accessibility. An “accessibility-ready” claim is a good sign, but verify it yourself.
What to Do When a Plugin Has Problems
You have several options, in roughly this order of preference:
- Report it. Open a clear support ticket describing the barrier and the WCAG criterion it fails. Many developers fix issues once they have a specific report.
- Check settings. Some plugins have options for pausing autoplay, enabling keyboard support, or changing markup.
- Fix it in a child theme or custom code. If you can safely adjust the output, for example by adding labels through a filter, do so and document the change.
- Swap it out. If a plugin is unmaintained or the problems are structural, a better alternative is usually the right long-term answer.
- Remove the feature. Not every page needs a carousel or a popup.
Remember that plugin updates can reintroduce problems you already fixed. Re-test after major updates, especially for components that carry a lot of interaction.
What Automated Scanning Can and Can’t Tell You
Automated scanners are good at finding missing labels, empty links, low contrast, and invalid ARIA, which covers a large share of plugin-generated issues. They can’t tell you whether a modal’s focus handling feels right or whether a carousel makes sense when read aloud. Treat scan results as a strong starting point, and pair them with manual keyboard and screen reader checks. No tool can promise full compliance on its own.
Take Action
LEWCA’s WCAG scanner checks your rendered pages, including output from your plugins, and points to the code-level issues behind each failure instead of covering them with an overlay. The accessibility toolbar gives visitors extra display controls, and Pro adds AI-powered code fix suggestions, scheduled scans so plugin updates don’t quietly break things, and compliance reports. See the options on our pricing page or download LEWCA and run your first scan today.