Accessibility evidence · checked 29 July 2026

Accessibility audit cost: compare the test

A scan, a sampled WCAG review, and a publishable BIK test are different products. Compare the target, sample, processes, evidence, exclusions, and retest before comparing price.

Project review with stakeholders
On this page
  1. Direct answer
  2. The pricing anchor
  3. Public price observations
  4. Why scopes diverge
  5. Normalize the quote
  6. Comparable request
  7. What tools can prove
  8. BFSG applicability
  9. Before accepting a quote
  10. Common questions
  11. Some Tech Work scope
Accessibility audit quote compared by sample, complete processes, manual tests, report, and retest
Direct answer
  • There is no audited German market average for a website accessibility audit in the public evidence we reviewed.
  • BIK currently prices a BITV test from a base amount, representative pages, and technical complexity. Its worked example is €4,200 net for seven selected pages plus an example €250 base amount.
  • Published provider offers checked on 29 July 2026 include a €490 net quick check, a WCAG 2.2 AA audit from €2,480 net, audit plus remediation from €4,900 net, and a separate audit-and-report offer from €195. Their different definitions prevent a combined market range.
  • Compare quotes only after the target standard, representative page states, complete processes, technologies, assistive-technology tests, reporting use, documents, remediation, retest, tax, and exclusions are fixed.
  • A tool report does not determine accessibility or conformance. W3C says knowledgeable human evaluation is required.
The pricing anchor

BIK publishes a transparent pricing mechanism.

The current BIK BITV/WCAG test pricing page says a BITV test is calculated from a base amount, the number of pages in a representative selection, and technical complexity. Its indicative net page prices are €420 for level I, €630 for level II, and €840 for level III. Complex web applications at level IV are estimated from expected test effort.

BIK’s worked FAQ example selects seven pages: one at level III, four at level II, and two at level I. The page prices total €4,200 net, followed by an example €250 administrative base amount. BIK also says the responsible test centre prepares an individual quotation and may deviate from the indicative page price.

That arithmetic is useful because its inputs are visible. It represents BIK’s worked example. A Some Tech Work price, German average, or prediction for your product would require separate evidence. A checkout, authenticated workflow, document library, or complex application can change the representative sample and effort materially.

Public price observations

The visible prices describe different products.

Sources: BIK pricing and FAQ, BFSG Expert provider pricing, and Charismarcom’s published rate card. These attributable observations have different definitions and do not form a combined market range or a Some Tech Work quote.
Source and date checkedPublished observationWhat the source says is includedDo not infer
BIK, checked 29 Jul 2026€420 / €630 / €840 net per selected page at levels I–III; level IV by effortBIK BITV test pricing logic; base amount and possible extras are separateA fixed total before representative selection and complexity assessment
BIK worked example, checked 29 Jul 2026€4,200 net for seven selected pages plus an example €250 base amountOne level III, four level II, and two level I pagesA typical seven-page website price or a promise from every test centre
BFSG Expert, checked 29 Jul 2026€490 net quick check; WCAG 2.2 AA audit from €2,480 netProvider-defined packages; the full audit describes manual criteria review and specific screen readersAn independent market floor or the scope of a BIK test
BFSG Expert, checked 29 Jul 2026Audit plus remediation from €4,900 netProvider-defined complete package with retest for its stated standard caseThe remediation cost for an unknown codebase or third-party system
Charismarcom rate card, April 2025Audit and report from €195One-page provider rate card says WCAG/BITV review and report, depending on website sizeEquivalent manual depth, sample, assistive technology, or reporting use
Why scopes diverge

Ten pages can mean ten copies of one template or ten different test states.

The W3C WCAG Evaluation Methodology 2.0 starts with the product boundary, conformance target, technologies, representative samples, and complete processes. A login, checkout, application, booking, or multi-step form must be followed through its states. Raw URL count misses that work.

The same methodology warns that evaluating a selected sample usually does not support a conformance claim for an entire website. A quote must say whether the output is a preliminary review, a sampled evaluation statement, a BIK result that may be published, or evidence for an internal remediation backlog.

