A website accessibility plugin is a WordPress add-on that scans your site against the WCAG 2.1 or 2.2 AA standard and fixes (or helps you fix) the issues it finds, things like missing alt text, broken keyboard navigation, low color contrast, unlabeled form fields, and missing skip links. The good ones edit your actual HTML and CSS. The bad ones load a JavaScript overlay on top of your site, change nothing underneath, and have a track record of getting stores sued anyway.

If you run a WooCommerce store, you need one. Not because plugins are magic, but because 95.9% of home pages on the web fail WCAG 2 (WebAIM Million 2026), 5,114+ ADA digital lawsuits were filed in 2025, and the European Accessibility Act has been enforceable since June 28, 2025 for anyone selling into the EU. The right plugin closes most of the easy gaps. The wrong one gives you a false sense of safety.

This guide covers what a website accessibility plugin actually does, what it cannot do, how to choose one for WooCommerce, and the exact WCAG criteria it should be checking.

Quick answer

  • A website accessibility plugin scans your site for WCAG failures and applies code-level fixes (alt text, ARIA labels, focus indicators, keyboard nav, color contrast, skip links).
  • For WooCommerce, you want a plugin that hooks into WooCommerce templates and the WordPress filter system, not a generic JavaScript widget bolted on top.
  • Overlay-style plugins (the floating accessibility button that opens a sidebar) do not provide legal protection. Plaintiffs and the FTC have repeatedly called them out.
  • Expect to pay $10 to $50 per month for a real fixer plugin. Free scanners exist but rarely apply fixes automatically.
  • No plugin gets you to 100% compliance. Roughly 30 to 40% of WCAG criteria require human judgment (meaningful alt text, accessible content order, plain language).

What a website accessibility plugin actually does

There are three categories, and they are not interchangeable.

1. Scanners (find problems, do not fix them)

These crawl your pages and produce a report. You see what fails, on which page, against which WCAG criterion. You then fix it manually or hand the list to a developer. Examples include WAVE, axe DevTools, and Equalify. Useful, but they do nothing automatically.

2. Real fixer plugins (find AND fix at the code layer)

These run as a WordPress plugin, integrate with WooCommerce templates, and apply fixes that survive in the page source. If you turn the plugin off, the broken parts come back, but while it is on the markup is genuinely accessible. The WooCommerce Accessibility Fixer is in this category, and so are a few other WordPress-native tools.

3. Overlay widgets (load a JS layer on top of your site)

This is the floating wheelchair-icon button. The user clicks it, a sidebar appears with toggles for font size, contrast, dyslexia font, and so on. The underlying HTML is unchanged. Screen reader users get a worse experience because the overlay frequently injects its own ARIA chaos. accessiBe, UserWay, and AudioEye are the big names. The FTC settled with accessiBe in 2024 over its compliance claims, and overlay-only stores still get sued routinely. Avoid these for legal protection.

The exact WCAG criteria a good plugin handles

Not all 78 WCAG 2.2 AA success criteria are automatable. Here is the realistic split for WooCommerce.

Fully automatable (a plugin can fix these):

  • 1.1.1 Non-text Content - adds alt text to product images (or flags missing ones).
  • 1.3.1 Info and Relationships - adds proper ARIA labels to WooCommerce form fields, billing/shipping/checkout.
  • 1.4.3 Contrast (Minimum) - overrides theme CSS for body text and buttons that fail 4.5:1 ratio.
  • 2.1.1 Keyboard - ensures all interactive elements are focusable.
  • 2.4.1 Bypass Blocks - injects a skip-to-content link.
  • 2.4.7 Focus Visible - restores visible focus outlines that themes love to remove with outline: none.
  • 3.1.1 Language of Page - sets the lang attribute on <html>.
  • 4.1.2 Name, Role, Value - adds accessible names to icon buttons (cart icon, search icon, menu toggle).

Partially automatable (plugin helps, you still review):

  • 1.1.1 alt text quality - the plugin can add alt attributes, but “meaningful” alt text needs human review for product photos.
  • 2.4.4 Link Purpose - flags ambiguous links like “read more” but you write the replacements.
  • 3.3.2 Labels or Instructions - flags missing form instructions, you write them.

