Skip to main content
Back to Blog
Tools & Platforms

WordPress Accessibility Plugins: What Works (and What Doesn't) in 2025

Comprehensive WordPress accessibility plugins comparison for 2025. Why most overlay plugins fail, what real accessibility requires, and how to choose the right solution for WCAG 2.2 compliance.

AllAccessible Team
12 min read
WordPressAccessibility PluginsWCAG 2.2WordPress AccessibilityOverlay Widgets
WordPress Accessibility Plugins: What Works (and What Doesn't) in 2025

WordPress Accessibility Plugins: What Works (and What Doesn't) in 2025

WordPress powers 43% of all websites, making it the most popular CMS globally. With 4,605 ADA lawsuits filed in 2024 and the European Accessibility Act now in force since June 28, 2025, WordPress site owners are searching for accessibility solutions—but most WordPress accessibility plugins don't deliver what they promise.

This comprehensive guide explains what actually works for WordPress accessibility, compares popular plugins, and helps you choose the right solution for genuine WCAG 2.2 compliance.

What you'll learn:

  • ✅ Why most "1-click accessibility" plugins fail
  • ✅ Overlay widgets vs. code remediation (what's the difference?)
  • ✅ Comparison of top WordPress accessibility plugins
  • ✅ What real accessibility requires
  • ✅ How to choose the right solution for your site
  • ✅ Testing and validation protocols

Table of Contents

  1. The WordPress Accessibility Problem
  2. What is an Accessibility Overlay?
  3. Why Overlay Plugins Fail
  4. Remediation vs. Overlays
  5. WordPress Accessibility Plugins Comparison
  6. What Real Accessibility Requires
  7. How to Choose the Right Plugin
  8. DIY WordPress Accessibility
  9. Testing WordPress Sites

The WordPress Accessibility Problem

Why WordPress Sites Have Accessibility Issues

WordPress is accessible by default (semantic HTML, proper heading structure, keyboard navigation) but themes and plugins break it:

Common issues:

  • ❌ Themes with insufficient color contrast
  • ❌ Slider plugins without keyboard controls
  • ❌ Page builders (Elementor, Divi) generating inaccessible code
  • ❌ Form plugins without proper labels
  • ❌ E-commerce plugins (WooCommerce) with inaccessible checkouts
  • ❌ Popups and modals trapping keyboard focus

The promise: Many plugins claim "1-click accessibility" or "instant WCAG compliance"—but accessibility doesn't work that way.

What is an Accessibility Overlay?

An accessibility overlay (also called widget or toolbar) is a JavaScript plugin that adds a floating icon to your site. When clicked, it opens a panel with accessibility "features" like:

  • Font size adjustment
  • Color contrast toggles
  • Screen reader mode
  • Cursor size changes
  • Keyboard navigation
  • Dyslexia-friendly fonts

Popular overlay solutions:

  • AccessiBe
  • UserWay
  • AudioEye
  • EqualWeb
  • Equally AI

The pitch: "Add 1 line of code and become WCAG compliant instantly!"

The reality: Overlays are widely criticized by accessibility experts and cited in lawsuits as ineffective.

Why Overlay Plugins Fail

1. Overlays Don't Fix the Underlying Code

The fundamental problem:

Overlays add a JavaScript layer on top of inaccessible code. They don't fix:

  • Missing alt text
  • Improper heading structure
  • Unlabeled form fields
  • Keyboard traps
  • Color contrast issues in images/logos

Example:

<!-- Original HTML (inaccessible) -->
<img src="product.jpg">

<!-- With overlay JS -->
<img src="product.jpg">
<!-- Overlay adds screen reader mode, but image still has no alt text! -->

What users actually experience:

  • Screen reader users: Still can't access images without alt text
  • Keyboard users: Still trapped in inaccessible modals
  • Low-vision users: Still can't read low-contrast text

2. Overlays Create New Accessibility Barriers

Overlay widgets themselves often have accessibility issues:

  • Keyboard traps (can't Tab out of overlay)
  • No screen reader announcements
  • Confusing interface for users with cognitive disabilities
  • Performance impact (JavaScript bloat)

Irony: Tools designed to "fix" accessibility often create new barriers.

3. Overlays Are Used in Lawsuits as Evidence

Legal cases where overlays failed:

Murphy v. Eyebobs (2021):

  • Site used AccessiBe overlay
  • Plaintiff (blind screen reader user) could not access site
  • Court allowed case to proceed despite overlay
  • Outcome: Overlay did not prevent lawsuit

Mendez v. Apple Leisure (2021):

  • Site used AudioEye overlay
  • Lawsuit filed citing numerous accessibility violations
  • Overlay widget itself had accessibility issues
  • Outcome: Company settled

Key takeaway: Overlays are not a legal defense against ADA lawsuits.

4. The Overlay Fact Sheet

The Overlay Fact Sheet (overlayfactsheet.com) is signed by over 700 accessibility professionals stating:

"Overlays, as a category, do not and cannot provide comprehensive accessibility. They do not solve underlying accessibility issues in the source code."

Signatories include:

  • WebAIM (Utah State University)
  • Deque Systems (makers of axe DevTools)
  • The Paciello Group
  • Hundreds of certified accessibility specialists

Remediation vs. Overlays

What's the Difference?

AspectOverlay PluginsRemediation Plugins
ApproachJavaScript layer on topFixes source code
EffectivenessAddresses ~10-20% of issuesAddresses 90-100% of issues
PermanenceTemporary (requires JS enabled)Permanent (baked into HTML)
Screen reader supportLimitedFull
Keyboard accessibilityOften breaks itFully supports it
Legal defensibilityWeak (used in lawsuits)Strong (actual compliance)
PerformanceAdds JS overheadMinimal impact
MaintenanceOngoing JS updatesOne-time code fixes
Cost$500-$5,000/year$500-$5,000 (one-time)

Real Accessibility Requires Code Changes

You cannot achieve WCAG compliance without fixing the HTML:

Issue 1: Missing alt text

<!-- Overlay can't fix this -->
<img src="product.jpg">

<!-- Real fix required -->
<img src="product.jpg" alt="Blue cotton t-shirt, crew neck">

Issue 2: Unlabeled form input

<!-- Overlay can't fix this -->
<input type="email" placeholder="Email">

<!-- Real fix required -->
<label for="email">Email Address</label>
<input type="email" id="email" name="email">

Issue 3: Low color contrast

/* Overlay toggles colors for individual users, but doesn't fix source */
.button {
  color: #999; /* 2.8:1 contrast - fails WCAG */
  background: #FFF;
}

/* Real fix required */
.button {
  color: #595959; /* 7:1 contrast - passes WCAG AAA */
  background: #FFF;
}

WordPress Accessibility Plugins Comparison

Category 1: Overlay Widgets (Not Recommended)

AccessiBe for WordPress

  • Type: Overlay widget
  • Cost: $490-$990/year
  • Effectiveness: Low (~15% of issues)
  • Legal risk: High (cited in lawsuits)
  • Verdict: ❌ Not recommended

UserWay WordPress Plugin

  • Type: Overlay widget
  • Cost: Free-$690/year
  • Effectiveness: Low (~10% of issues)
  • Legal risk: High
  • Verdict: ❌ Not recommended

Category 2: Testing & Auditing Tools

WP Accessibility Helper (WAH)

  • Type: Accessibility checker
  • Cost: Free (basic) / $99/year (pro)
  • Features: Scans pages, identifies issues, provides recommendations
  • Effectiveness: Good for identifying issues, doesn't fix them
  • Verdict: ✅ Recommended for auditing, not remediation

Accessibility Checker (Equalize Digital)

  • Type: WordPress-native accessibility scanner
  • Cost: Free (basic) / $299/year (pro)
  • Features:
    • Scans content as you write
    • Highlights accessibility issues in WordPress editor
    • Comprehensive reports
  • Effectiveness: Excellent for detection
  • Verdict: ✅ Highly recommended for content teams

Category 3: Remediation Tools

AllAccessible for WordPress

  • Type: Real-time remediation + monitoring
  • Cost: Starting at $10/month
  • Features:
    • Fixes missing alt text (AI-powered)
    • Corrects color contrast issues
    • Adds form labels
    • Implements keyboard navigation
    • Continuous monitoring
    • Actually modifies HTML/CSS (not just JS overlay)
  • Effectiveness: High (90%+ of issues)
  • Legal risk: Low (actual code fixes)
  • Verdict: ✅ Recommended for genuine compliance

WP Accessibility (Joe Dolson)

  • Type: Code-level fixes
  • Cost: Free
  • Features:
    • Adds skip links
    • Improves toolbar navigation
    • Outline fixes for keyboard focus
    • Adds landmark roles
    • Forces title attributes on links
  • Effectiveness: Medium (addresses common issues)
  • Limitations: Doesn't fix theme/plugin issues, requires manual work
  • Verdict: ✅ Good free starting point

Category 4: Specialized Plugins

WooCommerce Accessibility

  • Type: WooCommerce enhancement
  • Cost: Free
  • Features:
    • Accessible product filtering
    • Screen reader cart announcements
    • Keyboard-accessible checkout
  • Effectiveness: High for WooCommerce stores
  • Verdict: ✅ Essential for WooCommerce sites

Accessible Poetry

  • Type: Frontend accessibility fixes
  • Cost: Free
  • Features:
    • Keyboard navigation improvements
    • Focus management
    • ARIA landmark corrections
  • Effectiveness: Medium
  • Verdict: ✅ Useful supplement to other solutions

What Real Accessibility Requires

1. Fix the Source Code

You must address:

Images:

  • Add alt attributes to all <img> tags
  • Use empty alt (alt="") for decorative images
  • Provide long descriptions for complex images

Forms:

  • Associate labels with inputs (<label for="id">)
  • Add error messages with aria-describedby
  • Mark required fields with required attribute

Navigation:

  • Implement skip links
  • Use semantic HTML (<nav>, <main>, <header>, <footer>)
  • Ensure logical heading structure (h1 → h2 → h3)

Color contrast:

  • Update CSS for 4.5:1 minimum contrast
  • Don't rely on color alone to convey information

Keyboard accessibility:

  • All functionality available via keyboard
  • Visible focus indicators (3:1 contrast)
  • No keyboard traps

2. Choose Accessible Themes

Accessibility-ready WordPress themes:

  • Twenty Twenty-Five (default WordPress theme)
  • Astra (with accessibility mode enabled)
  • GeneratePress (WCAG compliant)
  • Neve (accessibility-ready)
  • Kadence (built with a11y in mind)

Avoid themes with known issues:

  • Themes relying heavily on visual editors
  • Themes with fixed headers that hide focused elements
  • Themes with insufficient color contrast

How to check: Look for "Accessibility Ready" tag in WordPress theme repository.

3. Audit Plugins

Not all WordPress plugins are accessible.

Before installing:

  1. Check plugin reviews for accessibility mentions
  2. Test with keyboard navigation
  3. Run automated scan (axe DevTools)
  4. Test with screen reader (NVDA)

Common inaccessible plugins:

  • Slider/carousel plugins (often no keyboard controls)
  • Popup builders (keyboard traps)
  • Form builders (missing labels)
  • Page builders (generate inaccessible code)

4. Test Continuously

Accessibility is not "set and forget":

  • New content may introduce issues
  • Plugin updates can break accessibility
  • Theme updates may change markup

Testing schedule:

  • Weekly: Automated scans (axe, WAVE)
  • Monthly: Keyboard navigation testing
  • Quarterly: Full screen reader testing
  • After updates: Test themes/plugins before deploying

How to Choose the Right Plugin

Decision Tree

Question 1: Do you need testing or fixes?

Testing/Auditing:

  • → Use Accessibility Checker (Equalize Digital)
  • Identifies issues in WordPress editor
  • Doesn't fix automatically

Automated Fixes:

  • → Use AllAccessible for WordPress
  • Fixes issues in real-time
  • Continuous monitoring

Both:

  • → Use AllAccessible (includes monitoring + fixes)
  • Or combine WP Accessibility (free fixes) + Accessibility Checker (auditing)

Question 2: What's your budget?

Free:

  • WP Accessibility (basic fixes)
  • Accessibility Checker (basic scanning)

Under $500/year:

  • Accessibility Checker Pro ($299/year)
  • WP Accessibility Helper Pro ($99/year)

$120+/year:

  • AllAccessible (starting at $10/month for comprehensive remediation)

Question 3: Do you have a developer?

No developer:

  • → Use AllAccessible (automated fixes, no coding required)
  • Or pay for manual audit + remediation service

Have developer:

  • → Use Accessibility Checker to identify issues
  • → Developer implements fixes manually
  • → Use WP Accessibility for baseline improvements

DIY WordPress Accessibility

Step-by-Step Implementation

1. Choose an accessible theme

  • Install Twenty Twenty-Five or accessibility-ready theme
  • Enable built-in accessibility features

2. Install baseline plugins

- WP Accessibility (free fixes)
- Accessibility Checker (content scanning)

3. Fix existing content

  • Run site-wide scan with Accessibility Checker
  • Add alt text to images in Media Library
  • Fix form labels in Contact Form 7 or Gravity Forms
  • Update low-contrast colors in theme customizer

4. Configure WordPress settings

Settings → Reading:
- Ensure "Search engine visibility" is OFF (allows indexing)

Settings → Permalinks:
- Use "Post name" structure (SEO-friendly, accessible URLs)

Appearance → Menus:
- Add descriptive menu labels
- Use "Screen Reader Text" for icons

5. Test with automated tools

  • Install axe DevTools browser extension
  • Scan homepage, blog post, product page, contact form
  • Fix critical issues (missing alt text, form labels)

6. Test manually

  • Tab through entire site (keyboard only)
  • Verify all functionality accessible
  • Test with NVDA or VoiceOver

Testing WordPress Sites

Automated Testing

1. axe DevTools

Install Chrome extension: https://chrome.google.com/webstore/detail/axe-devtools-web-accessib/lhdoppojpmngadmnindnejefpokejbdd

Steps:

  1. Open page to test
  2. Open DevTools (F12)
  3. Click "axe DevTools" tab
  4. Click "Scan ALL of my page"
  5. Review violations

2. WAVE

Install extension or use web service: https://wave.webaim.org/

Steps:

  1. Navigate to your WordPress page
  2. Click WAVE extension icon
  3. Review errors (red) and alerts (yellow)
  4. Fix critical issues first

Manual Testing

Keyboard navigation checklist:

  • Tab through entire page
  • All links and buttons reachable
  • Focus indicator visible (WCAG 2.4.11)
  • Menus accessible with keyboard
  • Forms submittable with Enter key
  • Modals/popups close with Escape
  • No keyboard traps

Screen reader testing:

NVDA (Windows):

  1. Download from https://www.nvaccess.org/
  2. Install and launch
  3. Navigate your WordPress site
  4. Verify:
    • Images have alt text announced
    • Headings announce correctly
    • Forms have labels
    • Links describe destination

Conclusion

WordPress accessibility requires real code fixes, not JavaScript overlays.

Key Takeaways:

  1. ❌ Avoid overlay plugins (AccessiBe, UserWay, AudioEye) - They don't work and won't protect you legally
  2. ✅ Choose accessibility-ready themes - Start with a good foundation
  3. ✅ Use remediation plugins - AllAccessible or WP Accessibility for actual fixes
  4. ✅ Test continuously - Accessibility is ongoing, not one-time
  5. ✅ Audit plugins before installing - Not all WordPress plugins are accessible
  6. ✅ Fix source code - Add alt text, form labels, proper heading structure

Recommended Setup:

Budget-conscious:

  • Theme: Twenty Twenty-Five (free)
  • Plugin: WP Accessibility (free)
  • Testing: Accessibility Checker (free version)
  • Manual fixes by developer

Full compliance:

  • Theme: Accessibility-ready premium theme
  • Plugin: AllAccessible for WordPress (automated remediation)
  • Testing: Accessibility Checker Pro (continuous scanning)
  • Quarterly manual audits

Next Steps:

  1. Remove any overlay plugins currently installed
  2. Install WP Accessibility (free baseline fixes)
  3. Run automated scan with axe DevTools or WAVE
  4. Fix critical issues (missing alt text, form labels)
  5. Test with keyboard and screen reader
  6. Consider AllAccessible for comprehensive automation

Need help? AllAccessible for WordPress provides automated remediation, AI-powered alt text, and continuous monitoring for genuine WCAG 2.2 compliance. Start free trial →

Published: November 17, 2025 Last Updated: November 17, 2025 Reading Time: 18 minutes

About AllAccessible: We provide real accessibility remediation (not overlays) with automated code fixes, AI-powered alt text generation, and continuous WCAG 2.2 monitoring for WordPress sites. Learn more at allaccessible.org.

Share this article