What actually happens after you hire us.
Four stages, a fixed scope and a dated record of every finding and fix — written out here so you have fewer things to ask on the call.
Scan
An automated pass runs across every unique template on your site — not every URL, because a thousand product pages built from one template fail in exactly one way. A few seconds, no signup, results on screen.
It reliably catches contrast failures, missing alt text, unlabelled form fields, empty links and buttons, and broken heading structure. That is roughly a third of what a plaintiff's expert would cite.
It cannot tell you whether your focus order makes sense, whether a screen reader announces your booking flow coherently, or whether an alt attribute is accurate rather than merely present. That is the audit.
14unique templates scanned
- Contrast, alt text, form labels, heading structure
- Focus order, screen reader output, alt accuracy
Audit
This is the manual half, and it is the half that decides whether a claim goes anywhere. An engineer walks every flow on the site using nothing but a keyboard, then traces the focus order against the visual reading order to find the places where they part company.
The same flows are run through NVDA on Windows and VoiceOver on macOS and iOS. Every form and every booking flow is completed by hand, start to finish. PDFs linked from the site are checked for tagging and reading order, because a demand letter will not stop at your HTML.
You get a prioritised report: each finding with its severity, the effort to fix it, and the specific page paths it appears on. Delivered in three business days. The fee is credited toward remediation if you proceed within ninety days.
Remediation
Fixes land where your code lives. If you have a repo, they arrive as a pull request your team reviews and merges like any other. If you are on a CMS or a hosted theme, we make the edits in place and show you exactly what changed.
Most fixes are made at the template level, so one change to a product card corrects the same failure on every page built from it. That is why a large catalogue is not automatically an expensive engagement — thirty-one pages, one fix.
Every fix is re-tested individually and signed off before it is closed, not batched into a single pass at the end. When the work is done we write your accessibility statement and publish it.
<div class="btn" onclick="addToCart()">Add to cart</div><img src="{{ product.image }}"><button type="button" class="btn">Add to cart</button><img src="{{ product.image }}" alt="{{ product.title }}">Re-tested and signed off individually · 3.3.2, 4.1.2, 1.1.1
Monitoring
A theme update or a new product template can undo months of work in a single deploy, and nobody notices until a letter arrives. So we re-scan on every deploy and alert you the moment something regresses.
Everything is dated. Every finding, every fix, every re-test and every alert goes into a running record with a timestamp. If a demand letter ever lands, your lawyer has a document showing what you knew and what you did about it.
A conformance report is issued each cycle against WCAG 2.1 AA and EN 301 549. Twelve months of this is included with remediation, and it continues after that if you want it.
What we need from you
Four things that make this fast.
None of these are dealbreakers. We have worked without every one of them. But each one you can hand over takes days off the engagement, so it is worth knowing up front.
- 01
Access to wherever the markup lives
A repo invitation if you have one, or admin access to the CMS or theme editor if you do not. Read access is enough for the audit; we only need write access once you have approved the scope and want fixes to land.
- 02
A staging environment, if one exists
It lets us test fixes against real content before anything reaches your customers. If you deploy straight to production, we work in smaller, more cautious batches instead — it takes a little longer, and that is fine.
- 03
One person who can approve a change
Not a committee. Most engagements that run long do so because a fix sat waiting for a decision about wording or a colour. One named contact who can say yes is worth more to the timeline than anything else on this list.
- 04
A list of your third-party embeds
Booking engines, chat widgets, review carousels, payment iframes. We will find them anyway, but knowing which vendor owns which embed on day one means we can tell you early what is ours to fix and what needs a conversation with them.
What we cannot fix.
You will hear this on the call anyway, so it may as well be on the website. These are real limits, and any vendor who tells you otherwise is selling you something.
- Flagged
Third-party iframes and embedded widgets
Booking engines, live chat, payment iframes and review carousels render inside a document we do not control, so we cannot edit their markup — nobody outside that vendor can. What we do is identify every one of them, test them anyway, document exactly which criteria they fail, and hand you a written summary you can send to the vendor. In our experience that email gets a faster response than a complaint from an individual customer.
- Flagged
Shopify checkout below Plus
Shopify does not give you access to checkout templates unless you are on Plus. We can fix everything up to the checkout button, and we will tell you precisely where our reach ends. If checkout accessibility is the exposure you are worried about, that is a conversation about your plan, not about your code.
- Not offered
Native mobile apps
We work on the web. iOS and Android apps are a different discipline with different tooling and different success criteria, and we would be learning on your budget. We would rather refer you to someone who does it properly.
- Conditional
Content published after we finish
A blog post uploaded next quarter with an untagged image is a new violation on a page we never saw. Monitoring catches this — that is most of why monitoring exists. Without it, our sign-off describes the site as it stood on the date of the report, and nothing after.
Typical engagement
Six weeks, give or take.
This is a typical shape, not a promise. Page count and platform move it more than anything else — a fourteen-template site on a theme we can edit runs at the fast end, a headless stack with a release train runs slower.
- Day 0
Free scan
You run it yourself. A few seconds, no signup, no call required.
- Day 3
Audit delivered
Three business days from kickoff. The prioritised report lands with severity, effort and page paths, plus a fixed remediation quote.
- Day 5
Scope agreed
You decide what is in and what waits. The number is fixed at this point and does not move again.
- Wk 1–4
Remediation
Two to four weeks is the usual range, driven almost entirely by template count and how much of the site is interactive. Fixes arrive continuously rather than in one drop at the end.
- Wk 4–5
Re-test and sign-off
Every fix verified against the criterion it was meant to satisfy, by hand where the criterion demands it. Anything that fails goes back rather than being marked done.
- Wk 5
Statement published
We write the accessibility statement, you approve the wording, and it goes live on your site with the date of the conformance report behind it.
- Wk 5 →
Monitoring begins
Twelve months included. From here it runs on every deploy without you thinking about it, and the conformance report reissues each cycle.
See what a plaintiff’s attorney would see.
One URL, sixty seconds, and a straight answer about where your site stands today.
Free scan. Results on screen, no signup. A few seconds.