Not automatable (you handle these yourself):

  • 1.3.2 Meaningful Sequence - content reading order in custom page builders.
  • 2.4.6 Headings and Labels - descriptiveness is editorial.
  • 3.1.5 Reading Level - plain language is a writing problem.
  • 3.3.4 Error Prevention - checkout flow logic for legal/financial transactions.

If a plugin claims to fix all 78 criteria automatically, that is a marketing claim, not an engineering one.

How to choose a website accessibility plugin for WooCommerce

A seven-step evaluation that takes about an hour.

Step 1: Read the plugin’s own homepage with a screen reader. Turn on VoiceOver (Mac) or NVDA (Windows free) and navigate the vendor site. If their own site is annoying to use, do not buy their tool.

Step 2: Check if it is WordPress-native or a JavaScript widget. Look at how it loads. View the page source. If everything happens inside one <script> tag from cdn.something.com, it is an overlay. If you see actual changes in your post HTML, alt attributes added, ARIA labels in form fields, it is a real fixer.

Step 3: Verify WooCommerce-specific coverage. Generic WordPress accessibility plugins often skip WooCommerce-specific elements: variation forms, cart quantity steppers, mini-cart, checkout review tables, My Account tabs. Ask the vendor for a list of WooCommerce templates they touch.

Step 4: Look for WCAG 2.2 support, not just 2.1. WCAG 2.2 became the W3C recommendation in October 2023 and is the de facto best-practice standard in 2026. The EAA’s technical standard EN 301 549 still references 2.1 AA as the legal floor, but 2.2 adds nine criteria you want covered, especially 2.4.11 Focus Not Obscured and 2.5.8 Target Size (Minimum) which directly affect mobile checkout.

Step 5: Test their scanner against a known-broken page. Most vendors offer a free scan. Run it on your product page. Then run the same page through WAVE and axe DevTools. Compare. If the vendor’s scanner finds way fewer issues, it is being optimistic. If it finds way more, it is padding the report.

Step 6: Confirm the fixes survive without the plugin loaded. Or at least understand they will not. Some fixers store the fix in the post meta (good, portable). Others inject CSS/JS at runtime (fine while installed, breaks if you remove it).

Step 7: Get the compliance report. A real fixer provides a PDF report showing what was scanned, what was fixed, and what remains. You want this for your legal file in case of a demand letter.

More depth on the buying decision is in our Best WordPress Accessibility Plugin for WooCommerce (2026) comparison.

A realistic implementation workflow

Here is what installing and running an accessibility plugin actually looks like on a WooCommerce store with 200 products.

  1. Backup first. Full site + database. Accessibility plugins modify markup; if anything goes sideways with your theme you want a rollback.
  2. Install on staging. Not production. Push to a staging URL or a local copy first.
  3. Run the initial scan. Expect 50 to 300 issues for a typical store. Most are repeated across templates (one bad button shown on 200 product pages counts 200 times).
  4. Apply automatic fixes. Alt text, ARIA labels, focus indicators, lang attribute, skip links. These are safe defaults.
  5. Review the manual-flag list. Product alt text usually needs your eyes. “image1.jpg” auto-set to “Red leather wallet” is fine. “product photo” is not.
  6. Test the checkout flow keyboard-only. Tab through cart, billing, shipping, payment. Every field must be reachable, focus must be visible, and you must be able to submit without a mouse. This is the #1 lawsuit trigger.
  7. Test with a screen reader. Spend 15 minutes with VoiceOver or NVDA on your homepage, a product page, cart, checkout. You will notice things scanners miss.
  8. Publish to production. Re-scan weekly. New products, new blog posts, theme updates all introduce new failures.
  9. Generate your compliance report. Save it. Date it. If you get a demand letter, this is your evidence of good-faith effort.
  10. Write your accessibility statement. Most plugins generate one. Link it in your footer.

A fuller version of this workflow is in How to Make Your WooCommerce Store ADA Compliant.

How AmazingPlugins helps

