If you’re choosing a WCAG WordPress plugin, compare what each tool actually changes. A scanner reports possible issues, a fixer changes selected output, and a visitor widget adds controls to the page. Those jobs need different checks.
This comparison uses publicly described features and, for our plugin, a review of the released 1.5.1 code on September 28, 2026. It is not a hands-on test of every vendor. If you need a step-by-step selection process, use the WordPress accessibility plugin guide.
Quick answer
There isn’t one best WCAG WordPress plugin. A serious site usually needs a stack:
- Scanner to find issues (Equalize Digital Accessibility Checker, WAVE, axe DevTools)
- Site-wide fixer for generic WordPress gaps (WP Accessibility)
- WooCommerce fixer for issues it demonstrably covers in your store
- Visitor widget, if its controls solve a need you have tested; verify the purchase flow separately
If you only install one thing and hope for “compliant,” you’ll be disappointed. WCAG is a mix of code, content, and design judgment.
Comparison matrix
| Type | Examples | What it does | Best for | Weak at |
|---|---|---|---|---|
| Scanner / checker | Equalize Digital Accessibility Checker, WAVE, axe | No (reports) | Finding issues in posts, pages, products | Auto-fixing checkout or theme bugs |
| Site-wide fixer | WP Accessibility | Yes, limited | Skip links, lang, focus basics | WooCommerce templates |
| WooCommerce fixer | AP Accessibility Fixer for WooCommerce (ours, 1.5.1) | Selected hooks, content filters, CSS, and inline scripts | Empty product-image alt fallback, selected focus styles, skip link | Full checkout repair, contrast measurement, legal guarantees |
| Overlay / widget | accessiBe, UserWay, AudioEye (widget mode) | Adds visitor controls and may change the live DOM | Specific user controls that work on your store | Proving the whole purchase flow works |
For a deeper look at plugin vs overlay, see WooCommerce plugin vs widget accessibility, the WooCommerce accessibility widget comparison, and why overlays don’t protect you from ADA lawsuits.
Scanners: best WCAG WordPress plugin for finding problems
A scanner is not a fixer. That is a feature, not a flaw.
Equalize Digital Accessibility Checker runs inside the WordPress editor and flags WCAG issues on posts, pages, and products. It’s strong when you want a report you can work from. It won’t rewrite your checkout for you.
WAVE and axe DevTools live in the browser. Use them while you click through cart and checkout. They catch a lot of theme and plugin markup that admin-only scanners miss.
Use a scanner when: you need a punch list before a redesign, after a theme update, or before you hire anyone to remediate.
Don’t expect it to: make the site pass WCAG by itself.
Site-wide fixers: generic WordPress WCAG gaps
WP Accessibility (Joe Dolson) is the classic free fixer for WordPress basics: skip links, language attribute, some focus and toolbar options. On a brochure site it can cover a lot of the boring failures.
On WooCommerce, it usually stops at the storefront chrome. Variation swatches, quantity controls, and checkout labels live in Woo templates that a generic fixer doesn’t own.
Use a site-wide fixer when: your theme is missing skip links or lang, and you want those fixed in the real document.
Pair it with: a scanner, and a WooCommerce-specific tool if you sell online.
WooCommerce fixers: where most stores fail WCAG
Ecommerce fails WCAG in predictable places: product images without alt text, unlabeled checkout fields, keyboard traps in cart drawers, tiny plus/minus targets, focus lost under sticky headers.
A WooCommerce accessibility plugin should hook into those templates and fix markup, not inject a floating toolbar.
Disclosure: AP Accessibility Fixer for WooCommerce is our plugin. The public 1.5.1 release has nine free fixers. They cover a fallback for missing product-image alt text, selected focus and error styles, form labels in post content, a skip link, and other limited changes. Some fixes use inline scripts. The release does not demonstrate general cart or checkout label repair.
Use a WooCommerce fixer when: scanners keep flagging product and checkout issues that generic WordPress plugins ignore.
Don’t expect it to: rewrite product descriptions, invent meaningful alt text for every photo without your input, or give you a legal certificate.
Check what a visitor widget changes
A browser script can change the live DOM and the accessibility tree a screen reader uses. The result depends on the product and the page. It may help with a specific control, miss a payment iframe, or interfere with focus in a cart drawer. Test the same purchase steps with the widget on and off.
The FTC’s accessiBe order addressed unsupported automated-compliance claims by that vendor. It did not rule that every widget is unlawful. Our overlay and ADA guide explains the testing and legal limits.
How to choose the best WCAG WordPress plugin for your site
Ask four questions:
- What does it change or report? Ask the vendor for the specific controls and pages it covers.
- Does it understand WooCommerce? If you sell products, generic WordPress coverage is not enough.
- Can you retest after a theme update? You want a workflow, not a one-time toggle.
- What still needs a human? Alt text quality, heading sense, form instructions, and custom flows always do.
A practical stack for most WooCommerce stores:
- Equalize Digital or axe for scanning
- WP Accessibility for WordPress basics
- A WooCommerce fixer for the product and storefront issues its released code covers
- Manual review of the top conversion paths with a keyboard and a screen reader
More context in our full WooCommerce accessibility plugin guide.
Verify the result on the real storefront
Do not judge a WCAG plugin from its settings screen. Open the homepage, a product page, the cart, and checkout in a private browser window. Turn off browser extensions that change contrast or font size. Then test the page with a keyboard and at least one screen reader.
Check that focus stays visible, labels still describe the right fields, quantity controls have useful names, and cart updates are announced. Run a scanner after the manual pass. AmazingPlugins’s WooCommerce Accessibility Fixer can handle repeatable markup fixes, but it cannot decide whether product alt text is meaningful or whether a custom payment flow works for every customer.
FAQ
Is there a single best WCAG WordPress plugin?
No. “Best” depends on whether you need detection, generic WordPress fixes, or WooCommerce template fixes. One plugin can’t honestly own all three at a high level.
What’s the difference between a WCAG WordPress plugin and an accessibility widget?
A plugin may change server output, add styles or scripts, or report issues. A widget usually adds visitor controls and can change the live page. Test either approach on the same product and checkout tasks. See plugin vs widget.
Can a free WordPress accessibility plugin make my site WCAG 2.2 AA compliant?
Free tools can fix real issues and surface many more. Full AA still needs theme work, content decisions, and retesting. No plugin, free or paid, is a complete substitute for that.
Do I need a WooCommerce-specific WCAG plugin?
Not automatically. First test checkout, cart, and product variations with your theme and extensions. Choose a WooCommerce-specific tool only when it addresses a barrier you have found and can verify.
Test before keeping a tool
Use a scanner to find candidates, fix the component producing each barrier, and test the result. Keep a widget or plugin only for the specific change it delivers on your store.
Start with a keyboard pass of your homepage, product page, and checkout. Then pick the tool type that matches the failures you actually see.