How Shopify apps quietly break theme accessibility
Most accessibility regressions on Shopify do not come from the theme. They come from apps: review widgets with unlabeled stars, popups that trap the keyboard, chat buttons with no accessible name. Here is what breaks, how to spot it, and the rules that keep apps from undoing your theme work.
The theme passed. Then the apps arrived
Here is a pattern we see constantly: a brand launches on an accessible theme, passes an audit, and six months later fails the same checks. Nothing in the theme changed. What changed is the app stack. A review app added a star-rating widget built from clickable divs. A post-purchase upsell started firing modals with no focus management. A chat widget injected an unlabeled button that screen readers announce as "button" with no context. Each app is small. Together, they quietly undo the theme's accessibility work.
What apps usually break
Review and rating widgets are the most common offender. Stars rendered as spans or divs with click handlers are invisible to keyboard users and meaningless to screen readers unless the app developer added proper roles and labels. Many did not. Popups and slide-outs come next: newsletter modals, spin-to-win wheels, and cart upsells that open without moving focus, trap the keyboard inside, or cannot be dismissed with the escape key. Live chat widgets frequently fail the simple test: tab to the chat button and check whether its purpose is announced. "Button" with no name is a failure.
Cookie banners and consent apps count too
Consent management apps inject banners on every page, and many of them have their own accessibility problems: buttons with low contrast, focus that does not move into the dialog, and settings panels that keyboard users cannot reach. An inaccessible consent banner is a barrier on every single page of the store, which makes it one of the highest-impact things to fix.
How to vet an app before installing
Install the app on a development or preview theme first, never directly on the live store. Then run a short checklist: tab through the app's interface with a keyboard and confirm everything is reachable and operable; check that interactive elements have accessible names, not just icons; open and close any dialogs and confirm focus behaves; run an automated checker and compare the results before and after. If the app adds errors, contact the developer before going live. Many app developers fix accessibility bugs quickly once they are reported, because the fixes are usually small.
Keep a regression routine
Apps update constantly, and an update can reintroduce problems a previous version fixed. Add accessibility checks to the routine you already run when installing or updating apps: keyboard walkthrough of the new interface, a quick automated scan diff, and a look at anything the app injects into checkout or the cart drawer. Continuous monitoring catches what the routine misses, because it tests the store as shoppers experience it, apps and all, after every change.
What to do with apps that will not cooperate
Sometimes an app is essential and its developer will not fix the issues. You still have options. Many apps expose settings that disable the worst offenders, like auto-opening popups or animated widgets. Some problems can be worked around at the theme level with careful overrides, though this needs maintenance. And occasionally the right answer is to replace the app: when two apps do the same job and one is accessible, the choice is straightforward. Accessibility is a feature of the whole storefront, and every app on it is either helping or hurting.