If you run a WooCommerce store, start with the barriers on your own pages. Scan a product page, cart, and checkout, then try each flow with a keyboard and screen reader. A plugin can help with specific issues, but its feature list is not proof that your store passes an accessibility audit.

This guide gives you a way to choose tools and check their results. For a vendor-by-vendor comparison, see the WCAG WordPress plugin comparison.

Quick answer

There is no single best WordPress accessibility plugin. There are three categories, and a real WooCommerce store usually needs one from each:

  1. A scanner / checker that audits your pages against WCAG 2.1 and 2.2 AA. Examples: Equalize Digital Accessibility Checker, Sa11y, WAVE browser extension.
  2. A site-wide fixer that patches generic WordPress issues (skip links, lang attribute, focus indicators). Example: WP Accessibility by Joe Dolson.
  3. A WooCommerce-specific fixer for the issues it demonstrably handles, such as missing product-image alt text or selected focus styles. Test cart and checkout behavior separately.

Treat any claim of instant compliance skeptically. The FTC’s accessiBe case ended in a $1 million settlement over deceptive accessibility claims. A widget or fixer still needs testing against the barriers on your store.

The SERP for this keyword is full of affiliate roundups that list 10 plugins and rank whichever one pays the highest commission. That is not how accessibility works.

Many WCAG checks need human judgment. A tool can find an empty alt attribute, for example, but cannot tell whether a product description conveys the useful detail in the image. The same applies to heading order, readable language, and custom checkout flows.

So when you compare plugins, do not ask “which one makes my site compliant”. Ask:

  • Which WCAG 2.2 criteria does it actually fix in code?
  • Which does it only flag in a report?
  • Does it understand WooCommerce templates, or only generic WordPress?
  • Does it leave behind a JavaScript widget, or does it edit the real HTML?

The plugins worth considering in 2026

Equalize Digital Accessibility Checker

Use a scanner to collect issues for review, then verify the reported barriers in the rendered store. Check the current plugin listing for its supported scans and features before choosing it.

WP Accessibility by Joe Dolson

Check the current WP Accessibility listing for its supported fixes, then test those fixes on your theme. In particular, test WooCommerce templates rather than assuming a site-wide WordPress setting covers checkout.

One Click Accessibility (by POJO)

If you consider a toolbar or widget, test what it changes in the default page and whether the underlying barriers remain. A visitor should not have to discover and activate a control before they can use checkout.

accessiBe / UserWay / AudioEye widget

Review each product’s current features and test the unmodified page as well as any visitor controls. Do not rely on a vendor’s compliance promise as a substitute for checking the cart and checkout.

AP Accessibility Fixer for WooCommerce (AmazingPlugins)

Disclosure: this is our plugin. We reviewed the public WordPress.org release 1.5.1 on September 28, 2026. Its nine free fixers include a fallback for missing product-image alt text, styles for selected focus and error states, form labels in post content, skip links, and specific keyboard-trap handling. Some fixes add inline JavaScript. The release does not provide a general contrast-ratio scanner or blanket checkout-template repair.

The WCAG 2.2 criteria a WooCommerce store actually fails on

Use these WCAG criteria as a checklist for your own store. The examples below are possible barriers, not findings from a test of every WooCommerce theme:

  • 1.1.1 Non-text Content - product images without alt text, decorative SVGs without aria-hidden.
  • 1.3.1 Info and Relationships - checkout fields where the label is a placeholder instead of a real <label>.
  • 1.4.3 Contrast (Minimum) - sale prices in light gray on white, “Add to cart” buttons that fail 4.5:1.
  • 2.1.1 Keyboard - variation swatches and quantity pickers that don’t respond to Tab and Enter.
  • 2.4.1 Bypass Blocks - missing skip link to the main content.
  • 2.4.4 Link Purpose - “Read more” links that don’t say what they link to.
  • 2.4.7 Focus Visible - outline removed by the theme with outline: none.
  • 2.4.11 Focus Not Obscured (Minimum) - new in WCAG 2.2; sticky headers and cart popups hiding the focused element.
  • 2.5.8 Target Size (Minimum) - new in WCAG 2.2; quantity minus/plus buttons smaller than 24x24 CSS pixels.
  • 3.1.1 Language of Page - missing or wrong lang attribute on <html>.
  • 3.3.2 Labels or Instructions - checkout fields with no programmatic label.
  • 4.1.2 Name, Role, Value - icon-only buttons (close cart, remove item) with no accessible name.

If you want the full breakdown of what changed in 2.2, see WCAG 2.2 Is Here. What Does It Mean for Your WordPress or WooCommerce Store?.

