A defensible ADA compliance program is a structured, documented accessibility governance system that combines auditing, remediation, training, monitoring, and executive oversight over time.
The DOJ extended the ADA Title II compliance deadlines by one year. Larger entities now have until April 26, 2027. Smaller entities and special districts have until April 26, 2028. The news analysis — what changed, what did not, and the first moves to make — we covered in full when the Interim Final Rule dropped.
This article is the next question. The one every agency is asking right now.
"We have the additional time. What do we actually do with it?"
The honest answer is: the exact same work. Just differently paced, differently resourced, and with a materially better chance of producing a compliance program that holds up under scrutiny instead of a frantic last-minute remediation sprint that produces a snapshot of conformance and no durable governance.
That is the difference between agencies that will come out of 2027 in a strong position and agencies that will come out of 2027 and 2028 in the same scrambling posture they would have been in under the original timeline — just twelve months later.
This guide is the playbook for the first group. A phase-by-phase plan for using the extended runway to build something defensible. Not a list of the five things to do tomorrow. A twelve-to-twenty-four-month structural plan that turns a regulatory extension into a compliance program that actually works.
The Two Ways to Waste an Extension
Before the playbook, a clear articulation of the two failure modes that this extension creates. Both of them are happening right now in agencies across the country.
Failure Mode 1: The Stall
The extension arrives. Leadership interprets it as relief. The accessibility line item in next fiscal year's budget gets quietly reduced or deferred. The procurement conversation that was about to happen gets pushed. The RFP language about accessibility gets softened because the pressure eased. Staff who were preparing to take accessibility training quietly stop hearing about it. The project that was going to kick off in May gets rescheduled to fall. Then to next year.
Twelve months later, the agency is in exactly the same position it was when the extension was announced. Except now it has eleven months until the new deadline instead of twenty-three.
The stall is the single most predictable response to this extension and the single most damaging one.
Failure Mode 2: The Perpetual Planning
The other failure mode. The agency does not stall. It plans. And plans. And plans.
Discovery meetings. Vendor demos. Scoping conversations. Internal alignment sessions. Draft plans that get revised. Governance framework designs that get escalated. Budget presentations that get requested. All of it productive-feeling. None of it producing actual compliance progress.
Twelve months later, the agency has a beautiful multi-phase accessibility roadmap document. And zero remediated PDFs, zero vendor tools audited, zero training completed, zero documented progress. The work is all still ahead. The runway is shorter.
The perpetual planning failure is what happens when the extended timeline removes the forcing function that would have made the agency choose action over deliberation.
The playbook below is designed to prevent both.
Why the ADA Extension Creates Capacity, Not Delay
The value of an extension is not that there is more time to do things. It is that there is enough time to do them well, with proper capacity allocation, without crashing them into the calendar.
A twelve-month compliance sprint under the original deadline required an agency to compress baseline auditing, remediation prioritization, vendor governance, training rollout, and documentation into a timeline where every phase overlapped and every handoff was rushed. It produced compliance theater at best and unfinished programs at worst.
A twenty-four-month runway under the extended deadline allows each phase to happen in sequence with meaningful time for testing, adjustment, and absorption between phases. Staff can absorb training before they are expected to apply it. Remediation can be validated before the next tranche is queued. Vendor conversations can result in actual remediation commitments rather than contract language that was never exercised.
The extension is not a reason to take longer to do the same work. It is an opportunity to do the same work correctly rather than frantically. That is the reframe that has to land before the playbook matters.
Phase 0: The First 60 Days After the ADA Deadline Extension
Every phase below assumes the agency has done the positioning work first. If you are reading this and any of the following items are not in place, start here. This is the foundation the rest of the playbook rests on.
Update every public-facing reference to the compliance deadlines. Your accessibility statement, your website's accessibility page, any published compliance commitments, any internal documentation referencing April 24, 2026 or April 26, 2027 as target dates. Update them to the new dates with a note explaining the DOJ extension. This is a credibility marker. An accessibility statement that still lists the old deadline as of July 2026 signals either inattention or avoidance.
Name the program owner. One person, accountable for the program, empowered to make decisions. This role may also be the agency's Title II ADA coordinator — in many agencies that makes sense. It may be a separate role. What cannot happen is a program with shared ownership that is nobody's clear responsibility.
Publish the governance commitment internally. An internal memo from the city manager, the district superintendent, the agency executive director — whoever holds the relevant authority — naming the program, naming the owner, describing the runway, and stating that resources will be allocated. This internal communication is what turns the accessibility program from a side project into an organizational priority.
Open the compliance documentation folder. A shared drive folder, a project management space, or equivalent. This is where every audit, every training record, every vendor communication, every remediation action will live. Start it now with the documents that already exist. It does not need to be populated before work begins. It needs to be the place where work is documented as it happens.
Set a quarterly review cadence. A one-hour meeting every quarter between the program owner and leadership to review progress. This is not a full project meeting. It is a governance checkpoint. The existence of a regular executive review is itself a piece of the defensibility story.
Sixty days into the extended runway, these five items should be complete. They are the positioning that makes every subsequent phase possible.
Phase 1: Baseline Accessibility Audit and Remediation Planning
This is the phase where the agency gets honest with itself about where it stands. Without a real baseline, every downstream decision is uncalibrated. This phase cannot be compressed and it cannot be skipped.
Commission the Professional Audit
Not an automated scan. Not a staff-run self-audit. A professional accessibility audit by a qualified third party that produces a WCAG 2.1 AA conformance report covering the full digital environment.
The audit scope needs to include:
The primary website — every significant page template and content type, not a sample of five pages. The transactional workflows — every form, application, payment portal, and service-delivery surface. The document library — a statistically valid sample of PDFs across categories, sufficient to characterize the library's overall accessibility status. The embedded third-party tools — every vendor platform integrated into public-facing services. Any subdomains, microsites, or separately branded digital properties operated by the agency.
The deliverable is a conformance report mapped to WCAG 2.1 AA success criteria, a risk-stratified list of findings, and a prioritized remediation roadmap with effort estimates.
This is not an optional step that agencies with tight budgets can skip in favor of self-auditing. The baseline audit is the single most important compliance document the agency will produce in the entire runway. It is what every subsequent remediation decision references. It is what demonstrates the agency assessed its environment systematically. It is what a DOJ inquiry will ask to see.
Agencies under genuine resource constraint should structure the audit as the first budget priority of the extended runway rather than as a cost to avoid. The cost of an audit is a fraction of the cost of remediating failures the audit would have caught.
Build the Documented Remediation Plan
The audit produces findings. The plan turns findings into a defensible sequence of work.
The plan should:
Group findings into priority tiers — critical failures blocking service access, major failures degrading service access, minor failures affecting secondary content, and issues affecting archival content.
Assign target completion timelines to each tier. Critical failures should be addressed within 90 to 180 days of audit completion. Major failures within 12 months. Minor and archival on a rolling schedule through the remainder of the runway.
Name ownership for each tier. Who is responsible for executing the remediation — internal staff, a development partner, a document remediation vendor.
Establish a validation standard. How will remediation be confirmed — retesting by the auditing firm, independent validation, staff testing against defined criteria.
Document the rationale. A brief written explanation of why the priority tiers were assigned as they were. This paragraph may feel unnecessary. It is not. It is what makes the prioritization decisions defensible rather than arbitrary.
Publish the Plan
Internally — to leadership, to staff who will execute the work, to department heads whose digital services are in scope. Externally — a summary version in the accessibility statement describing the agency's compliance program without necessarily including every specific finding.
Month 6 milestone: professional audit complete, documented remediation plan in hand, priority tiers defined, ownership assigned, executive leadership informed.
Phase 2: Critical Accessibility Remediation and Governance
With the baseline and the plan established, the work begins. Phase 2 focuses on two parallel tracks: addressing the highest-priority failures identified in the audit, and building the governance infrastructure that makes compliance sustainable.
The Critical Remediation Track
Address everything the audit classified as critical — failures blocking service access, failures in transactional workflows, inaccessible service application forms, blocking failures in payment portals. These are the items with the shortest timelines in the remediation plan and the highest direct impact on residents.
This is where the professional audit's prioritization pays off. The critical tier should not be where most of the work is — a well-prioritized audit concentrates findings into a manageable critical queue that is demonstrably addressable within the first remediation cycle. If the critical tier looks overwhelming, it is often because insufficient prioritization has been applied. Work with the auditing firm or a compliance consultant to ensure the critical tier is actually the critical tier — not everything that came back red.
The Governance Build Track
Parallel to critical remediation, build the governance infrastructure.
The remediation log becomes operational. Every issue identified, every action taken, every validation performed gets logged. Not just the items from the current audit — every new issue identified from any source (monitoring, complaints, new audit findings).
The accessibility statement is updated with specifics. Not a generic boilerplate — an honest description of the agency's current conformance status, known limitations, the active remediation program, and a working complaint contact that someone is monitoring.
The complaint intake process is tested. Send a test accessibility complaint to your own contact. Confirm it reaches the right person. Confirm a response protocol exists. Confirm response timelines are met. Document the process.
The vendor governance work starts. Request current VPATs from every third-party vendor in the digital environment. Begin the formal evaluation of each VPAT against WCAG 2.1 AA. Identify gaps and open remediation conversations with vendors whose tools have significant conformance issues. Begin writing accessibility language into every contract coming up for renewal.
The training program is designed. Role-specific modules — web developers, content editors, document publishers, IT/procurement, leadership — scoped and sequenced. Training content developed or selected. Delivery method determined. Documentation standard established.
Month 12 milestone: all critical remediations complete or on track with documented timelines, remediation log active with real entries, accessibility statement honest and current, complaint intake tested and functional, vendor VPAT collection complete, training program designed and ready to deploy.
At the halfway point of the extended runway, the agency should have a compliance program that exists, not just a compliance program that is planned.
Phase 3: Major Accessibility Remediation and Staff Training
With critical failures addressed and governance infrastructure operational, Phase 3 addresses the next tier of remediation while rolling out the training that makes the going-forward standard sustainable.
The Major Remediation Track
The findings classified as major in the audit — failures that degrade but do not entirely block service access. Color contrast failures in content areas. Heading hierarchy issues in complex pages. Form components with accessible but suboptimal implementations. Document accessibility issues on Priority 1 and Priority 2 documents in the remediation queue.
This is also the phase where the document library work happens in earnest. The triage framework from the document prioritization guide comes into full execution — active service forms fully remediated, current regulatory documents fully remediated, current meeting documents on their way, and historical archive work on its rolling schedule.
The Training Rollout Track
Phase 3 is when the training program built in Phase 2 actually runs.
Web and development staff complete their technical training on accessible component development, keyboard testing protocols, and CMS configuration. Attendance documented. Understanding confirmed through practical exercises.
Content editors complete the 90-minute role-specific module on heading structure, alt text, link text, and the five or six specific behaviors that most affect the accessibility of published content. Quick reference cards distributed to workstations.
Document publishers complete the 60-minute module focused specifically on PDF creation from Word, the accessibility checker workflow, and the pre-upload checklist. The physical checklist lands at their workstations alongside the training.
IT and procurement staff complete the VPAT evaluation training and the vendor accessibility contract language training. Sample contract provisions distributed. Vendor evaluation scorecard adopted.
Leadership receives the 30-minute briefing on the compliance program status, the quarterly reporting template, and the prepared response for public-facing accessibility questions.
The training is scheduled in a defined window — typically spread across a few weeks rather than a single day — so department coverage is maintained and staff can absorb the content at a reasonable pace.
Month 18 milestone: major tier remediation complete or on documented track, document library Priority 1 and 2 addressed, all content-creating roles trained with documented completion, going-forward standard operational with the training and the publishing workflows that support it.
This is the point at which the agency's compliance posture genuinely inflects. Before Phase 3 completion, compliance is an active project. After Phase 3 completion, compliance is an operational state sustained by trained staff, documented workflows, and active governance.
Phase 4: Accessibility Monitoring, Validation, and Compliance Documentation
Phase 4 is about sustaining and proving the compliance posture the earlier phases built. The remediation work continues — minor tier, rolling archive content — but the emphasis shifts to monitoring, revalidation, and documentation.
The Monitoring Program
Monthly automated scans are running at this point and have been for months. Phase 4 formalizes the full monitoring cadence:
Monthly automated scans with documented results and new findings logged. Quarterly manual keyboard and screen reader testing of primary transactional workflows. Annual document accessibility evaluation of a sample of newly published documents to confirm the going-forward standard is being applied. Vendor tool re-testing following any significant product update. Post-update regression testing following any significant CMS or template change.
All of these testing activities are documented. The monitoring log is alongside the remediation log as a twin pillar of the compliance documentation record.
The Validation Audit
Approximately 18 to 20 months into the runway — giving approximately four to six months before the compliance deadline — commission a validation audit. This is a more focused engagement than the original baseline audit. It confirms that:
The remediations identified in the baseline audit have been completed as documented. The going-forward standard is producing accessible content consistently. The vendor tools have been remediated or accessible alternatives are in place. The monitoring program is catching new issues.
The validation audit produces a revised conformance report — significantly more positive than the baseline — and identifies any remaining items to address before the compliance deadline.
The Executive Package
Approaching the final months before the deadline, assemble the executive compliance package — the documentation that would be produced in response to a DOJ inquiry, organized and ready. The goal is not to wait for an inquiry. The goal is to have this assembled as a standard operational document.
The package includes:
The current accessibility policy adopted by the relevant authority. The baseline audit report and the validation audit report. The remediation log with chronological entries. The monitoring records for the preceding twelve months. The complaint log with intake records and resolution documentation. The training records with role-specific attendance and completion dates. The vendor documentation — VPATs, remediation correspondence, accessible alternative pathway descriptions. The accessibility statement as published, with version history showing honest updates over the runway. The executive reports from the quarterly reviews.
Assembled and archived. Available for production on demand.
Month 24 milestone: validation audit complete, executive compliance package assembled, monitoring program in steady state, minor tier remediation substantially complete, program transitioning from initial build to sustained operation.
What a Defensible Position Looks Like at the Deadline
The compliance deadline is the checkpoint, not the finish line. But at the deadline, a well-executed twenty-four-month playbook produces an agency that can answer any DOJ inquiry substantively.
The agency has a current baseline audit and a validation audit documenting its compliance posture. It has a remediation log showing every identified issue and the action taken on each. It has training records demonstrating staff have been trained on accessible content publishing. It has vendor documentation demonstrating third-party tools have been evaluated. It has a monitoring program with records showing ongoing evaluation. It has a complaint process that has received complaints and produced documented resolutions. It has an accessibility statement that has been updated honestly throughout the runway. It has executive reports demonstrating leadership awareness and accountability.
The conformance status of the agency's digital environment will not be perfect. That is not the standard. The standard is documented, ongoing, good faith effort toward conformance. The playbook above produces exactly that — not because it was designed to satisfy documentation requirements, but because it is what sustained compliance actually looks like.
Where Agencies Most Commonly Go Off the Path
A few predictable deviations show up across agencies that start the playbook strong and drift off over the runway.
The audit gets delayed. Months pass. Procurement conversations happen. Scoping discussions drag on. The audit that should have been complete in Phase 1 is still being negotiated in Phase 2. Every phase downstream compresses. The playbook becomes harder to execute. The fix: set the audit procurement as the explicit first quarter deliverable and protect that timeline.
Governance is treated as a deliverable instead of infrastructure. The agency commissions an audit, receives findings, remediates the findings, and considers itself done. No remediation log for new findings. No monitoring cadence. No training beyond an initial rollout. Twelve months later, the compliance posture has regressed because the governance infrastructure was never actually installed. The fix: treat governance as operational infrastructure in Phase 2, not a closing ceremony in Phase 4.
The document library is deprioritized. The documents are tedious, the library is large, and the website-level work feels more visible. The document remediation program falls behind. The fix: assign document remediation to specific staff with specific targets for Priority 1 and 2 categories and track it as a named deliverable rather than a background task.
Vendor work is avoided. Third-party tools are the hardest part of the program because the agency does not control the remediation timeline. Some programs quietly avoid the vendor work because the outcomes are uncertain. The fix: open vendor conversations in Phase 2 regardless of uncertainty. The agency's defensibility comes from having engaged the vendor in documented good faith — not from having achieved a specific outcome.
Training becomes theater. An LMS module is assigned. Everyone clicks through it. Nothing changes in the published content. The fix: role-specific training with workplace reinforcement — quick reference cards, pre-publication checklists, CMS configuration changes that prompt accessible behavior at the point of content creation. Training without environment changes does not produce lasting behavior change.
Monitoring is not documented. Scans run. Results are reviewed in the moment. Nothing is archived. When the agency needs to demonstrate ongoing evaluation, there is no artifact to produce. The fix: archive every monthly scan result, every quarterly manual test record, every vendor test output. The documentation is the compliance evidence.
The Right Conversation to Have With Leadership
If you are the accessibility program owner reading this article, you may be trying to figure out how to position this playbook internally. The conversation with your city manager, your superintendent, your executive director, or your board chair matters.
The right conversation is not "the deadline was extended so we have more time." That conversation invites the stall.
The right conversation is not "we need to move faster because risk is still real." That conversation produces the defensive crouch rather than the proactive build.
The right conversation is: "The extended runway gives us the chance to build something that holds up. Here is what a twenty-four-month structured program looks like. Here is what it produces. Here is what it costs. Here is what happens if we do not build it."
Then show them the compliance package. The documented program. The defensible position. And the alternative — the Agency A scenario from the automated scanning piece, the agency that has no audit, no remediation log, no training records, no governance infrastructure, and a digital environment that may or may not be compliant but definitely cannot demonstrate compliance.
Leadership invests in the first picture when they see it clearly. The extension makes the first picture fully achievable within a single budget cycle. That is the conversation.
Related:
How to Write Alt Text for Government Images, Charts, and Maps
How to Audit Your CMS for Accessibility
How to Train Your Government Staff on Accessibility
FAQ: Using the Extended ADA Compliance Runway
How should our agency use the extra year that the DOJ's extension provides? Treat the extension as capacity, not as permission to delay. A twelve-month accessibility sprint under the original deadline forced most agencies to compress baseline auditing, remediation, vendor governance, training, and documentation into overlapping, rushed phases that produced compliance theater rather than durable programs. A twenty-four-month structured runway allows each phase to happen in sequence with meaningful time for testing, adjustment, and absorption. The extension is an opportunity to build a compliance program correctly, not an opportunity to take longer to do the same frantic work.
What is the single most important first step for an agency that is just starting its compliance program now? Commission a professional baseline accessibility audit. Not an automated scan, not a staff-run self-assessment — a third-party audit that produces a WCAG 2.1 AA conformance report covering the full digital environment including the primary website, transactional workflows, document library, and embedded third-party tools. The baseline audit is the foundation every subsequent remediation decision references. Agencies under resource constraint should structure the audit as the first budget priority of the extended runway rather than as a cost to defer. The cost of the audit is a fraction of the cost of remediating failures the audit would have caught later.
How should the twenty-four months of the extended runway be structured? A defensible four-phase structure: Phase 0 (months 1-2) for positioning — naming the program owner, establishing governance commitment, opening the documentation folder. Phase 1 (months 3-6) for the baseline audit and documented remediation plan. Phase 2 (months 6-12) for critical remediation and governance infrastructure build — remediation log, accessibility statement, complaint intake, vendor VPAT collection, training program design. Phase 3 (months 12-18) for major remediation and training rollout. Phase 4 (months 18-24) for monitoring program formalization, validation audit, and executive compliance package assembly.
What happens if an agency treats the extension as a reason to stall its compliance work? The stall is the single most common response to this extension and the most damaging one. Twelve months later, the agency is in the same position it was when the extension was announced, except with twelve fewer months of runway. The regulatory standard did not change. The enforcement environment did not change. Title II lawsuit exposure did not change. State-level enforcement is continuing to accelerate independently of the federal timeline. The stall produces exactly the last-minute scramble the extension was supposed to prevent — just shifted one year later with less time to execute.
What documentation does a defensible compliance program produce by the compliance deadline? At the deadline, a defensible program produces: a current baseline audit report and a validation audit report; a remediation log with chronological entries showing issues identified and actions taken; role-specific training records with attendance and completion documentation; vendor accessibility documentation including VPATs, remediation correspondence, and accessible alternative pathway descriptions; monitoring records showing ongoing evaluation for the preceding twelve months; a complaint intake log with resolution documentation; a current accessibility statement with version history showing honest updates over the runway; and executive reports demonstrating leadership awareness and governance. The conformance status does not have to be perfect — the standard is documented, ongoing, good faith effort, not absolute conformance.
How does an agency avoid the "perpetual planning" failure mode during the extended runway? Perpetual planning is what happens when the extended timeline removes the forcing function that would have compelled action. The countermeasure is treating each phase of the playbook as a deliverable with a specific end date and a named owner rather than as an ongoing discussion. The audit is commissioned and completed by Month 6. Critical remediations are complete by Month 12. Training is rolled out by Month 18. The validation audit is commissioned by Month 20. These milestones force execution over deliberation. An agency that is still scoping its baseline audit in Month 9 has drifted into perpetual planning and needs an intervention that returns it to execution mode.