Boutique & Online Shop Owners: The 6 Checkout Fields a Screen Reader Can't Read (and Why That's a Demand-Letter Magnet)
You run a boutique with an online store. You've got the brand, the product photos, the loyal regulars who DM you asking if that dress comes in sage. And somewhere in your inbox — or your competitor's — sits a demand letter that opens with a line like: "Our client, who is blind and uses a screen reader, was unable to complete a purchase on your website."
Here's the uncomfortable part: it's almost never the pretty homepage that gets flagged. It's the checkout. That's where money changes hands, and that's exactly where a plaintiff's tester (or their software) goes to prove someone couldn't buy from you. Let's walk through the six spots that most often break on a Shopify, WooCommerce, Squarespace, or Wix store — in plain English, no legal fear-mongering.
1. The "Add to Cart" button that announces nothing
A screen reader reads what's in the code, not what your eyes see. A lot of theme buttons are built as a styled div or an icon with no text label. So instead of hearing "Add to Cart," a blind shopper hears "button" — or nothing at all. If they can't tell what the button does, they can't start checkout. Fix: make sure the button is a real <button> with readable text or an aria-label.
2. Variant selectors (size/color) with no labels
Boutiques live and die by variants. But those swatches and dropdowns are often coded as clickable squares with no connection to a label. The shopper hears "button, button, button" and has no idea which one is "Small / Rose." Every size and color option needs an associated label the screen reader can announce — and the selected state needs to be communicated too.
3. Form fields where the label floats but isn't connected
That modern "floating label" look — where "Email" sits inside the box until you click? Gorgeous. Also a common break point. If the label isn't tied to the input with a for/id pairing, the screen reader reads an empty text box. The shopper doesn't know if they're typing their email, name, or zip. On a checkout form, that's a dead end.
4. Error messages that appear in color only
Someone fat-fingers their card number. Your form turns the field red and shows a little message. A sighted person sees it instantly. A screen-reader user? If that error isn't announced through an aria-live region or tied to the field, they have no idea anything went wrong. They just sit there wondering why "Place Order" won't work. This single gap is quoted in demand letters constantly.
5. The coupon code and quantity steppers
Those plus/minus quantity buttons and the "Apply Code" field feel minor — until they're unlabeled and un-reachable by keyboard. A screen-reader user navigates with the keyboard, not a mouse. If they can't tab to the quantity button or the code field, they literally can't adjust their order. Test it yourself: unplug your mouse and try to buy something.
6. The payment iframe and pop-up modals
Your payment gateway or an "Are you sure?" modal often loads in a window that traps or loses keyboard focus. The shopper tabs into a void, or gets stuck behind the pop-up with no way out. Focus management inside checkout modals is technical, but it's one of the most-cited failure points — because it's the last step before the sale.
Why widgets don't save you here
You've probably seen those "accessibility" overlay widgets that promise one line of code fixes everything. They don't — and courts and advocates have publicly said so. An overlay can't label your variant swatches or fix a broken checkout form; those live in your theme's actual code. We fix the real code. (And to be clear: we're an agency, not a law firm — we make your site genuinely usable, not paper over it.)
Run the 5-minute test tonight
- Turn on VoiceOver (Mac: Cmd+F5) or NVDA (free on Windows).
- Put a product in your cart using only the keyboard.
- Go through checkout. Can you tell what every field is?
- Trigger an error on purpose. Do you hear it?
If you got stuck anywhere, so does every blind shopper trying to spend money with you — and so does the tester looking for a reason to write a letter. Fixing this doesn't just keep you out of trouble; it opens your store to customers who were quietly getting locked out.
Want to know exactly where your checkout breaks? Grab a free accessibility scan at rankrebels.ai/accessibility — we'll show you the real code issues, in plain English, so you can get found, get the sale, and sleep better.
Want this done for you?
Rank Rebels builds fast websites and gets local businesses found on Google and AI search.
Get a free audit →