What should an agency do when a Shopify platform limitation blocks an accessibility fix?

Not every accessibility barrier is yours to fix. Shopify controls the checkout core, some platform-rendered components, and parts of the Shop app experience, and no theme edit reaches them. The professional response is to document the limitation precisely, implement every workaround the platform allows, and keep a dated record showing the remaining issue is platform-side. That record protects the client if the issue ever becomes part of a demand letter.

Separate what you control from what you do not

The first step is a clean boundary map. An agency should be able to say, in writing, which parts of the storefront render from theme code the agency controls and which render from platform code it cannot touch. On Shopify, the clearest platform-controlled area is the checkout core: the information, shipping, and payment steps run on Shopify's infrastructure with limited customization. Certain dynamic elements, like the Shop app's rendering of the store and some checkout extensions' default behaviors, also sit outside theme control.

Why does the map matter? Because remediation plans, quotes, and legal narratives all depend on it. A client paying for accessibility remediation should not pay for hours spent trying to override something that cannot be overridden. And if a plaintiff's scan flags a platform-side issue, the agency needs to show it knew the boundary and worked within it, not that it ignored the finding.

Document the limitation like evidence, not an excuse

When a scan flags an issue in platform-controlled code, document it in the same evidence log used for everything else, with one addition: proof of the boundary. Record the component, the WCAG criterion it fails, and the specific reason it cannot be fixed in theme code. Screenshots of the rendered markup showing platform-owned classes, links to Shopify's documentation describing the limitation, and a note of any support conversation where the platform confirmed the behavior all count.

This documentation serves two purposes. Internally, it stops the team from re-litigating the same finding every quarter. Externally, it demonstrates diligence. A demand letter that cites a platform limitation lands very differently when the brand can produce a dated record that says: identified, investigated, confirmed platform-side, workaround implemented.

Implement the workaround the platform allows

Platform limitations are rarely total. Shopify's checkout, for example, exposes extensibility points, checkout UI extensions, functions, and branding settings, that allow meaningful accessibility improvements even where the core markup is fixed. Theme-side code can add skip links that land on the main content, improve focus management around embedded components, and provide accessible alternatives for information the platform renders poorly.

The discipline here is to fix everything adjacent to the limitation. If the platform's date picker is not keyboard-friendly, the agency cannot rewrite the picker, but it can ensure the surrounding form has proper labels, error handling, and a keyboard path that degrades gracefully. Partial fixes are still fixes, and they still reduce both user harm and legal exposure.

Track platform changes that resolve old limitations

Platform limitations are not permanent. Shopify ships checkout and storefront changes continuously, and a limitation documented in January may be solvable by June. Agencies should review their documented platform limitations on a schedule, quarterly is reasonable, and test whether each one still holds. When the platform fixes the underlying issue, the agency should verify the fix on the client's store and close the log entry.

This is also a client-retention practice. Telling a client, unprompted, that a limitation you flagged six months ago is now resolved and you have verified the fix, is exactly the kind of proactive work that justifies a monitoring retainer. It turns a limitation log from a defensive document into a visible source of ongoing value.

Be honest in client communication

Clients deserve plain language about platform boundaries. The conversation should happen before the remediation quote, not after the invoice: here is what we can fix, here is what the platform controls, here is what we will do about the platform-controlled parts. Agencies that bury platform limitations in fine print invite the worst possible discovery moment, which is the client learning about the limitation from opposing counsel.

Honesty also sets up the right commercial model. Platform-limitation work is monitoring and documentation work, not remediation work, and it should be priced that way. A client who understands the boundary will pay for vigilance. A client who discovers it later will question every line of the original quote.