Skip to main content
Scanready Test now
Our own analysis · 19 sites · 794 findings

What remediation really costs: 792 findings are 284 decisions

Quotes for accessibility work range from 79 to 15,000 euros, and nobody explains why. The reason is that almost everyone uses the wrong anchor. We worked the remediation of 794 findings all the way through once.

The number of findings is the wrong price anchor

Between what a testing tool outputs and what somebody actually has to do lie two steps of reduction.

First step: raw hits versus consolidated findings. A contrast failure in the footer appears on every page of a site. A testing tool therefore reports it as often as it tested pages. In our measurement across 20 sites, 1,862 raw hits stood against 792 consolidated findings — a factor of 2.4. On individual sites the gap was larger still: 396 raw hits against 157 actual places.

Second step: findings versus decisions. Even 792 is too high. Many findings are repetitions of the same correction: the same colour pair, the same CSS class, the same icon in five places. Add those together and 794 analysed findings come down to 284 independent decisions — an average of 2.8 findings per decision, considerably more on the large jobs. The site with 157 findings came to 29 decisions.

Anyone quoting by raw hits is selling the same work up to five times over. Anyone quoting by findings is still selling it 2.8 times on average. That is no imputation of intent — it is simply the number that falls out of the tool if you do nothing further with it.

For the sake of clean figures: the remediation analysis ran on 25 August 2026 against the then-current stock of 19 sites with 794 findings. The accessibility measurement in the article on the most common barriers now covers 20 sites with 792 findings, because one site was added and several scans were refreshed. The two figures are therefore similar but not identical. We do not harmonise them artificially.

Four classes every finding falls into

The effort does not hang on the number but on how many decisions a human has to make.

We sort every finding into exactly one of four classes. Automatic means the proposal is complete and no substantive decision is required. Calculated means the same, except the value comes from arithmetic — for contrast, the nearest conforming colour value can be computed. Draft means the proposal is there but a human must confirm the wording, for example the label of an icon button. Human means there is no code proposal, only a recipe and the context.

Remediation analysis of 25 August 2026: 19 sites, 794 findings
ClassFindingsShareWho decides
calculated43054.2 %nobody — the value follows from the contrast calculation
automatic14718.5 %nobody — just install it
draft8811.1 %a human, in seconds
with a code proposal, total66583.8 %
human12916.2 %a human, looking at the page

Our own analysis of the stock as at 25 August 2026. “With a code proposal” means a concrete before-and-after fragment exists. It does not mean the change is installed unchecked.

More than half of all findings are pure contrast arithmetic. That is the practically most important figure in this article. A contrast ratio is not a matter of taste: for any given background there is a nearest colour value that reaches 4.5:1, and it can be calculated. There is still an argument — but not about the number, rather about whether the brand blue may be touched.

And the other direction: 16.2 per cent stays manual work, and it cannot be automated away. Anyone promising otherwise is selling an overlay.

Batch corrections: why a job is smaller than it looks

The reason 794 findings become 284 decisions has a name: the batch correction. Every proposal gets a key derived from the actual change at attribute level — for contrast from the colour pair, for a removed CSS class from that class. Everything sharing a key is the same act.

An example from the measurement: on an outdoor retailer’s site, a single act — removing the class no-underline from links in running text — cleared 42 findings at once. One colour value in a central CSS variable clears every finding with the same colour pair, no matter how many pages they sit on.

Measured in the browser, in the worksheet we use to work through findings: a job with 152 findings was empty after 37 key presses, one with 13 findings after 9. That is expressly not the working time — it is its floor. The time goes into reading and deciding, not into ticking off. But it shows the order of magnitude by which an honest calculation differs from one based on findings.

Where the work actually sits

Manual work is not spread diffusely across everything. It sits in two places.

Alternative texts, 62 findings. Whoever has not seen the image cannot describe it, and a wrong alternative text is worse than none: it makes the finding disappear without solving the problem. This is the only item that grows linearly with the number of images. A model that can see images would be the next step — but the result would still be a draft for a human to confirm.

Structural defects, 61 findings in total (listitem, nested-interactive, list, aria-required-children). Here the economics are the other way round: the defect almost always sits in one place in a template and clears many findings from there. Only finding it is expensive, because a testing tool reports the faulty fragment while the defect sits in the parent element.

What does not weigh in is computing time. Analysing all 19 sites cost 0.0025 US dollars in model fees — 0.13 cents per job — at around 0.6 seconds per job, nearly all of it waiting. Technology is not the cost driver in this business. The decision is, and so is the installation work in someone else’s system.

looked up on 25 August 2026

What is actually being asked in the market

For comparison, the prices we read off publicly available provider pages on 25 August 2026. Ongoing automated testing services ranged from 19 to 299 euros a month; one provider adds a “from 999 euros” tier for very large sites. Some net, some gross — the comparison is only worth making if you read that along with it. One-off testing services run from a quick check at 79 euros to a full audit between 490 and 1,250 euros.

