The monitoring tells you what is broken. This is the part where it stops being broken.

01 — WHY REPAIR IS NOT IN THE SUBSCRIPTION

A product that edits your site on a schedule is a different risk

The monitoring works because it observes and never intervenes. It runs whether or not anyone reads it, it cannot break a page, and it needs nothing from you, your webmaster or your developer. That is the whole design, and it is why the report is worth anything: an observer with no stake in the finding.

Repair is the opposite shape. It touches markup, it needs someone to approve a colour, it has to be tested, and it can regress the next time a plugin updates. Bundling that into a monthly fee would mean either quietly editing your site without asking, or sending you a task list every month and calling it a service. We do neither. So repair is priced once, scoped from evidence, and then it ends.

02 — THE TWO HALVES OF A FINDING

One half is a patch. The other half is a decision only you can make.

Treating every WCAG failure as the same kind of work is how remediation quotes become fiction. They divide cleanly, and they divide about evenly.

Mechanical

A button with no accessible name, an image with no alt text, a form field with no label, a landmark that is missing, a list role that its children do not satisfy. These have one correct answer. We make the change and the next scan shows the date it cleared.

A design decision

Contrast. Raising a failing ratio means changing a colour, and the colour is usually your brand. We propose the smallest change that clears the threshold, show it against the real page, and wait for your sign-off. We do not repaint a practice’s identity to win a number.

Out of scope either way

Anything requiring a judgement about content. Whether a page’s reading order makes clinical sense, or whether a video needs a described audio track, is not a defect a scanner can settle and we will not pretend otherwise.

03 — WHAT THE ENGAGEMENT IS

Five things, delivered once, then handed over

1. A scan of the live site, on the conversion path first

   Not the blog. The pages a patient actually moves through to book something — because that is where a failure costs the practice a patient, and it is where a complaint starts. You keep this document whether or not anything else proceeds.

2. The mechanical half repaired

   Names, labels, alt text, landmarks, roles and focus order corrected directly in the markup, on the pages in scope, without changing how anything looks.

3. A contrast pass, proposed and signed off

   Every failing pair measured, a minimal adjustment proposed against your existing palette, shown on the real page. Nothing ships until you approve the colours.

4. A re-scan, with dates

   The same engine, run again after the work. Each finding carries the date it cleared, and anything that did not clear is listed as still open rather than quietly dropped.

5. A handover document

   What changed, where, and why — written so whoever maintains the site next can avoid reintroducing it. Then the engagement ends.

04 — WHAT IT COSTS

One fee, paid once, scoped before anyone commits

Moves it down

Few templates, findings concentrated in markup, a palette that already clears AA.

Moves it up

Contrast failures in the brand colours themselves, many distinct page templates, third-party embeds you do not control.

Not charged

The scan that scopes it. Run it yourself, free, before you talk to anybody.

05 — WHAT THIS IS NOT

Four things this engagement will not do for you

• It will not make your site ADA compliantCompliance is decided by a court, not by a vendor and not by a scanner. What this produces is a smaller set of defects and a dated record of when each one was fixed.

• It will not install an overlayNot at any price, and not as an option. An overlay is a widget that claims to fix accessibility at the browser and does not. We will not ship one.

• It will not replace a human testerAutomated rules catch a real but partial share of what disabled patients actually hit. Someone using a screen reader on your booking flow will find things no engine does.

• It will not stay fixed on its ownA theme update or a new plugin can reintroduce any of it next month. That is what the monitoring is for, and it is why the two are priced apart.