All-round — what we do, what you do
We test your website, prepare the corrections and test again. Your share of the work is smaller than you might expect — but it is not zero, and it is set out here in full.
The offer at a glance
- Price — from €99 per month, graduated by annual turnover, excl. VAT
- Standard applied — EN 301 549 V3.2.1, which refers to WCAG 2.1 Level AA
- Test interval — the home page weekly, all discoverable pages every 14 days, up to eight
- Your effort — approve the order, answer a list of questions, have the patch sheet installed
- Access to your system — normally none — the default route is the installation template
- Test mark — included, once no machine-detectable finding is left open
- Term — cancellable monthly, no setup fee
What happens after you order
Nine steps. The timings count working days from receipt of the order; where a timing depends on your answer, it says so.
- 01 · minute 1
Initial scan
We open your home page and follow its links to contact, legal notice, privacy, terms, basket, sign-in and a product page — up to eight pages. No address is guessed: anything that is not linked counts as not found and is reported as such.
- 02 · day 1
Test report
Every finding with its success criterion, location in the code, severity and effect on use. Anything that sits in the header or footer of every page is counted once and noted as “on N of M pages” — otherwise the report would be three to four times longer without saying more.
- 03 · days 1–3
Correction proposals
For each finding, the code before and after, with the reasoning and the success criterion. Across 19 tested domains with 794 findings in total, 83.8 % received a ready-made code proposal.
- 04 · days 1–3
List of questions
The points nobody but you can decide — above all alternative texts for images. In the same measurement that was 16.2 % of findings. You get them as one list with file name, location and link target, not scattered across the report.
- 05 · after your answer
Patch sheet
The complete installation template: before, after, reasoning, success criterion, location. The same sheet is also your change log.
- 06 · days 3–10
Installation
By one of the four routes in the next section. The default route is that you or your agency install the patch sheet — we do not touch your system.
- 07 · straight afterwards
Re-test
A second scan of the same pages, compared finding by finding: fixed, open, new. This also catches installation errors that would otherwise surface on your side.
- 08 · once clear
Test mark
If no machine-detectable finding is left open and the conditions below are met, you receive the test mark and a public test page that it links to.
- 09 · ongoing
Continued testing
The home page weekly, all pages every 14 days. Every new finding arrives as a notification with success criterion and location.
What you have to do: the four installation routes
Between the finished correction proposal and your website sits one step no software takes off your hands: somebody has to install the change in your system. There are four routes. We recommend one, and one we cannot offer you at present.
| Route | What you do | What we do | Status |
|---|---|---|---|
| Installation templateroute D | you or your agency install the patch sheet | template, list of questions, re-test | recommended |
| Files back and forthroute A | export the affected templates or theme files and send them | we change them and send them back | on request |
| Git accessroute C | grant read access to the repository and a branch of our own | we supply a pull request; merging and deploying is yours | on request |
| Access to your live systemroute B | create a separate account in your shop system | we change things directly in the running system | currently closed |
The rows are ordered by decreasing recommendation, not by convenience. For website builders without file access, only the first route is realistic.
Why the template is the default route. It needs no access to a system holding orders, accounts and addresses. That removes processing on behalf of a controller under Art. 28 GDPR, it removes the risk of breaking something else in a running shop, and acceptance stays with you — which is also where the duties under the European Accessibility Act sit.
Why access to your live system is currently closed. Anyone changing something in a running shop can take it down, and a shop that stands still for a day has a quantifiable loss. We currently hold no professional indemnity insurance for that case. A liability clause in terms and conditions is no substitute for cover — and liability for intent and gross negligence cannot be excluded anyway. As long as the insurance is not in place we do not accept access to a live system, even if you offer it. The moment that changes, it will say so here.
What we need in every case. A written order naming which system, which scope and which period it covers. That is not a formality: nobody may work on someone else's system without documented permission. Where a route with system access does come into question, a data processing agreement, a backup before every change and withdrawal of the access after acceptance are part of it.
And your attention for the list of questions. We do not invent an alternative text for an image. Anyone who has not seen the image cannot describe what is on it, and a wrong alternative text is worse than none: it makes the finding disappear without removing the barrier. Depending on the number of images, allow twenty minutes to an hour — once, not recurring.
What you get and when
| Service | Form | When |
|---|---|---|
| Test report | HTML report by e-mail | on the first working day after ordering |
| Correction proposals | per finding, code before and after | days 1 to 3 |
| List of questions | one list with file name, location and link target | days 1 to 3 |
| Patch sheet for installation | template with reasoning and success criterion | after your answer to the list of questions |
| Change log | what was changed, when and why | together with the patch sheet |
| Re-test | second scan comparing fixed / open / new | immediately after installation |
| Test mark and public test page | image file under your identifier, test page with the findings | as soon as the conditions are met |
| Accessibility statement | text naming the success criteria from your findings | once, kept up to date afterwards |
| Ongoing testing | short test and full test compared with the previous run | weekly and every 14 days |
| Test log | list of all tests with date and result | at any time; at the end of the contract as an archive copy |
What is not included
This is not in the small print but here — it is the reason the rest can be believed.
Automated testing covers roughly one third of the criteria. What remains untested includes keyboard operability of the checkout, focus visibility, reading and tab order, whether alternative texts are factually right, whether error messages are understandable, and captions in videos. A report without findings is therefore no proof of accessibility, and the report says so.
The checkout stays out of scope. We open the basket but do not fill it. The ordering process is the most delicate part of a shop and is not tested at present.
We do not click consent banners away. An automated click on “Accept” would be a declaration of intent in your name. Where a banner covers content, the number of findings is more likely too low than too high — and we note that in the report as well.
No legal advice and no statement about your legal position. We are a private testing service — not an authority, not a notified body, not a law firm. We tell you what we measured and against which standard. Whether your website meets the legal requirements is not something we state: neither for you nor against you. A clean bill of health would be just as much a legal judgement as an accusation.
No overlay. We do not install a script meant to produce accessibility at runtime. Such tools have been declared unsuitable by the German monitoring bodies; their use is now taken as an indication that the requirements are not met.
No rebuild and no design work. We change what was found. A new visual identity, new content or restructuring your site is not part of the offer.
When you get the test mark
The test mark carries exactly one statement: “Tested regularly against EN 301 549” plus the test date. It does not say “accessible”, “certified”, “legally compliant”, and least of all “officially recognised”. These six conditions have to be met at the same time:
- A running test contract. A quality mark may not be displayed without recurring re-testing — that is not a clause of ours but the condition under which it is permitted at all.
- At least four pages of your domain actually tested, among them the home page and at least one page with a form.
- No open, machine-detectable finding — of any severity. No point scores, no traffic light with an amber award.
- At most three documented exceptions, for findings whose cause demonstrably lies outside your control, such as a third-party payment frame, a map service or a third-party ad slot. Each is named on the public test page, none may be critical, and each expires after twelve months.
- An accessibility statement and a way to report barriers are reachable on your website.
- No accessibility overlay in use. Such scripts change the page at runtime and therefore distort the test result.
The threshold is reachable. In the test run of 21 Aug 2026, one of eight tested shops stayed at zero findings across seven pages, with 206 checks passed.
If a later test finds something new, the mark stays visible for the time being and the public test page names the open points with a deadline: 14 days for critical or serious, 30 days for moderate or minor, 60 days where the cause lies in third-party content. Once the deadline passes, the mark is suspended. The same happens automatically if the test date is more than 45 days old — including when the failure is on our side.
The full award rules are public on this website — conditions, deadlines, presentation rules and the limits of the method. Any change to them is announced 30 days in advance.
How long it takes
A scan across eight pages takes 20 to 30 seconds. Measured on 21 Aug 2026 across eight shops and 49 pages: 211 seconds in total, around 4.3 seconds per page. The first findings are there before you close the browser.
The correction work is shorter than the number of findings suggests, because much of it is done in a single move: one colour value in a CSS variable fixes every finding with the same colour pair, and removing one class cleared 42 findings at once in one of the tested shops. That turned 794 findings across 19 domains into 284 separate decisions. For a typical shop that is 25 to 45 minutes of work on the file.
How long the installation itself takes depends on your system and your agency. That is the one step we do not control — and therefore the only one with no figure here.
How to cancel — and what then happens to the test mark
Monthly, to the end of the billing month, informally in text form. No minimum term, no setup fee, no call-back designed to change your mind.
- The test mark expires on the last day of the term. No run-out, no residual period — without re-testing it may not continue to be displayed.
- For locally copied embeds you have five working days to remove them.
- After that, the image address permanently serves a neutral graphic instead of an error. A broken image on your page explains nothing to anybody.
- Your test page stays online for twelve months as an archive copy, clearly marked: “Testing ended on DD.MM.YYYY — not a valid mark”. That is your evidence of continuous effort in case of an inspection. At your request we delete it earlier.
- The corrections stay in your website. We roll nothing back and reclaim nothing.
Watch service or All-round — what is in each package
Both offers test the same thing, against the same standard, at the same intervals. The difference is who works through the findings.
| Service | Watch service | All-round |
|---|---|---|
| Initial test against EN 301 549 / WCAG 2.1 AA, up to eight pages | yes | yes |
| Test report with success criterion, location and remediation note | yes | yes |
| Weekly short test of the home page | yes | yes |
| Full test of all discoverable pages every 14 days | yes | yes |
| Notification as soon as new findings appear | yes | yes |
| Test log as evidence of continuous effort | yes | yes |
| Accessibility statement | template, once | kept up to date |
| Correction proposal per finding, before and after in the code | no | yes |
| List of questions for the points only you can decide | no | yes |
| Patch sheet for installation, doubling as a change log | no | yes |
| Re-test after installation: fixed, open, new | no | yes |
| Test mark with a public test page | no | yes, once the threshold is met |
| Price per month, graduated by annual turnover | from €19 | from €99 |
Both cancellable monthly, excl. VAT, no setup fee. What is in neither offer is set out on both pages under “What is not included” — in the same place as everything else, not in the small print.
Read on
Watch service in detail
The smaller offer: the same testing at the same intervals, without remediation and without a test mark.
Pricing
Three tiers by annual turnover, openly published, without a sales call.
What accessibility costs
Four cost blocks, the market prices of 25 Aug 2026 and why the ranges are so wide.
Findings first, decision second
The scan costs nothing and takes half a minute. Only once you know how much there is to do is it worth talking about price.