For remediation there are no comparable list prices. Agencies state on their own pages roughly 2,000 to 8,000 euros for retrofitting an existing corporate website, 8,000 to 15,000 euros for sites with a shop or many interactive components, and 200 to 800 euros a month for ongoing support. These are providers’ own statements, not surveyed market data — we reproduce them as exactly that.

Put side by side, the contradiction becomes visible: the most expensive item is remediation, and it is precisely for that item that nobody states a traceable unit of calculation. The range from 2,000 to 15,000 euros is a factor of 7.5. The range of findings is just as wide — except that one of them is measurable and the other is guessed.

A fuller breakdown by the four cost blocks — testing, remediation, monitoring, documentation — is on our cost page.

Six questions any quote must answer

To turn a ballpark figure into a calculation. These questions apply to our own quotes too.

  • Do you count raw hits or consolidated findings? In our measurement the difference was a factor of 2.4, and more in individual cases.
  • How many of the findings are the same single act? A serious quote can state the number of batch corrections, not just the number of findings.
  • What is included — testing, remediation, documentation, monitoring? Four blocks of completely different magnitudes. A quote that stirs everything into one figure cannot be compared, and often that is the point.
  • How many findings remain manual work? For us it was 16.2 per cent. Anyone saying zero is promising something that is not possible.
  • Who installs the changes, and in which system? A code proposal shows the element, not the file. Only whoever holds the source knows where the place is.
  • What happens after the next theme update? See below.

And one question for any provider promising completeness: what share of the criteria does your procedure test automatically? Anyone who names no figure, or says “all of them”, has either not checked or is selling an overlay.

§ 14(3) BFSG

The item almost every quote leaves out

Conformity is not a state but a process. Every theme update, every new product page, every additional plugin can introduce new barriers — and regularly does. A one-off remediation applies to today’s state.

That is not our sales prose but the statutory text. § 14(3) BFSG requires the service provider to meet the accessibility requirements at all times, and expressly names changes in the way the service is provided, changes in the requirements and changes in the harmonised standards as matters to which “due regard” must be given. And § 17(3) requires anyone invoking a disproportionate burden to repeat the assessment at least every five years and whenever the service changes.

In practice: an honest calculation contains a recurring item. How large it is depends on how often the site is worked on — different for a shop with weekly changes than for a site touched twice a year.

Technically the effort for it is small: a second scan compares finding by finding using the same fingerprint and separates them into fixed, still open, new. That is at once the evidence for third parties — and, frankly, the point at which you notice whether a remediation was really installed or merely ticked off.

What that costs with us, and what the test mark is tied to, is on the pricing page. In short: the mark is valid for as long as testing continues — that is not a contract clause of ours but the condition under which a test mark may be displayed at all.

Sources and data

All links were checked on 27 August 2026. Market prices were read off publicly available provider pages on 25 August 2026; they are providers’ own statements and are marked as such.

  1. Own analysis, ScanreadyRemediation run of 25 August 2026 across 19 sites with 794 findings: class distribution, batch corrections, 284 decisions, model costs. Method and limits are described above.https://scanready.eu/en/ (opens in a new window)Retrieved on 27.08.2026
  2. Own measurement, ScanreadyScan runs of 21 and 25 August 2026 across 20 sites, 108 pages, 1,862 raw hits, 792 consolidated findingshttps://scanready.eu/en/knowledge/most-common-barriers-online-shops/ (opens in a new window)Retrieved on 27.08.2026
  3. Barrierefreiheitsstärkungsgesetz (BFSG)§ 14(3) — continuous fulfilment of the requirementshttps://www.gesetze-im-internet.de/bfsg/__14.html (opens in a new window)Retrieved on 27.08.2026
  4. BFSG§ 17(3) — repeat assessment at least every five years and whenever the service changeshttps://www.gesetze-im-internet.de/bfsg/__17.html (opens in a new window)Retrieved on 27.08.2026
  5. Web Content Accessibility Guidelines (WCAG) 2.1, W3C RecommendationSuccess criterion 1.4.3 — contrast ratio 4.5:1 for normal text, 3:1 for large text; the basis of the “calculated” classhttps://www.w3.org/TR/WCAG21/#contrast-minimum (opens in a new window)Retrieved on 27.08.2026
  6. axe-core 4.10.2, Deque Systems, licence MPL-2.0Testing engine whose rule identifiers the class assignment is derived fromhttps://github.com/dequelabs/axe-core (opens in a new window)Retrieved on 27.08.2026

Read on

The most common barriers in German online shops

The measurement this article builds on: which findings occurred how often, and what a test does not see.

Who is exempt

Before you calculate: you may not be covered at all. The exemption in its exact wording.

Cost overview

The four cost blocks — testing, remediation, monitoring, documentation — with market prices side by side.

Our pricing

What testing, remediation and ongoing monitoring cost with us, and what the test mark is tied to.

Check the numbers on your own site

The instant result states both: raw hits and consolidated findings. That gives you the figure with which to check any quote — including ours.

Test your website See pricing