What should a store do when an accessibility issue comes from Shopify itself?

Figure out exactly where the boundary is: what you control in the theme, what the platform renders itself, and what apps add. Work around what you cannot change, file what you cannot work around, and document the boundary so it is a decision, not a shrug.

Map the boundary first

A Shopify storefront has three layers of responsibility. The theme layer is yours: templates, sections, CSS, and JavaScript your team ships. The app layer belongs to vendors: review widgets, chat, search replacements, loyalty tabs. The platform layer belongs to Shopify: checkout, Shop Pay, the Shop app, order status pages, and increasingly the accelerated checkout buttons. When an alert fires, the first question is which layer the finding lives in. Test in a clean theme with apps disabled. If the finding persists on checkout or Shop Pay surfaces with no theme or app involved, it is a platform issue. Guessing the layer wastes the most time, so isolate before you act.

Work around what the platform renders

Platform surfaces are mostly not editable, but merchants still have moves. For checkout, review what is configurable: the wording of checkout fields where Shopify allows it, the order and visibility of available options, and whether accelerated checkouts that skip the accessible standard flow are the right default for your customers. For post-purchase pages, check what content and scripts you can add through the platform's own extension points rather than fighting the markup. A workaround is not a fix, and you should say so internally, but it is better than leaving a known barrier in the highest-value flow on the store.

File it properly with Shopify

Platform issues should be reported, not just complained about. File with a reproduction: the page, the steps, the assistive technology and browser versions, and what WCAG 2.2 success criterion is involved. Vague reports get ignored. Specific ones with a criterion attached land on a real queue. Keep the ticket number and the date in your accessibility evidence log. If the issue affects checkout, say so plainly, because checkout-adjacent reports get more attention than theme-adjacent ones.

Document the boundary in your accessibility statement

Your accessibility statement should name what you have tested and where the limits are. Stating that checkout is provided by Shopify and that you have reported specific issues, with dates, is honest and defensible. Stating nothing, or implying the whole store was tested when checkout was not, is neither. The statement is the document a plaintiff's lawyer reads first. A boundary drawn in writing reads as diligence. A boundary nobody wrote down reads as ignorance.

Keep monitoring the platform layer anyway

Shopify ships platform changes regularly, and a finding that was a platform issue in March may be fixed by October, or replaced by a new one. Keep the platform surfaces in the monitoring scope even though you cannot fix them directly. When a platform regression appears, you get the alert, the workaround plan, and the report to Shopify before your customers have to tell you about it. The store is still responsible for the customer experience on its pages, regardless of which layer introduced the problem.