Audits
Accessibility retainers for agencies: what to scope, monitor and report
How to scope an accessibility retainer: what to audit once, what to re-check on a schedule, what each client report needs, and what a tool can't promise.
An accessibility retainer is a standing agreement to keep a client’s site accessible after the first audit, while the site keeps changing. Scope it in five main parts: one baseline audit, scheduled re-checks of each page template, manual testing that no scan can replace, checks when a release changes the site, and a monthly report the client can act on. The contract then says what the retainer does not promise.
Below is each part, a scope table to adapt, an outline for the monthly report, and the contract terms that keep both sides honest.
A baseline accessibility audit starts the retainer. This post is about what comes after it.
Why one audit is not enough
An audit describes the site on the day it was tested. After that, developers release, editors publish pages and upload images, marketing adds a chat widget, and a design-system update changes a button used on hundreds of pages. Any of these can bring back a failure the audit closed, or add a new one.
For a client covered by the European Accessibility Act, keeping up is part of the law. Article 13(3) says service providers must have procedures in place so that the service “remains in conformity” with the accessibility requirements, and must take into account changes to the service, to the requirements and to the standards. In the Act’s text, the duty sits with your client, as the provider of the service: the Act places no obligation of its own on the agency that builds the site, so yours is whatever your contract says. Microenterprises providing services, those with fewer than 10 staff and no more than €2 million in annual turnover or balance sheet total, are exempt from the Act’s requirements for services (Articles 3(23) and 4(5)). See what the Act asks of a website, and check the national law that applies to your client.
For a public-sector client, the Web Accessibility Directive requires an accessibility statement that is “regularly” updated (Article 7(1)), and the Commission’s model statement (Implementing Decision (EU) 2018/1523) encourages a review at least once a year.
Neither the Act, the Directive nor W3C sets how often a site must be re-tested. W3C’s evaluation method says an evaluation may be re-run after fixes or “periodically to monitor progress”, and leaves the interval to you. Set it with your client, from how often their site changes.
A retainer is not a promise that the site conforms, and it is not a script or widget added to the page. Fixes go into the site’s own code and content.
The scope at a glance
Each row is a separate piece of work with its own trigger. Put the table in the contract annex and change the intervals to fit the site.
These intervals are a starting point, not a rule. Shorten them for a site that releases every week, and lengthen them for one that rarely changes.
Start with a baseline audit
Every later report is compared with the baseline, so it has to be a full audit, not a scan. W3C’s WCAG Evaluation Methodology (WCAG-EM 2.0, a W3C Group Note of July 2026) gives the method in five steps: define the scope, explore the site, select a sample, evaluate it, and report.
- A structured sample. Pages that cover the common views, the essential functionality, each type of page and each technology the site relies on.
- A random sample on top. 10% as many pages again, chosen at random, to show whether the structured sample missed anything.
- Complete processes. Every step of a process such as checkout. Under WCAG 2.2, a page in a process conforms only when every page in the process does (conformance requirement 5.2.3).
- A target. WCAG 2.2 Level AA, unless the client’s law or contract names another standard or version.
Write down what the baseline did not test: states such as errors and open menus, the browsers and the assistive technology used, and any part of the site left out. A monthly report can only say what changed against what was recorded. For budgeting, see what drives the price of a baseline audit.
Re-check by template, not by page count
A site is usually built from a handful of templates and shared components. A failure in the product-page template’s code repeats on every product page, and fixing the template fixes it on all of them. A retainer that promises “500 pages a month” measures the wrong thing. One that lists the templates and components, and re-checks a page of each, finds what changed in the code.
- Keep the template list in the contract annex. Add a template when one appears, and retire it when it goes.
- Re-check the shared components too: the header, the navigation, form fields, dialogs and the consent banner.
- One page per template finds most failures in the shared code. It will not find a missing alt text on one article, which is why the content spot check is a separate line in the scope.
Our guide to finding a site’s templates and choosing one page for each covers the sampling in detail.
What a scan cannot check, so the retainer must
W3C’s guide to choosing evaluation tools is plain about the limit: “Web accessibility evaluation tools can not determine accessibility, they can only assist in doing so.” A tool measures. A person judges.
- A tool can decide whether an image has a text alternative, whether most text meets a contrast ratio, and whether a field has a label in the markup. It can also measure a target’s size and spacing.
- A person decides whether that alt text describes the image, whether headings and labels make sense, whether an error message says how to fix the problem, whether focus moves in a sensible order, and whether captions match the speech.
- Only a person can complete a journey with a keyboard and a screen reader, and notice that the checkout cannot be finished.
Plan manual hours into every quarter, spent on the complete processes rather than on single pages. See which A and AA criteria a tool can decide before you price the split.
Testing with people with disabilities can find problems an expert review misses. W3C’s page on involving users says such evaluation “identifies usability issues that are not discovered by conformance evaluation alone”, and WCAG-EM 2.0 strongly recommends it, though it does not require it. Offer it as a named line in the retainer, even if only once a year.
Releases, components and editors
A schedule catches drift. Some changes deserve a check when they happen:
- a new template, or a redesign of an old one;
- a change to a shared component, such as the navigation, a form field or a dialog;
- a new third-party script: chat, booking, payment or consent;
- a CMS change that alters what editors can insert.
If you build the site, run accessibility checks in CI so a failure stops the release before visitors meet it. The scheduled re-check still matters: it sees the live site, including third-party scripts and editors’ content, which the build never sees.
Third-party content counts. WCAG 2.2 says conformance is for full pages only, and “cannot be achieved if part of a web page is excluded” (conformance requirement 5.2.2). When an embedded booking widget fails, record it, tell the client who can fix it, and say whether you have contacted the vendor. WCAG lets the author of such a page make a statement of partial conformance, but the statement itself says the page does not conform.
Editors make many of the changes on a content site. A short training session and a checklist for alt text, headings, link text and documents prevent failures that a re-check can only report once they are live.
The monthly client report
A client who reads only the summary should know what changed, what is at risk, and what they must decide. Everything else is the evidence behind it. The baseline and the yearly re-audit use the sections a full audit report needs; the monthly report records what changed since.
# Accessibility report: <site>, <month and year>## 1. Summary- What changed on the site this month- New: <n> Regressed: <n> No longer found: <n> Still open: <n>- Decisions we need from you## 2. What we tested- Templates re-checked, and the page used for each- Journeys tested by hand, and with which assistive technology- Screen sizes and browsers- Not tested this month, and why## 3. New and regressed findingsFor each finding:- Template and page- WCAG criterion, with its number and level- What fails, and the evidence (element, value, screenshot)- Severity, on the scale agreed in the contract- Who fixes it, and by when## 4. No longer foundFor each finding: the date of the re-check and the method used## 5. Still openFor each finding: owner, target date, and what is blocking it## 6. Third-party contentFailures in parts neither of us controls, and the vendor we contacted## 7. Next monthPlanned checks, expected releases, open questionsWrite “no longer found”, not “fixed”. A re-check shows that the failure is gone from what was tested, not that the fix works for everyone. Re-check with the method that found the failure: a problem a person found in a screen reader needs a person and a screen reader again.
Keep the counts honest. A month with more findings can mean more of the site was tested, not that it got worse, so the scope section matters as much as the numbers.
Size it by templates, journeys and releases
The effort in a retainer depends on how much there is to check, how often it changes, and who fixes it:
- the number of templates and shared components to re-check;
- the number of complete processes to test by hand, and with how many screen readers and devices;
- how often the site is released, and how many of those releases touch the interface;
- how much content editors publish each month;
- whether the retainer includes fixing, or only finding and reporting;
- whether you also support the client’s accessibility statement or Annex V information.
Price finding and fixing separately. You know the size of a re-check before you start; you do not know the size of a fix until the failure is found. A block of fixing hours, or an estimate per batch of findings, keeps the monthly fee predictable.
What the contract should say
- What is in scope: the template list, the journeys, the schedule, the report date, and the target standard with its version and level.
- Who fixes what: your team, the client’s developers, or a third-party vendor, for each part of the site.
- What is out of scope: platforms you cannot change, content the client’s editors publish beyond the spot check, and documents and media unless listed.
- How fast you respond to a regression: for example, a failure that blocks a complete process is triaged within an agreed number of working days.
- What “done” means: no longer found by the method that found it, with the date recorded.
- What the retainer does not promise: it reports what was tested and what was found. It is not a statement that the site conforms, or that the client meets the law. The client’s accessibility statement, or the Annex V information a service publishes, stays theirs to sign.
To see what an automated check reports on one of your client’s pages, scan one page free, without signing up. It covers one public page, so treat it as a first look, not a baseline.
Frequently asked questions
What should an accessibility retainer include?
A baseline audit at the start, scheduled re-checks of each page template and shared component, manual testing of complete processes with a keyboard and a screen reader, checks when a release changes the site, a content spot check, and a monthly report. The contract should also say who fixes what and what the retainer does not promise.
How often should a client's site be re-tested for accessibility?
Neither the European Accessibility Act nor the Web Accessibility Directive sets a frequency, nor do WCAG and W3C's evaluation methodology. Check your national law. One pattern is an automated re-check of each template every month, a manual journey test each quarter, and a full re-audit each year or after a redesign, plus a check whenever a release changes a template or a shared component. Adjust it to how often the site changes.
Can an accessibility retainer guarantee compliance?
No. A retainer reports what was tested and what was found, and fixes what the contract covers. It cannot establish that a site conforms to WCAG or that the client meets the law. Under the European Accessibility Act the duty to keep a service accessible sits with the service provider, your client, if the Act covers its service. Check the national law that applies.
Is an automated monitoring tool enough for a retainer?
No. A tool measures things such as missing labels, contrast ratios and target sizes, and re-checks them on a schedule. Whether alt text is accurate, whether an error message helps, and whether a checkout can be completed with a screen reader need a person.