WooCommerce
Accessibility fixes for WooCommerce stores, from home page to checkout.
On WooCommerce you own the whole stack: theme, page builder, plugins and checkout. That means more places for barriers to hide, and it also means all of them can be fixed.
Where WooCommerce stores usually fail
| Where it shows up | What fails | WCAG |
|---|---|---|
| Page builder layouts | Headings chosen for size rather than structure; buttons built from divs that a keyboard can't reach | 1.3.1, 2.1.1 |
| Variation dropdowns and swatches | Options with no accessible name; price change not announced | 4.1.2, 4.1.3 |
| Quantity fields and coupon box | Inputs with placeholder text but no label | 3.3.2, 1.3.1 |
| Checkout errors | Error messages shown in red only, not announced or tied to the field | 3.3.1, 1.4.1 |
| Mini-cart and AJAX add-to-cart | Cart updates without telling a screen-reader user anything happened | 4.1.3 |
| Sliders and testimonial carousels | Auto-rotating, no pause, not keyboard-operable | 2.2.2, 2.1.1 |
| CAPTCHA on forms | A challenge with no accessible alternative | 1.1.1 |
| Theme colours | Contrast below 4.5:1 on body text, buttons and links | 1.4.3 |
How we work on a WooCommerce store
- A staging copy. We work on a staging site your host creates, or one we set up for you, so the live store keeps trading.
- A child theme, so our fixes survive your parent theme's updates. Plugin output is corrected through hooks and templates, not by editing plugin files that the next update would overwrite.
- Limited access: a WordPress account on staging and file access there. We don't need production admin rights or payment-gateway credentials.
- Verification of the full purchase path, including checkout, with keyboard only, NVDA on Windows and VoiceOver on Mac and iPhone.
- Deployment and report: you or your host push staging to live, you get the before-and-after report, and monitoring starts.
Plugins and page builders
Most WooCommerce failures come from plugins and builders rather than WooCommerce itself. We fix what can be fixed from the theme and plugin settings. Where a plugin's output can't be corrected safely, the report names the plugin, the failure, and what to ask its developer for, or suggests an accessible replacement.
Unlike hosted platforms, your checkout is part of your site, so it is fully in scope.
Price
| Service | Scope | Price |
|---|---|---|
| Scan | Automated WCAG 2.2 AA scan of key templates, plain-English report, fixed quote | Free |
| Remediation · Standard | Up to 50 products on a stock or lightly customized theme | $4,900 |
| Remediation · Extended | Up to 500 products, a customized theme, or third-party add-ons in the purchase path | $7,900 |
| Attorney response package | Statement of work, before-and-after findings and verification log, formatted for counsel | $1,500 |
| Monitoring | Monthly re-scans and change alerts; first three months included | $149/mo |
Larger catalogs and headless storefronts are quoted from the scan.
Get a free scan of your store
A WCAG 2.2 AA scan of your key templates, each failure mapped to the part of your theme it lives in, with a fixed quote. Usually within one business day. Nobody calls you.
What we don't promise. We are engineers, not lawyers, and nothing here is legal advice. No vendor can certify a store as "ADA compliant"; there is no certifying body. We remove the barriers, verify that a keyboard and screen-reader user can complete a purchase, and document the work so your attorney can use it.
Questions
Will plugin or theme updates undo the fixes?
Fixes live in a child theme and in hooks, which updates don't overwrite. Monitoring re-scans monthly and after changes, so a regression from an update gets caught.
We built the site with Elementor (or Divi). Is that a problem?
No, but builder pages usually need more attention to headings and buttons. The scan shows how much, and the quote reflects it.
Do you need our hosting login?
Only access to a staging copy. If your host can't make one, we'll tell you the simplest way to set it up.