A practical workflow: how to pick and install the right plugins

This is the order I would follow on a real store.

Step 1. Run a baseline scan. Scan your home page, one category page, one product page, the cart, and the checkout. Save the issue list. Also try each flow with a keyboard and screen reader so you can compare automated results with real use.

Step 2. Check the site-wide basics. Look for a working skip link, a correct page language, and visible keyboard focus. If your theme misses one, use a verified plugin setting or a theme fix, then test the result.

Step 3. Fix WooCommerce-specific issues. Check the variation form, cart, and checkout on your own theme. Use a plugin where its released code covers the issue; use a theme or template fix for the rest. Re-test after each change.

Step 4. Write real alt text for product images. No plugin can do this correctly. “Blue cotton t-shirt, size medium, model wearing with jeans” is good alt text. “product_image_4837.jpg” or “blue t-shirt blue t-shirt blue t-shirt” is not. A plugin can flag missing alts and auto-fill from the product title as a fallback, but you should review them.

Step 5. Publish an accessibility statement. Describe what you have checked, known limitations, and a way for customers to report a barrier. Get jurisdiction-specific legal advice if you need to describe a compliance obligation.

Step 6. Re-scan and document. Run the same checks again, save the results, and assign remaining issues to someone who can fix them.

For a store-specific sequence of checks, use the WooCommerce accessibility checklist.

If you want the direct comparison between a real WooCommerce accessibility plugin and a widget overlay, read WooCommerce plugin vs widget accessibility. For a side-by-side of scanners, fixers, and overlays aimed at the “best WCAG WordPress plugin” search, use Best WCAG WordPress plugins compared.

If you need the rollout plan after you pick a tool, use ADA ecommerce remediation plan template so the fixes, owners, and re-scan dates are written down.

How AmazingPlugins helps

The public 1.5.1 release of AP Accessibility Fixer for WooCommerce has nine free fixers and no Pro tier. It:

  • Fills empty product-image alt text from an image or product title. You still need to review the wording.
  • Adds accessible names to some unlabeled inputs in post content. It does not demonstrate a general checkout-template label fix.
  • Adds focus outlines and error borders for selected WooCommerce fields. It does not calculate text contrast ratios.
  • Adds a skip link and specific Escape-key handling through small inline scripts.
  • Adjusts some heading levels in post content and adds a main landmark when a matching wrapper exists.

It does not install a floating overlay widget. Some fixes use inline JavaScript and CSS at render time. Check the plugin page for the other fixers and their limits.

What it does not do, because no automated tool honestly can: write meaningful alt text, restructure your custom one-page checkout, or make a poorly designed mega menu keyboard-friendly. Those need a human.

People also ask

Is there a free WordPress accessibility plugin that makes my site compliant?

No. Free plugins like WP Accessibility and the free tier of Equalize Digital cover real ground (skip links, lang attribute, scanning), but no plugin, free or paid, makes a site fully WCAG 2.2 AA compliant on its own. Compliance is a combination of plugin fixes, theme code, and human-written content.

Installing a widget does not, by itself, establish that your store is accessible. The FTC announced a $1 million settlement with accessiBe over deceptive claims. Test the default page and purchase flow regardless of the tool you choose.

Do I need a WooCommerce-specific plugin or is a generic WordPress one enough?

Test the cart, checkout, product variation forms, and quantity controls directly. If a generic plugin leaves a barrier in those flows, use a WooCommerce-specific change that you can verify on your theme.

What is the difference between WCAG 2.1 AA and WCAG 2.2 AA for a WooCommerce store?

WCAG 2.2 added nine success criteria. For a store, check whether sticky headers obscure focus, whether drag interactions have an alternative, and whether small controls meet the target-size criterion. The applicable legal standard depends on your jurisdiction and type of organization; use the W3C WCAG 2.2 standard for the technical criteria.

How much should I budget for an accessibility plugin?

Start with free scans and manual checks to identify your actual barriers. AP Accessibility Fixer for WooCommerce includes all nine fixers free and has no Pro tier. If you need paid testing or development, price the work against a written list of issues rather than a generic package.

Will any of this protect me from an ADA lawsuit?

No plugin is a legal shield. Keep a record of the barriers found, the changes made, and the issues still open. Ask a qualified lawyer about legal exposure for your business.

The honest takeaway

Choose tools from the issues you found on your own store. Use a scanner to locate candidates, check them manually, and verify every fix on the live theme and checkout. Review generated alt text. Re-scan after theme and plugin updates.

If you need the next step, use WooCommerce plugin vs widget accessibility as the buying filter before you spend money on the wrong thing.

If you are comparing specific vendors, use: