Got an ADA demand letter for your WooCommerce store? Here’s what to do

If you just received an ADA demand letter about your WooCommerce store, here is the whole answer in one breath: do not ignore it, do not sign or pay anything, send the letter to your own attorney, preserve a dated record of your site exactly as it is today, and start fixing the real accessibility defects in your site’s code with dated documentation of every fix. The letter itself is a legal matter and belongs with a lawyer. The website is a technical matter, and it can be repaired and documented starting this week. According to public litigation trackers, most single-plaintiff web accessibility claims settle in the $5,000 to $20,000 range, and the condition of your site while those conversations happen is one of the few things you actually control.

You are not alone in this. Seyfarth Shaw’s tracking at adatitleiii.com counted 8,667 ADA Title III federal lawsuits in 2025, and demand letters, which never reach a courthouse docket, are widely understood to outnumber the filed cases. This is a volume business for the firms that send these letters. That does not make your letter less real. It means there is a well-worn path for dealing with it, and you are about to walk it with a map.

The first 48 hours: five steps

1. Do not ignore the letter

The single worst move is putting it in a drawer. Demand letters typically carry a response deadline, and if the sender files suit and you never respond, you risk a default judgment, which is the most expensive possible outcome of a process that usually settles for far less. Whatever you decide to do, decide it on purpose and on time.

2. Do not sign anything, pay anything, or reply to the sender yourself

The letter may include a settlement figure, a prewritten agreement, or a number to contact. Do not engage with any of it directly. Anything you say or write to the plaintiff’s firm can shape the negotiation, and you would be negotiating against people who do this every day. Silence toward them, for now, is not ignoring the letter. It is holding your position until your own counsel speaks for you.

3. Send the letter to your own attorney

This is the step everything else hangs on. Fix47 is not a law firm, and this page is not legal advice. The demand letter, the deadlines, the settlement talks, and any agreement you eventually sign are attorney territory, full stop. If you do not have a lawyer, look for a defense attorney with ADA Title III or web accessibility experience; many offer a short initial consultation. Forward them the letter, the envelope or email it arrived in, and the date you received it. A letter that costs you a few hundred dollars of attorney time to handle correctly is a bargain against a negotiation handled badly.

4. Preserve a dated record of your site as it is today

Before you change anything, capture the current state: dated screenshots of your homepage, product pages, cart, and checkout, plus a dated accessibility scan of the site as it stands. This matters for two reasons. Your attorney needs to know what the plaintiff’s expert actually saw, and once remediation starts, you want a clear before-and-after trail showing exactly what was broken, what was fixed, and when. A free scan that produces a dated score is a reasonable first artifact; a fuller evidence report comes with the remediation work itself.

5. Get the site actually fixed, in the code, with documentation

This is the part that is ours, and it is the part that changes your position. Whatever your attorney negotiates, the underlying question in every web accessibility claim is whether the site works for disabled users. A site that has been repaired at the code level, with dated evidence reports documenting each fix, is a materially different conversation than a site that is still broken. And note the word “code”: in 2025 the FTC ordered accessiBe, the largest overlay widget vendor, to pay $1 million over deceptive claims about what its AI widget could achieve, and UsableNet’s 2025 Midyear Report found that 22.6% of accessibility suits filed in the first half of 2025 targeted sites that already had a widget installed. Pasting a widget into your store after receiving a demand letter is not a fix. It is a documented non-fix.

Why WooCommerce stores get targeted

WooCommerce runs a huge share of small and mid-size e-commerce, and the way most stores are built creates a predictable set of WCAG failures. These are the ones we find over and over on Woo sites:

• Unlabeled icon buttons.The cart icon, the search magnifier, the quantity plus and minus, the wishlist heart. To a sighted user they are obvious. To a screen reader without an accessible name, each one announces as “button”, which means a blind user cannot tell the add-to-cart from the remove.
• Low-contrast theme text. Popular theme defaults ship gray-on-white body text and pale placeholder text in form fields that fail the WCAG contrast minimums out of the box, and every product description inherits the failure.
• Keyboard traps in off-canvas carts, popups, and galleries. The slide-out mini cart, the newsletter modal, the product image lightbox. These are built for mouse users. A keyboard user tabs in and cannot tab out, which is a failure of WCAG 2.1.2 (No Keyboard Trap), a Level A criterion, the most basic tier of the standard.
• Checkout forms without proper labels and error announcement. Fields identified only by placeholder text, and validation errors that appear visually but are never announced to assistive technology, so a screen reader user has no idea why the order will not go through.
• Carousels and variation swatches that only work with a mouse. Color and size pickers built as clickable divs, unreachable and unusable by keyboard.

Here is the strategic point: the checkout is where litigation looks. An ADA Title III web claim is, at its core, an allegation that a disabled customer was denied access to your goods and services. The strongest version of that allegation is “I tried to buy and could not complete the purchase.” That makes your product page, cart, and checkout the highest-stakes screens on your site, and on WooCommerce they are exactly where themes, payment plugins, and shipping calculators pile on the most third-party code.

One more thing worth knowing before you trust a clean automated report. A site we scanned in July 2026 scored 94 out of 100 with zero axe-core violations, the same engine most free checkers run. Keyboard-path testing, the interaction layer our scanner runs, still found a focus trap, a WCAG 2.1.2 Level A failure that only exists once someone starts interacting with the page. Automated scanners test the page standing still. Plaintiffs’ experts test it by hand. Your remediation has to hold up to the second test, not the first.

What “fixing it” actually means

Fixing it means the defects stop existing in your site’s code, not that a script paints over them in the visitor’s browser. In practice, on a WooCommerce store, that looks like this:

1. A full audit that goes beyond automated scanning.Automated engines plus manual keyboard-path testing of the exact journeys a plaintiff’s expert would walk: find a product, add to cart, check out.
2. Fixes written into the theme and templates. Accessible names on the icon buttons, contrast corrected at the source, focus management added to the mini cart and modals, labels and error announcement wired into checkout fields. When the work is done, the accessible version of your store is the only version. Nothing to load, nothing to toggle, nothing that vanishes if a third-party script fails.
3. Dated evidence reports. A document trail recording what was found, what was fixed, and when, with before-and-after scores. This is the artifact your attorney can actually use: not a badge, not a toolbar, a dated record of remediation.
4. Monthly rescans. Stores change constantly. New products, new plugins, theme updates. Monthly verification catches regressions before they accumulate, and each rescan extends the dated record.

This is what Fix47 does. The brand descriptor is exactly what it sounds like: ADA Website Remediation. One public example of the end state: Pinsilike, a WordPress e-commerce site, went from 73 violations to zero, verified monthly since.

One honest limit, stated plainly: no vendor can promise the demand letter goes away, and no one can promise you will never receive another. Anyone can send a letter to anyone. What remediation changes is the substance underneath the claim, and the substance is the only part of this that is fully in your hands.

Frequently asked questions

Related reading: Does an accessibility widget stop ADA lawsuits? · accessiBe alternative: widget vs real code remediation