What should a Shopify brand do when a customer complains the store is not accessible?
An accessibility complaint is a customer telling you, for free, that something on your store is broken. Respond within a day, reproduce exactly what they could not do, fix it, tell them what changed, and then turn the incident into a monitoring rule so the same barrier never ships again.
Respond within a day, even before you have a fix
The worst response to an accessibility complaint is silence, because silence is what turns a frustrated customer into a demand letter. Acknowledge the complaint within 24 hours: thank them for reporting it, tell them you take it seriously, and give a realistic timeline for an update. You do not need to admit fault or quote legal standards. You need to show a human read the message and something is happening.
Route the complaint to whoever owns the storefront, not just support. Support can acknowledge, but the fix lives with the person who controls the theme and the apps. A complaint that sits in a support queue for two weeks reads as indifference to the person who filed it, and indifference is what gets screenshot and forwarded.
Reproduce the exact barrier, on the live store
Ask what the customer was trying to do and with what technology, then recreate it. Common complaints: the checkout form error that screen readers never announce, the size selector that only works with a mouse, the discount code field with no label, the carousel that traps keyboard focus. Test it on the live store with the same conditions, because staging often runs older code and the barrier may already differ.
Write down the reproduction steps while you do it. This record becomes the test case for the fix, and later the regression check. If the complaint turns out to be a misunderstanding, the notes still document that you investigated in good faith, which matters if the same customer escalates.
Fix the barrier, then check the whole template
Fix the specific barrier first, fast. Then scan the template it lives on for the same class of issue, because accessibility defects travel in families. A missing label on the discount field usually means missing labels on other fields in the same form. A keyboard trap in one popup usually means the same popup pattern elsewhere traps too. Fixing one instance while leaving five siblings is how a brand gets a second complaint a month later about the same problem.
Deploy the fix and re-test with the same reproduction steps. Then run your automated scan on the changed templates and diff against baseline, so you confirm the fix did not introduce something new. This is the moment monitoring earns its keep: the alert that would have caught this barrier before a customer did should exist from now on.
Tell the customer what changed
Close the loop. Email the customer, describe what you fixed in plain language, and thank them again. This does two things: it converts a critic into an ally, and it creates a dated record that the brand acted on the complaint promptly. If the customer uses assistive technology, offer to have them confirm the fix works on their end. A customer who feels heard rarely becomes a plaintiff.
Keep the exchange filed with the date, the barrier, the fix, and the deploy date. If a demand letter ever references the same issue, this file shows the timeline of good-faith remediation, which is the strongest position a brand can be in.
Turn the incident into a permanent monitoring rule
Every complaint is a signal your monitoring missed something. Ask why. Was the template excluded from scans? Was the barrier in an app iframe the scanner could not reach? Was it a keyboard or screen-reader issue that automated checks cannot catch, and if so, is it covered by your manual spot checks? Close the gap the complaint exposed, not just the barrier itself.
Add a regression check for this exact scenario to your post-deploy checklist. The next theme update or app install should re-verify the fixed flow by keyboard and screen reader, not just by scan. The goal is simple: no customer should ever have to report the same barrier twice, because the second report means your process failed, not just your template.
Review your contact path while you are at it
Most accessibility complaints arrive through a generic contact form that the customer struggled to use. Check that your support channels are themselves reachable: a working email address on the contact page, a phone number that is answered, a form with labeled fields and clear errors. An inaccessible complaint form is a bad look and, practically, it suppresses the feedback you most need.
Brands that treat complaints as free QA get better stores. Brands that treat them as nuisances get demand letters. The difference is a one-day response, a documented fix, and a monitoring rule that makes the incident the last of its kind.
Frequently asked questions
What should we do first when a shopper complains about accessibility?
Thank them, record exactly what they could not do and on which page, and try to reproduce it. A specific, respectful first response buys goodwill and gives your team the detail it needs to fix the actual barrier rather than guessing.
Should we reply before we have fixed the problem?
Yes. A prompt reply that acknowledges the issue, says what you are doing, and offers a way to complete the purchase in the meantime is better than silence while a fix is built. Follow up again when the fix ships.
Does one complaint mean the whole store has a problem?
Not necessarily, but treat it as a lead. The barrier one shopper reported often affects a shared template or component, so check the same pattern on other pages before closing the issue.