What moves a Sprint between bands is theme complexity: how many custom sections there are, how the variant picker is built, whether there is a mega menu, how many drawers and modals exist, and how app-dense the storefront is. None of that is visible from the outside, which is why we measure before we quote. After the Audit you get a fixed price in writing — no hourly billing and no scope surprise.
Payment is 50% to start and 50% on delivery. Access is taken by Shopify collaborator invite only; we do not accept a shared admin password, even when it is offered. Neither the Scan nor the Audit needs any access at all — both run against the public storefront. Access is only required once there is something to fix, which is after you have already seen our work.
A Sprint includes the first three months of Guard. After that it continues only if you want it to, and ends on written notice.
Request the free scan
What you actually receive
A Sprint delivers six things, and all six are files rather than assurances:
- the findings report — criterion, severity, theme file location, suggested fix;
- the remediated theme;
- a before-and-after verification report — same engine, same routes, two different dates;
- the text of an accessibility statement you can publish, written to say honestly what has been done and what is still open;
- a dated evidence record;
- the remaining roadmap, including anything that did not pass.
We have no published case study yet, and we are not going to invent one. This service line is new. There is no client wall, no logo strip and no “before 42, after 0” graphic on this page, because we do not yet have one we are permitted to show. What we can point at is our own work: Darkroom, the Shopify theme we build and maintain ourselves, where the accessibility and performance constraints are properties of the package you can verify by reading the code. Case studies get published here when a client gives written permission and the numbers are anonymised — not before.
One thing you can check right now, on this page. We run the same engine against our own pages. This one, measured on 25 August 2026 with axe-core against the WCAG 2.2 AA rule set, at 390px and 1440px: zero violations in both viewports, with one element on mobile the scanner could not decide on its own. That is the automated half only — the same limit we state in every report, and the reason the 28 manual checks exist. It proves nothing about your store. It does mean the people selling you an audit passed their own.
Who this is for
Three groups, and we are direct about it because a bad fit wastes your week and ours.
US direct-to-consumer Shopify brands, roughly $1M to $25M
Large enough that a broken purchase path costs real orders, small enough that the work is still one focused engagement rather than a programme. If you have received a demand letter already, talk to your lawyer first — we do the measurement and the remediation, and we do not give legal advice at any point.
Brands selling into the EU
The European Accessibility Act applies to services provided to consumers in the Union, and being established elsewhere is not in itself an exemption. Whether you are in scope is a legal assessment; whether your storefront can be used with a keyboard is not, and that is the half we can answer this week.
Theme studios shipping to the Shopify Theme Store
Theme Pass is a pre-submission pass: five days, $800 to $1,500, before review rather than after a rejection.
Who this is not for
Anyone looking for a badge to put in the footer, because no such thing legitimately exists. Anyone who wants the appearance of remediation rather than the work. And any store whose scope, once measured, runs past roughly forty hours — there we split the engagement or decline it, rather than quoting a number we would have to earn back by cutting the verification.
What is not included
The most important section on this page. Everything written here is also written in your contract, in the same words.
This is not legal advice. We are not lawyers, we are not a substitute for one, and we do not produce an opinion that any regulation has been met.
There is no such thing as an accessibility certificate. Neither the ADA nor the EAA defines one and no body issues one. What we produce is measurement, remediation, verification and a dated record.
No site is permanently “fully accessible”. The next content update, app install or campaign page can introduce new violations. That is why a Sprint is sold as a baseline rather than an ending.
An automated scan is not an audit. The 57% and 30% figures at the top of this page are the reason the manual pass exists — and your free scan report says so inside the report itself, not only here.
Out of scope, listed explicitly in the contract: third-party app iframes · user-generated content, including reviews and customer photography · PDFs and other documents · Shopify checkout, which is controlled by the platform and cannot be reached from theme code · email templates · native mobile apps · any route not named in the scope list.
We do not offer an indemnity.
We do not invent alt text. If it can be derived from the image or your product data, we derive it. If it cannot, we ask you. Empty is better than wrong.
We do not change your appearance unilaterally. Contrast is a palette decision; no fix affecting the brand’s look ships without design approval.
So what is it you are buying
Position, not protection. The defensible version of the argument is this: documented, good-faith remediation improves a settlement position, and evidence dated before a demand letter arrives carries more weight than a record assembled after one. We are not going to put a percentage on that, because we cannot show you where the percentage came from, and a number without a source would undo the only real advantage we have. What you are buying is a timely, measured, dated record — and behind it, a theme that has genuinely been fixed.
Questions
We already run an accessibility widget. Does that change anything?
No, and that is usually why the findings are worth reading: a scan run while the widget is live still returns them. An overlay runs after the page has rendered, so what it can reach is the final DOM — it can attach a label to a button, it can apply a contrast filter. What it cannot reach is the .liquid file that produced the button. We do not ask you to remove anything. We fix the source and leave; whether you keep paying a subscription after that is your call to make with the report in front of you.
Does this mean we will not be sued?
No. Be wary of anyone who tells you otherwise — no product prevents a demand letter or a lawsuit, and ours does not either. What we do is measurable: we remove real barriers and we document the work with dates attached. Documented, good-faith remediation improves your settlement position, and evidence dated before a demand letter arrives carries more weight than evidence produced after one. We are not going to attach a percentage to that, because we cannot show you where the percentage came from. What we sell is position, not protection, and we say so on the page rather than in the small print.
Our theme came from the Shopify Theme Store. Is it not already accessible?
Partly. Theme Store review sets a floor rather than a finish line, and the floor covers a fraction of the WCAG success criteria. The bigger issue is that most of what we find did not ship with the theme: it arrived afterwards, in custom sections, installed apps, campaign pages and rewritten variant pickers. A store generates accessibility debt as it is merchandised. That is also why the free scan is worth ten minutes even if you are confident about the theme itself.
A widget costs $49 a month. You are asking for thousands.
That is the wrong comparison, because the two things do not do the same job. A subscription is an indefinite rent — around $3,000 over five years, and the day you stop paying you are back where you started, because nothing changed in your theme. Our work is a one-off change that stays in your code: no script to remove, no runtime cost, no licence to renew, plus a dated record a subscription invoice cannot give you. If the budget is genuinely tight, the right entry point is not the Sprint but the $750 Audit — you get the full findings and your own developer does the work. If you come back to us, that $750 is credited in full. The scan costs nothing at all.
Could our own developer do this?
Yes, and we mean that. The report is written so they can: every finding carries its WCAG criterion, a severity class, the theme file it lives in and a suggested fix. It is yours whether or not you work with us. The difference is speed and the part automation does not reach. Automated testing catches roughly 57% of accessibility issues by volume and fully automates about 30% of the success criteria; the rest is a manual pass — keyboard traps, focus order, focus return from a drawer, live-region announcements, form error handling — and the critical purchase path actually completed with VoiceOver and NVDA. If your developer has done this before, you are in good hands. If they have not, the first one is usually learned at a price higher than ours.
We are a micro business, or we are not in the EU. Does the European Accessibility Act apply to us?
That is a legal question and you should put it to a lawyer — we do the measurement side, not the assessment. Two technical details get skipped often enough to be worth stating. First, the micro-enterprise exemption requires fewer than 10 people and a turnover or balance sheet total not above €2 million; headcount on its own is not enough. Second, being established outside the EU is not itself an exemption — the Act is written around services provided to consumers in the Union, so where you ship to matters as much as where you are. If you conclude you are out of scope, this page closes for you, and that is a perfectly reasonable outcome.
We are redesigning soon. Should we wait?
It is a reason to move it forward rather than back, and that is engineering rather than sales. During a redesign, accessibility is a decision: semantic structure, focus order and a contrast-safe palette are born inside the design. After launch it becomes a repair, and you get the same result by taking finished components apart. The second is always more expensive. Theme Pass exists for exactly this moment — five days, $800 to $1,500, before the new theme goes live. If you would still rather wait, take the free scan now; it costs you nothing and gives you a list to put in the redesign brief.
Will this change how our store looks?
Almost none of it will. The overwhelming majority of fixes are invisible: missing labels, button names, closed drawers that never received inert, focus order, form associations, a language attribute. None of those have a pixel consequence. The one visible category is contrast — and there we do not act unilaterally, because contrast is a palette decision. We show you options that pass, you choose, and no fix that affects how the brand looks ships without design approval. That is our internal rule, not a concession we make when asked.
Will anything break? How long does it take, and what do you need from us?
We never touch your live theme. We duplicate it, work on the clone, verify on staging, show you, publish with your approval and record a rollback point. Your store trades normally throughout. Timings: the scan takes about ten minutes and needs nothing but your store URL; the Audit is three days and needs a collaborator invite; the Sprint is 10 to 14 working days and needs the invite, answers to a few content questions, and palette approval. Your own time is usually under an hour in total. Those content questions exist because we do not invent alt text — if it cannot be derived from the image or the product data, we ask you.
Do you issue a certificate, or a badge we can put on the site?
No — and that is not a gap in what we offer. No such document exists. Neither the ADA nor the EAA defines an accessibility certificate and no body issues one; the badges being sold are self-awarded. What you get instead is less decorative and more useful: a before-and-after verification report run on the same engine and the same routes on two different dates, a dated record of what was measured, what was fixed and what is still open, and the text of an accessibility statement you can publish — one that says honestly what you have done and what is still outstanding. If a demand letter ever arrives, those three are what your lawyer will ask for. A badge is not.
Why is the price a range? Give me a number.
The variable is not how many products you sell, it is how much theme there is to work through: custom sections, how the variant picker is built, a mega menu, how many drawers and modals exist, how app-dense the storefront is. None of that is knowable from the URL. So the order is: free scan, then the $750 Audit, then a fixed price in writing once we have measured. No hourly billing, no scope surprise. If you take the Audit and stop there, you keep the full findings report. Quoting before measuring either favours you or favours us, and both are a bad way to start.
What happens after the Sprint?
The first three months of Access Guard are included. After that, continuing is optional and ends on written notice — there is no lock-in, and if you stop, nothing is taken back: the fixes are in your theme and the evidence record is in your hands. The only thing you lose is the monitoring. The reason to keep it is that accessibility is a maintenance item rather than a state. A new section, a new app, a campaign page or a theme update can each produce new violations. Guard re-scans monthly, catches the regression, closes it inside a two-hour monthly allowance, and keeps the dated record running. One dated report is a snapshot; an unbroken series is a practice.
Sources
Every figure on this page is either a price we set or a number with a source you can open. Where we do not have a source, the number is not here — which is why this page carries no litigation statistics, no share-of-lawsuits figure and no violations-per-theme range. Those exist in our internal notes with the denominators unverified, and they stay there until the reports behind them can be linked from this list.
- Deque Systems, The Automated Accessibility Coverage Report — the source of the ~57% by volume and ~30% of success criteria figures. deque.com/automated-accessibility-coverage-report
- US Federal Trade Commission, press release, January 2025 — a $1,000,000 order over deceptive claims that an AI product could make websites conform to accessibility guidelines. ftc.gov press release
- W3C Web Accessibility Initiative, What’s New in WCAG 2.2 — the nine added success criteria and their conformance levels. w3.org/WAI — new in WCAG 2.2
- Directive (EU) 2019/882, the European Accessibility Act — the micro-enterprise definition and the scope of services covered. eur-lex.europa.eu — Directive 2019/882
Send us your store URL and we will send you the measurement
Five routes, mobile viewport, WCAG 2.2 Level AA. About ten minutes later you have the count, the number of distinct rules behind it, which routes are affected, and which findings close site-wide with a single fix.
The report is yours. If you never speak to us again you can hand it to your developer — that is what it is written for.
Prefer email? Send hello@fyzn.studio the store URL and nothing else — that is genuinely all we need to start.
Everything runs in writing. No call, no deck, no waiting for a calendar slot — measurement, a fixed written scope, and a recorded walkthrough when the work is done.