Boutique Owners: The 6 Checkout Bugs That Trigger Screen-Reader Demand Letters (And How to Kill Them)

You built your shop to sell the pieces you love — the vintage denim, the small-batch candles, the earrings your customers text photos of to their friends. What you did not sign up for was a certified letter from a law firm demanding money because a blind shopper couldn't finish checkout on your site.

Here's the honest part: those letters aren't random, and they aren't (usually) a scam. Firms run automated scans and hire real screen-reader testers to hunt for stores with broken accessibility. Boutiques get hit because your checkout is a maze of custom buttons, variant pickers, quantity steppers, and coupon fields — exactly the stuff that breaks for a screen reader. The good news? Most of the damage comes down to a short list of code bugs you can actually fix.

We're a web + accessibility shop, not a law firm — so this isn't legal advice. But we fix this real code every week, and here's where the trouble hides.

The 6 bugs testers hit on boutique checkouts

1. The "Add to Cart" button that isn't really a button

A lot of custom themes fake buttons with a styled <div> or <span>. Looks fine to you. To a screen reader, it's silent — the shopper literally can't tell there's anything clickable there. Real <button> or <a> elements announce themselves. Fake ones don't.

2. Size and color swatches with no labels

Those pretty little color circles and size boxes? If they're coded as unlabeled tiles, a screen reader reads "button, button, button" with no idea which is Small and which is Sage Green. The shopper can't pick a variant, so they can't buy. This is the single most common boutique-specific failure we see.

3. Form fields with placeholder text instead of labels

Faint gray "Email address" text inside the box disappears the moment someone types — and screen readers often skip placeholders entirely. Every field (email, address, card number, coupon) needs a real, connected <label>. Without it, the shopper hears "edit text, blank" and has no clue what to enter.

4. Error messages that only show up in red

You forgot your ZIP, the field turns red — great, if you can see. Screen-reader users hear nothing. Errors need to be announced (an ARIA live region) and described in words, not just color. "Invalid" in red pixels is invisible to the exact person who filed the letter.

5. A pop-up cart or discount modal that traps focus — or loses it

When your cart slides out or a "10% off your first order" modal appears, keyboard and screen-reader focus should move into it and be trapped there until it's closed. Broken modals dump the shopper back at the top of the page or trap them with no way to escape. Instant dead end.

6. Payment buttons inside an iframe with no accessible name

The Shop Pay, Apple Pay, or third-party checkout button often lives in an iframe. If it's unlabeled or hidden from assistive tech, the shopper reaches the last step and simply can't finish. That final-inch failure is catnip for a demand letter, because the tester can document that the sale was impossible.

How to check your own store this week

• Unplug your mouse. Tab through your whole checkout using only the keyboard. Can you reach and activate every field and button? Can you close the cart drawer?
• Turn on a screen reader. VoiceOver is built into Mac (Cmd+F5); NVDA is a free download for Windows. Try to buy one item start to finish with your eyes closed. If you can't, neither can your customer.
• Test swatches specifically. Can you tell which size and color you're selecting by sound alone?

Why widgets won't save you

You'll see ads for an "accessibility widget" — one line of code, instant compliance, $49/month. Skip it. Those overlays don't fix your underlying HTML, screen-reader users have publicly complained they make things worse, and plenty of demand letters have named sites running a widget. We don't sell band-aids. We fix the actual code so your checkout works for real people using real assistive tech.

Fixing these six things does two jobs at once: it takes you off the easy-target list, and it opens your store to shoppers who were quietly leaving because they couldn't buy.

Want to know which of these your store is failing right now? Grab a free accessibility scan at rankrebels.ai/accessibility — we'll show you exactly where your checkout breaks, in plain English, no scare tactics.