A WooCommerce accessibility plugin can find some barriers and change some page output. It cannot certify your store under the ADA. The test is whether someone can find a product, choose options, add it to the cart, check out, and get help using a keyboard or assistive technology.

This guide was reviewed on September 28, 2026. It explains how to choose and check a plugin. For dates and legal scope, see our WCAG deadline guide.

What the law says, and what it doesn’t

The U.S. Department of Justice says the ADA applies to goods and services that businesses open to the public offer on the web. Its Title III guidance does not set a detailed website technical standard for private businesses. WCAG is useful technical guidance, but calling WCAG 2.1 AA a universal legal floor for every private store overstates the rule. The DOJ’s separate Title II web rule covers state and local governments, not ordinary private stores.

The European Accessibility Act covers specified consumer services, including ecommerce services provided after June 28, 2025. Its scope, exceptions, and enforcement depend on the directive and applicable national law. An EU visitor alone does not settle whether your store is covered. If you need a legal answer for your business, ask a qualified adviser.

For engineering work, WCAG 2.2 is a sensible target. It builds on 2.1 and adds checks relevant to store controls and account access. Meeting a checklist on one page still doesn’t establish conformance across a whole purchase process.

What to ask before installing a plugin

Ask the vendor to show you exactly which pages it scans and which rendered elements it changes. “Works with WooCommerce” could mean a few selectors on standard templates. It does not prove support for your theme, checkout extension, payment iframe, or product configurator.

Check these points on a staging copy of your store:

  • Scan coverage: Are shop, product, cart, account, and checkout included? Does it inspect every product, or only a sample? Which checks are actually implemented?
  • Fix scope: Is a change in saved content, rendered HTML, CSS, or browser-side JavaScript? Can you inspect and reverse it?
  • Human review: Can you correct a suggested image description or reject a change that alters the meaning of a control?
  • Reports: Does the export contain the tested URLs, date, findings, and unresolved issues? A report records a scan; it is not proof of ADA compliance.
  • Maintenance: Can you repeat the check after theme, WooCommerce, payment, and catalog updates?

The FTC’s 2025 final order against accessiBe addressed unsupported claims that an automated product could make any website WCAG compliant. It did not declare every overlay unlawful or decide whether every site using one violates the ADA. Treat any one-click compliance promise with the same skepticism, whether it comes from an overlay or a WordPress plugin.

Test the store before and after a fix

Start with one representative page of each type: shop, simple product, variable product, cart, account sign-in, and checkout. Include any third-party payment or shipping step. An automated checker can identify candidates such as missing accessible names, some contrast problems, and absent image alternatives. The DOJ warns that a clean automated report does not mean a page is accessible.

Then use the store:

  1. Complete a purchase path with a keyboard. Watch focus in menus, variation pickers, dialogs, cart drawers, and payment fields.
  2. Repeat with a screen reader. Check control names, price and stock changes, errors, and order confirmation.
  3. Review product images in context. A product title copied into alt may omit the detail that distinguishes a variation. Decorative images may need an empty alt instead.
  4. Measure text contrast against the actual rendered background. A focus outline style does not repair every text color.
  5. Record each issue with its URL, browser, steps to reproduce, owner, and retest result.

Install changes on staging first. Compare the rendered output before and after each fix. Retest the full flow when it goes live, then after substantial theme or checkout changes. Keep dated findings and retest notes because they help your team track what was fixed and what remains. Don’t describe them as a legal shield.

Where our plugin fits

Disclosure: AmazingPlugins publishes AP Accessibility Fixer for WooCommerce. We reviewed the public WordPress.org 1.5.1 release and its code on September 28, 2026. It is free, with no Pro tier or scan quota.

The release scans configured WooCommerce pages, the front page when distinct, and up to three randomly selected published product pages per run. Its scanner uses a limited set of HTML checks. It is not a full WCAG audit or a catalog-wide scan. Its nine fixers include a product-image alt fallback, a skip link, selected focus and error styles, and form-label changes in content processed by WordPress’s the_content filter. Some changes use inline JavaScript. The color-contrast fixer styles certain focus and error states; it does not measure and repair arbitrary text contrast. The form-label fixer does not establish blanket coverage of checkout templates.

The admin has a scan report and a downloadable, print-friendly HTML report. The public report controller serves an .html attachment, so we would not promise a PDF export. Test each fix against your theme and checkout before relying on it. The plugin cannot write meaningful alt text, resolve every keyboard interaction, or guarantee conformance.

Questions worth asking a vendor

Can a plugin prevent an ADA claim?

No vendor can promise that. A tool may remove a specific barrier on your site. Verify the result with users and manual testing, and get legal advice if you need an assessment of exposure.

Should I avoid all browser-side fixes?

No. The method matters less than whether the resulting experience works. A script can add a useful skip link; a script can also break keyboard behavior. Inspect the result and test it. The FTC order concerns unsupported compliance claims, not a blanket ban on JavaScript.

Do I need a paid plugin or an audit?

Choose based on the gaps you find, your store’s complexity, and your team’s ability to test them. There is no defensible universal price, remediation percentage, or product-count cutoff. A custom checkout or payment flow often needs specialist review because a generic plugin cannot see every state.