# A client wants an accessibility widget instead of real remediation. Now what? | A11yShieldHQ Source: https://a11yshieldhq.com/blog/2026-10-10-agency-client-accessibility-widget-instead-remediation.html [Home](../index.md) / Client acquisition Published October 10, 2026 Do not refuse the widget outright and do not install it quietly. Explain what the widget does and does not fix, show the gap in their own scan results, and offer the widget as a supplement to a remediation plan, never a substitute for one. The client who asked for the widget is telling you they want the cheapest fix; your job is to make the real fix feel like the safe one. ## Why the client asks for the widget The request is almost never about accessibility. It is about price, speed, and fear. The client got a demand letter or saw a competitor get one, googled the problem, and found a product that promises compliance from a single line of JavaScript. Compared to your proposal for a three-month remediation engagement, the widget looks like the obvious move: five minutes to install, a monthly fee smaller than their coffee budget, and a badge on the site that says they did something. Underneath that is a belief you need to address directly, not dismiss. The client thinks accessibility is a checklist with a yes or no answer. They think the widget is the answer. If you respond by scoffing at the product, you confirm their suspicion that agencies are just upselling. If you respond by installing it, you own the liability when it fails. Neither path protects anyone. The useful response is a demonstration, not an argument. ## Show the gap on their own storefront Run your scanner against their store before and after a widget trial, and put the two reports side by side. What they will see is exactly the point you need to make: the widget changes the toolbar experience for the visitor but the underlying issues are still in the report. Unlabeled form fields are still unlabeled. The keyboard trap in the mobile menu still traps the keyboard. The contrast failures in the theme are still failing. The widget did not touch the code, so the code still fails. This is the part clients actually absorb, because it is their store and their risk. The abstract debate about whether widgets work is endless; a report with their domain on it is not. Walk them through five findings that a serial plaintiff would notice first. Name the price of each finding in the context of a demand letter. Then ask the only question that matters: if this store were tested by a plaintiff's expert with a screen reader, would you rather defend the widget or defend the fixes? One caution: do this before the widget is installed, not after. Once the widget is live, the client has made a decision and you are now arguing against it. Your scan comparison becomes an attack on their judgment. Time the conversation for the proposal stage, when they are still choosing. That is also when the comparison costs you nothing, because you have not done any remediation work yet. ## Offer the widget as a supplement, not a substitute There is a version of this conversation that ends with the widget installed and everyone honest about what it is. The client may genuinely want the assistive toolbar for some visitors. That is fine, as long as it is documented as an enhancement, not as compliance. Your scope of work should say this explicitly: the widget provides user-facing adjustments; the remediation engagement fixes the underlying WCAG failures; the widget is not a defense against a demand letter and the agency does not represent it as one. That sentence protects you, but it also protects the client, because it forces the real decision into the open. If they still choose the widget alone, they have done so with eyes open, and you have a signed scope that says what was and was not done. If they choose remediation, the widget conversation is behind you and never comes up again. What you cannot do is leave the ambiguity in place. An unsigned assumption about what the widget covers is the thing that becomes a lawsuit footnote. ## The agency's real product here is certainty Clients buy the widget because it feels certain: install, badge, done. Your remediation proposal feels uncertain: audits, phases, findings that change the number. The way to win this conversation is to make remediation feel more certain than the widget. That means a findings inventory before a quote, a fixed scope built on that inventory, and a clear statement of what the client gets at the end: a store that passes a real audit, with the report to prove it. The widget conversation will keep coming up, with every new client, for the foreseeable future. Build the response once: a one-page explainer you attach to proposals, a scan template that produces the before-and-after comparison, and a scope-of-work paragraph that names the widget's role honestly. Then the request stops being an awkward moment and becomes a selling moment. The client who asked about the widget is the client who already knows accessibility matters. They just need someone to make the real work feel safe. ## Frequently asked questions ### Can an accessibility widget make a Shopify store compliant on its own? No. A widget can adjust presentation for some visitors, but it does not fix missing labels, keyboard traps, or poor structure in the underlying code. Stores still need remediation of the actual barriers, with the widget, if used at all, as a supplement rather than a substitute. ### How should an agency respond when a client asks for a widget instead of remediation? Explain plainly what the widget can and cannot change, put that explanation in writing, and offer a scoped remediation plan for the barriers that matter most. If the client still chooses the widget alone, document the decision and the advice that was given. ### What should we do if we already installed a widget? Keep testing the store as shoppers experience it, with keyboard and screen reader passes, and fix the barriers those tests find in the theme itself. Do not let the presence of a widget close findings that are still present underneath it.