The WooCommerce Accessibility Fixer is a WordPress plugin specifically for WooCommerce stores. It uses WordPress hooks and WooCommerce template filters, so the fixes are baked into your rendered HTML, not painted on top by JavaScript.

What it handles automatically:

  • Alt text on product images (auto-generated from product title for missing ones, flagged for review when generic).
  • Keyboard navigation across cart, mini-cart, variation forms, checkout.
  • Visible focus indicators that survive theme outline: none rules.
  • ARIA form labels on every WooCommerce billing/shipping/payment field.
  • Color contrast adjustments for body text and primary buttons (with theme-safe overrides).
  • Skip links to main content and to footer.
  • Empty button text fixes (icon buttons get accessible names).
  • lang attribute on <html>.
  • Link distinguishing text (no underline-only color cues).
  • Accessible input names for search, filter, and quantity inputs.

The Pro tier adds batch scanning across your entire catalog, an auto-fix mode that applies safe fixes in bulk, a PDF compliance report you can hand to your lawyer, and priority support.

What it does not do: write meaningful alt text for product photos that need human judgment, restructure a poorly built custom theme, or fix accessibility problems in third-party page builders we cannot template-override. It flags those for you.

People also ask

Are accessibility plugins legally required?

No plugin is required by law. WCAG compliance is. Title III of the ADA applies to e-commerce sites in the US (settled case law), and the EAA requires WCAG 2.1 AA compliance for stores selling to EU consumers as of June 28, 2025. A plugin is the cheapest way to get most of the way there. You can also hire an accessibility consultant for $5,000 to $25,000 to do it manually. Most stores combine both: plugin for ongoing maintenance, consultant for the initial audit.

Do free accessibility plugins work?

For scanning, yes. WAVE and the WordPress.org repo have decent free scanners. For automatic fixing, mostly no. Free fixer plugins typically handle 3 to 5 of the easy criteria (lang attribute, skip links, basic ARIA) and leave the rest. If your budget is zero and your store does under $50K/year, start with a free scanner and fix issues manually. If you do more than that, the legal exposure (average ADA lawsuit settlement: $25K) makes a $20/month plugin obvious math.

Will an accessibility plugin slow down my WooCommerce store?

A WordPress-native plugin adds a few KB of CSS and minimal PHP overhead per request, typically under 50ms. Overlay widgets are different: they load 200KB+ of JavaScript, often render-blocking, and frequently tank Core Web Vitals. If you check your LCP score before and after installing an overlay, you will see the damage.

Does an accessibility plugin protect me from ADA lawsuits?

It reduces your risk significantly but does not eliminate it. A real code-level plugin combined with an accessibility statement, manual review of judgment-based criteria, and ongoing monitoring is the realistic recipe for not getting sued. Overlay-only plugins do not protect you. Plaintiffs’ law firms specifically target sites running overlay widgets because the underlying code is still broken.

What is the difference between an accessibility plugin and an accessibility audit?

A plugin is software that scans and fixes automatically. An audit is a human (usually a certified accessibility specialist) manually testing your site against WCAG with assistive tech, producing a remediation report. Audits cost $3K to $25K and catch things plugins cannot (content order, plain language, custom widget logic). Most serious stores do an audit once a year and run a plugin continuously between audits.

Can I install multiple accessibility plugins?

Not recommended. Two fixer plugins will fight over the same hooks, add duplicate ARIA labels, or override each other’s CSS. Pick one fixer. You can run multiple scanners (WAVE + axe + your plugin’s built-in scan) since scanners only read, they do not write.

The honest bottom line

A website accessibility plugin is not a compliance silver bullet, but it is the highest-leverage hour of work you can put into your WooCommerce store right now. Real fixer plugins handle roughly 40 to 60% of WCAG criteria automatically. Combined with an accessibility statement, a manual review of your top 10 pages, and a yearly audit, you are doing more than 95% of e-commerce stores. That is the practical definition of “reasonable accommodation” under the ADA.

For a deeper walkthrough of the compliance side specifically, see the ADA Compliance Plugin for WooCommerce Full 2026 Guide.