Your Lighthouse accessibility score says 87. You think you’re covered. You’re not.
Lighthouse catches roughly 30% of real accessibility failures. The failures it misses live in your cart drawer, checkout form fields, and Add to Cart button flow. ADA demand letters target exactly those failures.
Most e-commerce accessibility checklists for small businesses give you 40 WCAG items with no platform context. This e-commerce accessibility checklist gives you four specific fixes for the failures most likely to cause checkout abandonment and legal exposure. You can complete all four in Shopify or WooCommerce this afternoon, without a developer.
What’s the legal risk of an inaccessible e-commerce store — and how real is it for a store my size?
ADA demand letters targeting e-commerce stores are common now — small stores included. In 2023, plaintiffs filed over 4,600 federal accessibility lawsuits, a record. Settlements for small operators run $5,000–$25,000 plus remediation costs.
Letters typically arrive before any lawsuit. Your revenue range is exactly the zone opportunistic plaintiffs target.
The law that applies to you is the Americans with Disabilities Act, Title III. Courts increasingly interpret it to cover online stores. Boutique DTC brands, niche supplement stores, and handmade goods shops have all received letters.
The disabled consumer market is not a rounding error. Americans with disabilities hold an estimated $490 billion in annual disposable income. Checkout abandonment by screen reader users represents real lost revenue — not just a compliance checkbox.
WCAG compliance for small businesses does not require a full audit firm or legal team. See [link: Shopify checkout conversion guide on bizlegos.com] for how these same fixes overlap with standard checkout conversion improvements.
Why does a Lighthouse score above 80 not mean my store is compliant?
Lighthouse catches roughly 30% of actual accessibility failures. It checks things it can measure automatically: missing alt attributes, low contrast ratios, absent document language declarations. It cannot test keyboard flow logic or focus trap behavior in cart modals.
It also can’t tell you whether checkout error messages communicate anything useful to a screen reader user. That gap is where demand letters come from.
What most store owners do — and what it costs
Most owners run a Lighthouse audit, see a score in the 80s, and stop there. That’s the mistake.
A WooCommerce kitchenware store doing $65k/month scored 84 on Lighthouse and assumed they were fine. Six months later, an axe DevTools scan on their checkout page surfaced 11 critical failures — none flagged by Lighthouse. Three were inside the payment form.
Mobile screen reader abandonment showed up nowhere in their analytics. They had no way to segment for assistive technology traffic. The lost revenue was completely silent.
The 20% move that actually works: run axe DevTools on your product page and your checkout page. Fix every "Critical" flagged item before touching anything else. These failures appear in demand letters and cause silent checkout abandonment.
How do I test my e-commerce site for accessibility issues without hiring expensive consultants?
Three free accessibility audit tools cover 80% of what a small store needs. Accessibility testing without consultants is feasible using axe DevTools (free Chrome extension), which finds critical technical failures automatically, and WAVE (free, browser-based at wave.webaim.org), which gives a visual overlay of errors on any live page.
Chrome’s built-in Tab key tests keyboard navigation in under 10 minutes. Start with these three before spending a dollar.
The tool sequence that works
Install axe DevTools from the Chrome Web Store. Open your product page. Click the axe icon in Chrome DevTools and run the scan.
Issues sort by impact level. Ignore "Best Practice" and "Minor" for now. Work through "Critical" and "Serious" only — that’s your real to-do list.
Then go to wave.webaim.org. Enter your checkout URL. Red icons are errors.
Orange icons are alerts. Fix red first.
A Shopify home goods store doing $28k/month ran this two-tool audit in 90 minutes. They found 7 critical errors — all on product and checkout pages. None had shown up in their Lighthouse scan.
They fixed 5 of those errors the same afternoon using Shopify’s theme editor and the free Accessible app from the Shopify App Store.
Manual keyboard test: 8 minutes, no tools required
Close your mouse. Open your homepage. Press Tab.
Watch where focus goes. You should see a visible outline moving from element to element. If it disappears — especially near the cart drawer or header navigation — that’s a failure.
Try adding a product to cart using only Tab and Enter. Then attempt to reach checkout without touching the mouse. Mark every point where you lose focus or get stuck.
That’s where keyboard-only users abandon.
What belongs on an e-commerce accessibility checklist for Shopify and WooCommerce this week?
Four fixes cover the highest-risk failures for most small stores: descriptive alt text, explicit form labels, clear error messages, and keyboard access to the Add to Cart button. These changes reduce legal exposure and recover checkout sessions from assistive technology users.
Fix 1: Alt text on product images
Every product image needs a descriptive alt attribute. "Red leather wallet with multiple card slots and zip compartment" works. "wallet" does not.
Empty alt text (alt="") is correct only for purely decorative images — not for product photos.
In Shopify: go to Products > [product name] > click the image > edit the alt text field directly. In WooCommerce: go to Products > [product] > Product Gallery > click the image > update "Alternative Text" in the media library panel.
A Shopify apparel store doing $55k/month found 340 product images with missing or one-word alt text. After a bulk update using a free alt text app, organic image search traffic rose 9% over 60 days. The accessibility fix doubled as an SEO fix.
Descriptive alt text also lifts organic image search traffic — see [link: product image SEO guide on bizlegos.com] for the full strategy.
Fix 2: Form labels in checkout
Every input field in your checkout needs an explicit <label> tag with a for attribute that matches the input’s id. Placeholder text does not count as a label. Screen readers stop announcing placeholder text once a field is focused.
In WooCommerce, check your woocommerce/templates/checkout/form-billing.php file. Each input needs a structure like <label for="billing_first_name">First name</label>. If your theme uses floating labels, test them with NVDA or VoiceOver to confirm they announce field names correctly.
In Shopify, checkout form labels live in your theme’s Liquid templates. Shopify Plus stores can edit checkout.liquid directly. For standard Shopify plans, most free accessibility apps handle common label issues.
Fix 3: Error messages that explain the problem
"Invalid input" tells a screen reader user nothing. "Please enter a valid email address, for example name@domain.com" tells them exactly what to do.
Every checkout error message needs two things: the specific field with the problem, and the specific correction. ARIA live regions announce these messages to screen readers when they appear — but only when coded correctly. Test this by triggering a form error while using VoiceOver or NVDA and listening for the announcement.
Fix 4: Keyboard access to Add to Cart
Press Tab from your product page until you reach the Add to Cart button. Press Enter. If nothing happens, the button is broken for keyboard users.
This is the single most common critical failure in Shopify stores using custom themes. The fix is usually one line of CSS or a missing type="submit" attribute on the button element. Check the rendered HTML in DevTools.
If your button is a <div> instead of a <button>, that’s the problem.
What should I expect after fixing these issues — and how long does it take?
Most stores complete all four critical fixes in one afternoon without developer help. Legal exposure drops immediately once documented failures are resolved and recorded. Checkout completion rate recovery from the affected user segment typically runs 5–15%.
A realistic timeline
Day 1 (2–3 hours): Run axe DevTools and WAVE on your product page and checkout. Screenshot or export every critical failure. This is your audit record.
Days 2–5 (1–2 hours per day): Fix alt text, form labels, and error messages. Test with keyboard navigation after each change. Use NVDA (free, Windows) or VoiceOver (built-in, Mac) to verify the checkout flow end-to-end.
Week 2: Fix focus indicators and test your Add to Cart button across devices. Test mobile separately — iOS and Android handle keyboard focus differently.
Month 2: Run a second axe scan to confirm all critical failures are cleared. Set a quarterly calendar reminder to recheck after any theme update or new app installation. New apps frequently introduce new failures.
A WooCommerce supplement store doing $42k/month ran this process in 9 days using one team member with no developer background. They cleared all critical failures on product and checkout pages. Over the following month, three customers emailed to say they had previously been unable to complete checkout — and now could.
What to document
Record your audit date, the tool used, the failures found, and the fixes applied. This documentation matters if a demand letter arrives. Demonstrating good-faith remediation effort changes the legal conversation significantly.
The stores most at risk from accessibility complaints are the ones that have done just enough to feel safe. A Lighthouse score above 80 creates false confidence. Those failures live in keyboard flows and form fields that automated scanners cannot reach.
You don’t need to fix everything this month. Complete your e-commerce accessibility checklist: fix the four critical failures on your product and checkout pages. Run the two free scans this week.
Set a quarterly reminder to repeat the audit after every major theme change. That covers your legal exposure and recovers real checkout sessions — no consultant, no developer, no WCAG docs required.