Documents, mobile apps, videos, third-party widgets, multiple roles, authenticated areas, languages, and user research can each sit inside or outside the quote. Missing scope detail can make a low price describe a smaller product.

Normalize the quote

Put every provider on the same request.

A comparable quote has a frozen scope version and an accountable owner for every unresolved assumption.
FieldRecord before requesting a priceWhy it changes the result
PurposeProcurement evidence, release gate, remediation plan, complaint response, or monitoringThe reporting depth and independence differ
TargetExact WCAG version and level, BITV test, contractual standard, or other requirementWCAG 2.1, WCAG 2.2, BITV, and customer criteria are not interchangeable labels
Product boundaryDomains, web app, mobile app, authenticated roles, documents, media, and languagesAn excluded product cannot be covered by the result
Representative sampleTemplates, components, page states, random sample, and selection ownerA provider-selected publishable test differs from a client-selected internal sample
Complete processesSignup, login, search, booking, application, checkout, payment, errors, and confirmationEvery process state may contain distinct barriers
Test matrixBrowsers, devices, keyboard, zoom/reflow, screen readers, and other assistive technologySpecific environments make results reproducible
ReportCriterion mapping, evidence, reproduction, severity, ownership, and permitted publicationA scanner export and an evaluation report support different decisions
Commercial boundaryTax, travel, licences, third-party access, remediation, documents, statement, retest, and change requestsHeadline price hides the largest exclusions
Comparable request

Build an accessibility audit request in eight steps.

Accessibility audit decision and report use
01

Name the decision

State what the report must support, who will rely on it, whether it may be published, and the review date. Do not ask for “a compliance certificate” without defining the authority and scope.

Accessibility target standard record
02

Set the target

Record the exact standard, version, level, legal or contractual reference, and any organisation-specific criteria. Keep legal interpretation with qualified counsel.

Digital product accessibility inventory
03

Map the product

Inventory domains, templates, components, states, roles, languages, documents, media, mobile surfaces, and third-party services before selecting samples.

Complete customer process states
04

Freeze complete processes

List the start, every state, error path, and completion point for login, search, booking, applications, checkout, payment, and other critical journeys.

Representative accessibility sample
05

Agree the sample

Record who selects representative and random samples, which states are included, what is excluded, and whether the result can support the intended statement.

Manual and assistive technology test matrix
06

Specify manual tests

List keyboard, focus, zoom, reflow, errors, content judgement, browsers, devices, screen readers, and any user evaluation. A tool name alone cannot define the method.

Accessibility finding evidence fields
07

Define the evidence

Require criterion, location, state, observed result, expected result, reproduction, environment, impact, evidence, owner, and retest criterion for each finding.

Accessibility audit commercial boundary
08

Price the boundary

Separate audit, remediation, retest, statement drafting, documents, captions, training, monitoring, tax, travel, third-party work, change control, and cancellation.

What tools can prove

A scan is useful evidence. It is not the verdict.

W3C’s guidance for selecting evaluation tools says tools cannot automatically check every accessibility aspect, require human judgement, and can produce false or misleading results. A fixed percentage of issues found would be indefensible. Automated coverage varies by tool, rule, technology, and content.

The current WCAG 2.2 Recommendation defines testable success criteria and conformance requirements. W3C advises WCAG 2.2 for future applicability, while WCAG 2.0 and 2.1 remain Recommendations. Your quote should name the required target instead of silently changing a contract, tender, or legal reference.

A useful report follows a declared method. W3C’s evaluation-report template includes scope, reviewers, tools and versions, manual review, results, recommended actions, and detailed criterion-level findings.

Compliance next step

Get a compliance check on: Accessibility audit cost

Send us where your site stands today. We reply with the risks that carry real exposure, not a generic checklist.

Name the regulation, the page, or the deadline you are working against.

By submitting you agree to our privacy policy.

BFSG applicability

The BFSG does not make every German website the same legal case.

