An accessibility project fixes a defined set of WCAG issues at a point in time, while an accessibility retainer provides ongoing monitoring, remediation, and documentation required for sustained ADA Title II compliance.
When public agencies start getting serious about ADA Title II digital accessibility, one of the first decisions they face is how to structure the engagement with an outside partner.
Most agencies frame this as a procurement question. Do we hire someone for a project or do we bring on a retainer? What is the scope? What is the deliverable? What does it cost?
Those are reasonable questions. But they are downstream of a more important one that most agencies skip entirely.
What problem are you actually trying to solve?
If the answer is "we need to fix our website so it passes an accessibility audit," a project makes sense. That is a defined scope with a defined endpoint. Fix the issues, validate the fixes, close the engagement.
If the answer is "we need to demonstrate defensible ADA Title II compliance that holds up when a complaint arrives, survives staff turnover, and continues to function as our digital environment evolves," a project does not solve that problem. It addresses a snapshot of issues at a point in time. The problem you are trying to solve does not have an endpoint.
That distinction is the entire article. But it is worth unpacking carefully because the consequences of choosing wrong are significant and not immediately obvious.
What an ADA Accessibility Project Engagement Actually Delivers
A project engagement is scoped around a defined set of deliverables with a start date and an end date. In the accessibility context, a typical project looks something like this.
An agency contracts with an accessibility vendor or agency for an audit and remediation sprint. The vendor conducts an audit, produces a findings report, and then works through the identified issues over a defined period — six weeks, three months, whatever the scope allows. Templates get fixed. Form labeling gets addressed. High-contrast failures get corrected. PDFs get remediated. At the end of the project, a remediated website is delivered and the engagement closes.
That is a legitimate and valuable thing. A well-executed accessibility project produces real improvements that reduce real barriers for real residents. It is not nothing.
What it is not, is a compliance program.
Here is what happens in the twelve months after a typical accessibility project closes.
Content editors continue publishing. Dozens of new pages go up, new PDFs get uploaded, new event registrations get embedded. None of it goes through an accessibility review because the project is over and there is no ongoing process in place.
Vendors update their tools. The payment gateway gets a platform update. The permit portal vendor releases a new version. The GIS tool gets a UI refresh. No one tests any of these updates for accessibility regressions because there is no monitoring program running.
Templates get modified. A developer adds a new feature. A CMS update changes markup behavior in ways no one anticipates. A new plugin gets installed. Each of these events is a potential regression that goes undetected without monitoring.
Staff turns over. The web manager who understood the accessibility standards and could apply some informal judgment to new work moves on. Their replacement has no accessibility training and no documented standards to work from.
Twelve months after the project closed, the agency's accessibility posture has regressed significantly. Not because anyone was negligent. Because the digital environment is a living system and a project is not.
What a ADA Accessibility Retainer Engagement Actually Delivers
A retainer engagement is scoped around an ongoing relationship rather than a defined deliverable. In the accessibility governance context, a retainer provides the continuous operational coverage that sustains compliance over time.
What a well-structured accessibility governance retainer includes:
Continuous monitoring. Monthly automated scans with human review of findings. Quarterly manual QA of core transactional workflows. New issues are caught through monitoring rather than through complaint. Regressions introduced by content updates, vendor changes, and template modifications are identified and addressed before they accumulate.
Ongoing remediation capacity. A defined allocation of remediation work per month — developer hours, document remediation, vendor coordination — that ensures the remediation queue keeps moving rather than stalling between project cycles. New issues identified through monitoring get fed directly into the remediation workflow.
Documentation and log maintenance. The remediation log stays current. Every issue identified, every fix made, every validation confirmed — documented with timestamps, WCAG criterion references, and risk classifications. The documentation record grows continuously rather than being built once and abandoned.
Executive reporting. Quarterly accessibility status reports prepared and delivered to agency leadership. The reports give leadership a consistent, credible picture of compliance posture, risk trends, and remediation progress. Leadership is informed before questions arrive from outside.
Vendor oversight. VPATs reviewed as part of procurement decisions. Embedded vendor tools tested after major updates. Vendor-related accessibility issues tracked and escalated through the documented channels that give the agency contractual leverage.
Content and development standards support. Accessible content guidelines maintained and distributed. Accessibility review available for new features and templates before they go live. The standards that prevent new issues from being introduced are kept current and enforced.
Governance framework maintenance. The accessibility policy stays current. Ownership is defined and documented. Training is delivered to new staff. The governance structures that make the program person-independent rather than person-dependent are maintained over time.
The output of a retainer is not a deliverable. It is a compliance posture that is continuously maintained, documented, and defensible.
The Defensibility Gap Between Projects and Retainers
The most important practical difference between a project engagement and a retainer engagement is what each one produces in terms of defensibility documentation.
A project produces a point-in-time deliverable. An audit report dated to a specific moment. A set of fixes validated at the close of the engagement. If the project was done well, it produces a strong baseline. But the baseline ages. Twelve months after the project, the baseline no longer accurately reflects the agency's current compliance posture — and there is no documentation of what has happened in the intervening period.
When an enforcement inquiry arrives twelve months after a project-only engagement closed, the agency can show an old audit report and a completed remediation project. What it cannot show is any evidence that the compliance posture has been maintained since the project ended. The monitoring records do not exist. The remediation log has no entries after the project close date. The executive reporting history is blank.
The enforcement narrative that the documentation tells is: this agency did something about accessibility once, and then stopped.
That is not good faith compliance. That is a past project.
A retainer produces a continuous documentation record. The audit establishes the baseline. The monthly monitoring records show the cadence of evaluation. The remediation log grows with every issue identified and addressed. The executive reports create a timeline of sustained organizational attention. The vendor review records show that the compliance scope extends to the full digital ecosystem.
When an enforcement inquiry arrives twelve months into a retainer engagement, the agency can produce a complete, organized, timestamped record of a compliance program that has been actively running. The narrative the documentation tells is: this agency built a real program and has been maintaining it.
That distinction — between a past project and an active program — is the difference between a defensible compliance posture and a vulnerable one.
When a Project Makes Sense
Projects are not the wrong answer for every agency situation. There are circumstances where a project engagement is the appropriate starting point and where it creates genuine value.
When you have never had a formal audit. If your agency has no documented baseline of its accessibility posture, a project engagement that delivers a comprehensive audit and initial remediation is a legitimate first step. It gives you the baseline that everything else is built from. The critical thing is not to treat the project as the compliance program — treat it as the foundation that a governance program is built on top of.
When you have a specific, bounded remediation need. If your agency recently completed a website redesign and needs accessibility review and remediation of the new build before launch, a project engagement makes sense. The scope is defined. The deliverable is specific. The project serves a clear purpose.
When budget constraints make a full retainer impractical in year one. A phased approach — project in year one to establish the baseline and address highest-risk issues, retainer starting in year two to sustain and govern — is a reasonable path for agencies working within tight fiscal constraints. The important thing is having an explicit plan to move from project to governance rather than treating the project as sufficient.
When you need to demonstrate immediate progress to leadership. An audit-and-remediation project produces visible, concrete deliverables that are easier to present to leadership than a governance retainer. In some organizational contexts, demonstrating tangible output from a defined project is the political path that creates the budget authorization for an ongoing program. Use that strategically.
When a Retainer Is the Right Structure
A retainer is the right structure when an agency's goal is ongoing defensibility rather than a one-time improvement.
When you have already completed an initial remediation project. If your agency has done the baseline work — audit, initial remediation, governance framework — the natural progression is to sustain that work through an ongoing engagement. A retainer picks up where the project leaves off and prevents the regression that otherwise occurs.
When your digital environment is complex or high-volume. Agencies with multiple departments publishing independently, large vendor portfolios, significant document volume, or multiple subdomains and microsites have too much complexity for a project-only approach to sustain. The surface area is too large and changes too quickly for a point-in-time project to provide durable coverage.
When leadership has made compliance a stated organizational priority. When accessibility has executive attention — when city managers or county administrators are asking about compliance posture, when legal counsel is engaged, when council or board members are raising questions — the organization needs ongoing defensibility documentation, not just a completed project. A retainer is the structure that produces that documentation continuously.
When your agency has experienced a complaint or enforcement attention. If your agency has received an accessibility complaint, a demand letter, or any form of enforcement attention, the appropriate response is not a remediation project. It is a governance program with complete documentation. A retainer structure provides that program.
When you cannot afford the cost of reactive compliance. The financial argument for a retainer over repeated projects is straightforward. A planned, ongoing governance program costs significantly less over a three-to-five year horizon than the cycle of audit, project, regression, re-audit, project that characterizes a project-only approach — and dramatically less than the emergency remediation, legal engagement, and potential consent decree costs triggered by enforcement action.
The Questions That Reveal Which Structure You Need
If you are trying to determine which engagement structure is right for your agency's current situation, these questions clarify the answer.
Can your agency demonstrate ongoing compliance today? Not a completed project. Not an old audit. Ongoing, current, documented compliance with a monitoring record and a remediation log that shows activity in the last 30 days. If the answer is no, a retainer is what creates that capability.
What happens to your compliance posture when your web manager is out for two weeks? If the answer is "nothing, because the monitoring runs on a schedule and the log gets updated as a matter of process," you have a governance program. If the answer is "things probably fall behind," you have a person-dependent situation that a retainer with an external governance partner is designed to solve.
What would you produce if asked today for your compliance documentation? An old audit report and a memory of fixes that were made? Or a current audit, a timestamped remediation log, monthly monitoring records, and quarterly executive reports? The answer tells you whether you have a documentation program or a documentation gap.
Is your compliance posture improving, stable, or regressing? If you are not monitoring, you cannot answer this question. If you cannot answer this question, you cannot manage the risk.
Project or Retainer: The Practical Decision Framework
Here is the simple way to think about it.
If your goal is to fix a specific set of accessibility issues identified in an audit, a project is the appropriate vehicle for that work. It has a defined scope, a defined deliverable, and a defined end point.
If your goal is to demonstrate defensible ADA Title II compliance that holds up under scrutiny, sustains through staff turnover, keeps pace with a changing digital environment, and produces the documentation record that good faith compliance requires, that is not a project. That is a program. And programs require retainers.
Most public agencies that have been around the accessibility conversation for any length of time have already learned the project lesson. They completed a project. They watched the compliance posture regress. They completed another project. The cycle is expensive, frustrating, and never-ending.
The retainer breaks the cycle by making compliance a continuous operational function rather than a periodic emergency.
That is the difference. Not the cost structure. Not the contract length. The nature of the problem being solved.
What Hounder's ADA Web Governance Program Provides
The Hounder ADA Web Governance Program is a retainer-based ongoing compliance program designed specifically for public agencies and higher education institutions that need defensible, sustained accessibility governance rather than a one-time project.
It includes continuous monitoring, ongoing remediation capacity, full documentation and log maintenance, quarterly executive reporting, vendor oversight integration, and governance framework maintenance — the complete operational infrastructure for a compliance program that produces defensible documentation every month it runs.
It is not the right fit for every agency. If what you need is a baseline audit and initial remediation project, that is where to start and we can help with that too.
But if what you need is a compliance program that holds up, a retainer is the structure that makes that possible.
[Learn more about an accessibility remediation log →]
[Learn about good faith compliance →]
FAQ: Project vs. Retainer for ADA Accessibility
What is the difference between an accessibility project and an accessibility retainer? An accessibility project is a defined engagement with a specific scope, a set of deliverables, and an end date. It typically includes an audit, remediation of identified issues, and validation of fixes. An accessibility retainer is an ongoing engagement that provides continuous monitoring, remediation capacity, documentation maintenance, and governance support over time. A project produces a point-in-time improvement. A retainer produces a continuously maintained compliance posture. Public agencies that need defensible ADA Title II compliance — not just a completed project — need a retainer structure.
Can a one-time accessibility project satisfy ADA Title II requirements? A one-time project is not sufficient for ongoing ADA Title II compliance. The DOJ evaluates whether agencies have documented, sustained compliance programs — not whether they completed a remediation project at some point in the past. A project that is not followed by ongoing monitoring, documentation, and governance will regress as new content is published, vendor tools are updated, and templates are modified. Most agencies that rely on project-only approaches find themselves in repeated remediation cycles that are more expensive over time than a sustained governance program.
How much does an accessibility retainer cost compared to a project? Project costs vary widely based on site size, issue volume, and scope of remediation. Retainer costs depend on the services included and the complexity of the agency's digital environment. Over a three-to-five year horizon, a well-structured retainer program is typically less expensive than the repeated audit-project-regression-re-audit cycle that characterizes a project-only approach — and dramatically less expensive than the emergency remediation and legal costs triggered by enforcement action. The retainer also produces the documentation record that reduces legal exposure, which has financial value independent of the direct cost comparison.
When should a public agency start with a project before moving to a retainer? A project-first approach makes sense when an agency has no existing audit baseline and needs a foundation to build from, when a specific bounded remediation need exists such as a new website launch, or when budget constraints make an immediate full retainer impractical. The critical requirement in a project-first approach is an explicit plan to transition to a retainer-based governance program after the project closes. Treating a project as the compliance program — rather than as the foundation for one — is the most common mistake agencies make in their accessibility journey.
What does an ADA accessibility retainer typically include? A well-structured ADA accessibility retainer includes monthly automated monitoring with human review of findings, quarterly manual QA of core transactional workflows, ongoing remediation capacity to address issues as they are identified, continuous remediation log maintenance with timestamped entries, quarterly executive reporting, vendor accessibility oversight including VPAT review and post-update testing, accessible content and development standards support, and governance framework maintenance. Together these components provide the continuous operational coverage that sustains compliance and produces the documentation record that defensible compliance requires.
What happens to compliance posture when a retainer ends? When a retainer engagement ends without a transition plan, the compliance posture begins to regress at the rate at which the digital environment changes — which in most public agencies is continuous. New content introduces new issues. Vendor updates introduce regressions. Template modifications create accessibility failures. Without monitoring, these changes go undetected. Without an active remediation program, identified issues are not addressed. Without log maintenance, the documentation record stops growing. A retainer should not be ended without either a clear transition to an internal governance program with equivalent capabilities or a plan to resume the retainer at a defined point.