Continuous conformance monitoring

You fixed it once.
Your next deploy can break it again.

Accessibility is not a project that finishes. A component library update, a new product template, a marketing landing page, a tweaked brand colour — any of them can reintroduce a failure you already paid to fix, and nobody will notice until a regulator or a customer does.

Monitoring watches your site on a schedule and on every release, tells you the moment something breaks, and keeps a dated record proving you were watching.

What you actually get

1. Scans that keep running without you

Daily, weekly or monthly depending on your plan, at full crawl depth within your page budget. You nominate the pages that matter — the checkout, the account area, the one landing page nothing links to — and they are tested every single time.

2. Alerts when something changes, not before

We compare every scan against the one before it and email you only about what is new. Set the severity that is worth interrupting you for. A blocking failure on a purchase path always gets through immediately; everything else waits for the summary. Noise is what gets monitoring cancelled, so we work hard to send you very little.

3. An accessibility statement that is never out of date

We host it, it updates itself after every scan, and you link to it from your footer with one line of HTML. No more statement claiming conformance you lost eight months ago — which is itself a misleading commercial practice, quite apart from the accessibility problem.

4. An audit trail you can hand over

Every scan, every change, every date, downloadable as a single evidence pack. When an authority asks what you have been doing about accessibility since June 2025, this is the document that answers them — and the difference between a fine and a conversation.

Standard and Enterprise

Catch it in the pipeline, not in production

Add one line to your deploy step. We scan the release as it ships and alert within minutes if it introduced a failure — while the person who wrote the code still remembers writing it.

Rapid-fire deploys are coalesced rather than queued, and the call never fails your build: it returns immediately and we get on with it.

In your CI pipeline

curl -X POST \
  -H "x-conformance-key: $CONFORMANCE_KEY" \
  -H "content-type: application/json" \
  -d "{\"ref\":\"$GIT_COMMIT\"}" \
  https://www.conformancehub.eu/api/monitor/$MONITOR_ID/deploy

Plans

Monthly, cancel any time. Prices exclude VAT.

Essential

€300

per month

One scheduled scan a month across your key pages, with regression alerts and a hosted statement. The minimum a market surveillance authority would expect to see.

  • Monthly scheduled scans
  • Up to 50 pages per scan
  • 1 site, 2 nominated pages
  • Hosted accessibility statement
  • Evidence pack for regulators

Most chosen

Standard

€500

per month

Weekly scans plus a deploy hook your CI pipeline can call, so a regression is caught in minutes rather than sitting live until the next scheduled run.

  • Weekly scheduled scans
  • Up to 150 pages per scan
  • 1 site, 10 nominated pages
  • Deploy hook for CI
  • Hosted accessibility statement
  • Evidence pack for regulators

Enterprise

€800

per month

Daily scans across up to three sites, deploy hooks, and priority response. For teams shipping continuously, or carrying several brands under one legal entity.

  • Daily scheduled scans
  • Up to 500 pages per scan
  • 3 sites, 25 nominated pages
  • Deploy hook for CI
  • Hosted accessibility statement
  • Evidence pack for regulators
  • Priority support

Secure recurring payment by Stripe. Cancel any time from your dashboard.

What the first fortnight looks like

  1. Today — two minutes of setup

    Confirm the site, nominate any pages we would not find by crawling, choose who gets alerts and at what severity. We take the baseline scan immediately and you see the result while you are still on the page.

  2. Same day — the baseline email

    Your starting position, dated. This is the first entry in your audit trail, and the point from which every future change is measured. Your hosted statement goes live at the same moment.

  3. Then — mostly silence

    Scans keep running. Nothing changes, so we send you nothing. This is the correct behaviour and it is deliberate: an alerting system you learn to ignore is worse than none.

  4. The day a release breaks something

    An email naming exactly what is new, on which pages, at what severity, with the fix and the WCAG criterion. If your pipeline calls our deploy hook this arrives within minutes of the release rather than at the next scheduled scan.

  5. The day you fix it

    We confirm it, in writing, with a date. That confirmation is worth more than the alert: it is the evidence that your process works.

  6. Every 30 days — the summary

    What was scanned, what changed, what is open. Sent even when the answer is "nothing", because a documented quiet period is exactly what you want to be able to produce later.

What monitoring does not do

Worth reading before you buy, because a monitoring service that lets you believe you are covered is worse than no monitoring at all.

It does not replace a manual audit

Automated testing catches roughly a third of WCAG 2.1 AA. Monitoring keeps that third honest continuously. The other two thirds need a human, once — that is the audit.

It does not fix anything

We tell you precisely what broke and how to fix it. Someone still has to do it — your team, or ours.

It cannot see behind a login

We do not hold your customers' credentials. Authenticated areas are covered during a manual audit instead. Full scope →

Compliance is a state, not an event.

From €300 a month, cancel any time.

Choose a plan