German BFSG § 1 lists the covered products and consumer services. The EU summary of Directive 2019/882 likewise names categories including e-commerce, consumer banking, e-books, electronic communications, and parts of passenger transport.

BFSG § 2 defines a microenterprise as employing fewer than ten people and having either annual turnover or an annual balance-sheet total no greater than €2 million. BFSG § 3 exempts microenterprises that provide services from its accessibility duty. Covered products require a separate assessment because the exception has a narrower reach.

The official BMAS microenterprise guidance gives examples for e-commerce and appointment booking. Use those sources to frame a question for counsel. An accessibility audit tests the agreed digital scope; it does not decide every legal fact about your business.

Before accepting a quote

A quote is ready to compare when it records:

Source URL, issue date, validity period, currency, tax basis, and contracting entity.
Purpose, audience, publication rights, legal or contractual target, and evidence limitation.
Product boundary, technologies, roles, languages, documents, media, and third-party systems.
Representative and random sample logic, selected states, complete processes, and exclusions.
Manual test matrix, assistive technologies, browsers, devices, tool versions, and evaluator roles.
Finding fields, severity method, code guidance, delivery format, review meeting, and data handling.
Remediation ownership, retest scope, regression treatment, acceptance criteria, and unresolved findings.
Statement drafting, documents, captions, training, monitoring, expenses, tax, change control, and exit.
Common questions

Accessibility audit cost questions, answered without a false range.

How much does an accessibility audit cost in Germany?

There is no audited national average in the sources reviewed. BIK publishes an indicative page-and-complexity model and a worked €4,200 net seven-page example plus an example €250 base amount. Other providers publish packages from €195, €490, and €2,480 net, but their definitions differ. Compare one frozen product boundary, sample, manual test matrix, report, exclusions, and retest.

Can an automated scan prove WCAG compliance?

No. W3C says tools cannot check all accessibility aspects automatically and cannot determine accessibility on their own. Use scans for repeatable machine-testable rules, then document knowledgeable human evaluation of the agreed pages, complete processes, content, and interaction.

Does a sampled audit prove the whole website conforms?

Usually not. WCAG-EM 2.0 says a conformance claim for an entire website cannot be based on a selected subset alone because other errors may remain. The report should say exactly what was sampled, what complete processes were evaluated, and what conclusion that evidence can support.

Should the audit target WCAG 2.1 or WCAG 2.2?

Use the version required by the applicable law, tender, contract, or policy. WCAG 2.2 is the current W3C Recommendation and W3C advises using it for future applicability, but WCAG 2.0 and 2.1 remain Recommendations. Preserve every explicit requirement.

Are remediation and retesting included?

Only if the quote says so. Separate audit findings from code and content remediation, third-party fixes, documents, captions, statement drafting, retest, and regression checks. Define what happens when a fix changes the sample or exposes another barrier.

Does the BFSG apply to our website?

That depends on the covered product or consumer service, business facts, exceptions, and transition rules. BFSG §§ 1–3 and the official BMAS guidance are the starting points. A technical audit can test an agreed digital scope, but legal applicability should be confirmed with qualified counsel.

Some Tech Work scope

We quote the evidence boundary before testing.

Some Tech Work does not publish an unapproved universal accessibility-audit price. Our proposal names the target, product boundary, representative states, critical processes, test environments, manual checks, report fields, exclusions, and retest. That lets your team compare the work before comparing the number.

The accessibility audit service covers technical evaluation and a remediation-ready record. The proposal lists implementation, content work, documents, legal interpretation, and independent user research separately. For broader applicability context, use the EAA guide.

Start here

Ready to talk.Book a short diagnostic.

Tell us what needs fixing

A process, a tool, a decision that's stuck. One sentence is fine.

By submitting you agree to our privacy policy.

We read every brief and reply within one business day.

Prefer to talk first?or request a tech stack audit or email us directly

Not sure where to start? Send the stuck decision, workflow, or page. We will say whether you need a diagnostic call, a tech stack audit, or a different first step.