State and local government ADA compliance requires coordinated accessibility governance across department websites, vendor platforms, document libraries, and public service workflows.
The DOJ extended the ADA Title II compliance deadlines by one year. Cities, counties, and special districts now have a materially different planning horizon than they did in April. Larger entities have until April 26, 2027. Smaller entities and all special districts regardless of size have until April 26, 2028.
For the state and local government (SLG) segment specifically, that extended runway arrives alongside operational realities that make the "just use the extra time productively" advice easier to say than to execute.
The city budget calendar does not reset when the DOJ issues an Interim Final Rule. The council election cycle does not pause. The county CIO is still managing departmental technology procurement across a dozen department-level relationships, each with its own vendor ecosystem and each with its own autonomy over the procurement conversation. The special district board meets monthly, has limited staff, and may not have a dedicated IT function. The city manager who was supporting the accessibility budget line item may not be the city manager making the budget decisions in twelve months.
The extended runway is long enough to build a defensible compliance program in any of these environments. It requires a plan calibrated to the actual operating realities of state and local government — not a generic public sector plan that assumes centralized authority, consistent staffing, and budget cycles that align with federal compliance timelines.
This guide is that plan. It takes the four-phase structure from the post-extension playbook and maps it specifically to the SLG environment — the multi-department vendor landscape, the document library reality, the budget calendar alignment, the political calendar risks, and the governance handoffs that sustain compliance programs through the administrative transitions that happen in every term of local government.
Why State and Local Government Is Different
Three structural characteristics shape how ADA compliance programs need to be built in cities, counties, and special districts. They are not insurmountable challenges. They are design constraints that a well-built program accounts for from the start.
Characteristic 1: Decentralized Vendor Systems and Accessibility Risk
In most state and local government environments, technology procurement is not centralized. The finance department buys its own billing platform. The planning department buys its own permit management system. The parks department buys its own registration platform. The police department buys its own records management system. The library buys its own catalog platform. Each of these vendor relationships was procured at a different time, under different conditions, by a different procurement team, and with different levels of accessibility scrutiny — which in most cases is to say, with no accessibility scrutiny at all.
The accessibility compliance program cannot operate as if technology procurement is centralized. It has to operate as a coordination function across a distributed ecosystem of department-level vendor relationships. This is different from enterprise environments where a single CIO controls most vendor decisions. It is different from higher education environments where centralized IT still exists alongside decentralized department authority. It is its own pattern and it requires its own approach.
Characteristic 2: Why Local Government PDF Libraries Create Massive ADA Risk
Cities, counties, and special districts produce and publish enormous volumes of documents as a core function of government. Board agendas. Meeting minutes. Staff reports. Public notices. Permits. Annual budgets. Strategic plans. Zoning maps. Code books. Environmental documents. Water quality reports. Infrastructure reports. Bid documents. Contract awards.
The document publishing obligation is not a side function — it is central to how local government operates and how transparency requirements are met. Every meeting produces documents. Every public process produces documents. Every annual cycle produces documents. The library grows continuously and historically consisted almost entirely of PDFs produced without accessibility consideration.
This means that for most SLG agencies, the document remediation question is the largest single component of the compliance program by volume — larger than website remediation, larger than vendor tool evaluation, larger than training. The playbook has to treat it that way.
Characteristic 3: The Political and Budget Calendar
Unlike higher education (where academic calendars drive institutional rhythm) or enterprise environments (where fiscal year calendars drive the budget cycle), state and local government operates on a political calendar that introduces discontinuities the compliance program must account for.
City councils and county boards hold elections every two to four years. New administrations bring new priorities, new budget emphases, and sometimes new senior staff. A city manager who championed the accessibility program in 2026 may not be the city manager making budget decisions in 2028. A council that supported the program in one election cycle may look different after the next one. A county supervisor who was the executive sponsor may leave office. The institutional memory of a multi-year compliance program lives in documentation and in staff tenure — and in state and local government, both of those are more variable than they would be in a longer-tenured organizational environment.
Budget cycles compound this. Most cities and counties operate on annual budgets adopted months in advance of the fiscal year. Accessibility program investments need to fit into that cycle. A mid-year funding request for a baseline audit often cannot be accommodated the way an enterprise IT organization could accommodate it.
These three characteristics — decentralized technology, document library scale, and political calendar risk — are the SLG realities the playbook has to reflect. What follows is that playbook.
Phase 0: The First 60 Days — SLG Positioning
The positioning items from the core playbook apply. A few additions and emphases specific to SLG.
Map the departmental technology ownership landscape early. Before the audit is commissioned, produce an inventory of which departments own which technology relationships. This inventory does not need to be comprehensive — it needs to identify the major department-level vendor platforms (billing, permits, records, GIS, parks, library, public safety) and the accountable person in each department. This map is what makes the downstream vendor governance work possible.
Identify the budget cycle alignment. Understand exactly when the accessibility budget decision happens in the annual cycle. In most cities, budget preparation begins six to eight months before adoption, with department proposals due mid-cycle. The accessibility program's funding requirements need to be in the department budget proposal at the right point in the cycle. Missing the cycle means waiting twelve months for the next one.
Establish political continuity through documentation. Because leadership transitions are a predictable risk, the program's foundational documents need to be in place early and visible enough that they survive transitions. A formal accessibility policy adopted by council resolution. A program charter. The accessibility statement. These are institutional artifacts that carry across administrative changes. Their early adoption is protection against the political calendar.
Name the inter-departmental coordination function. The compliance program owner cannot operate as an IT function alone — the program requires coordination with finance, public works, parks, planning, and every department with significant public-facing digital services. A standing coordination structure — a monthly meeting, a clear escalation path, defined roles — is what makes cross-departmental execution possible.
Month 2 milestone for SLG: departmental technology ownership mapped, budget cycle alignment identified, foundational governance documents adopted or scheduled for adoption, inter-departmental coordination structure named.
Phase 1: Local Government Accessibility Audits and Baseline Assessment
The baseline audit scope for state and local government needs to reflect the distributed technology and document library realities. A narrow audit of the main city or county website is inadequate — it addresses the most visible surface and misses the places where the largest share of the compliance exposure actually lives.
What the SLG Audit Scope Must Include
The primary agency website. City hall's main site, the county's primary domain, the special district's website. Page templates, content types, navigation, forms, and the high-traffic service pages.
Every department-level website, microsite, or subdomain. Parks and recreation sites. Library sites. Police and fire department sites. Planning and building department sites. Transit agency sites. Water district sites (where applicable). Economic development portals. Each one is part of the agency's digital environment and within scope.
Every transactional workflow across departments. Permit applications. Utility bill payment. Parks program registration. Court fine payment. Public records requests. Business license renewal. Jury management. Community event registration. Each transactional surface is evaluated as its own workflow — not just as a link from the main website.
The document library across departments. Not a sample of fifty documents. A representative sample that reflects the true distribution across document types and departments — meeting documents from the city council and all boards and commissions, current regulatory documents from planning and building, current rate schedules and tariff documents from finance, current RFP and bid documents from procurement, public notices from every department that issues them, annual reports from each department that produces one.
Every department-level third-party tool. The billing platform, the permit platform, the records management system, the payment processing systems, the scheduling tools, the citizen engagement platforms, the public meeting video platforms, the GIS tools, the library databases, the translation widgets, the chat tools. Each one evaluated.
Mobile apps operated by the agency. Transit apps, parking apps, service request apps, emergency notification apps. Separate digital environments that carry their own Title II compliance obligation.
The embedded social media surface. Not the social platforms themselves — those are not the agency's compliance object. But the agency's use of social platforms — image-based announcements without alt text, video content without captions, content communicated only through social platforms without accessible equivalents on the website — is within the agency's compliance scope.
The SLG Audit Deliverable
Given the breadth of scope, the useful audit deliverable structure for an SLG agency:
A compliance posture summary at the agency level.
Department-level findings reports that each department head can work with directly — the planning department's findings package, the parks department's findings package, and so on. This departmental packaging makes the remediation work distributable across the organization rather than centralized in a single office that cannot possibly address it alone.
A vendor-stratified risk analysis identifying which vendor relationships most affect the agency's compliance posture and which deserve the focused contractual attention in the coming renewal cycles.
A document library characterization with the tier-based triage framework applied, producing a prioritized remediation queue rather than an undifferentiated list.
A prioritized overall remediation roadmap that integrates the findings across surfaces and accounts for the distributed ownership reality.
Month 6 milestone: audit complete at full scope, findings delivered in departmentally-relevant packages, vendor risk stratification done, document library triage applied, overall remediation roadmap in hand.
Phase 2: Critical Accessibility Remediation and Governance
Critical Remediation in SLG Context
The critical tier for state and local government typically concentrates in transactional service workflows and active public notice content.
Transactional workflows that residents must complete to access core services. The utility bill payment portal. The permit application portal. The business license renewal workflow. The court fine payment system. The jury response system. These are the workflows where accessibility failures create the most direct barriers to service access and therefore carry the highest enforcement priority.
Active public notices and time-sensitive regulatory content. Any document being published under a legal notification obligation — environmental notices, right-of-way acquisition notices, public hearing notices, rate change notices. These carry simultaneous Title II obligations and underlying notification obligations. The remediation timeline is tight.
Emergency and public safety digital surfaces. The emergency alert signup portal, the active alert publication pages, the shelter information resources. The urgency principle from the emergency management vertical applies — when accessibility fails at the moment of emergency, it fails for the residents who most need the information.
Current fiscal year forms and applications. The forms residents are using right now to access current services. Not every form in the library — but the current versions of every active service application form.
SLG Governance Build
The governance infrastructure in Phase 2 has SLG-specific emphases.
The formal policy adoption. The accessibility policy adopted by city council resolution, county board action, or special district board action. This is the formal instrument that makes the policy survive administrative transitions. Drafting it, walking it through the council or board process, and getting formal adoption is a Phase 2 deliverable. A program without an adopted policy is a program that can be defunded by a future administration without any institutional record of the commitment.
The inter-departmental compliance structure. Monthly coordination meetings operational. A compliance lead identified in each major department. Escalation paths documented. This structure is what translates the central program into execution across the distributed organization.
Document remediation work begins. Not just planning — actual remediation. Tier 1 documents (active service forms, current regulatory documents, public notices) move through the queue. The volume is meaningful by Month 12.
Vendor VPATs collected at scale. One by one, across every department-level vendor relationship. This is a significant lift for SLG agencies — most have dozens of vendor relationships and many vendors will take weeks to produce a current VPAT. Start the request process early, track the responses, and escalate where vendors are unresponsive.
The complaint intake process is tested and formalized. A named contact, a monitored inbox or phone line, a defined response timeline, a documented resolution workflow. The complaint process is a public-facing function that has to work — residents reporting accessibility barriers deserve responsive handling and the compliance record benefits from documented responsiveness.
Training program design is complete. The role mapping is done, the modules are drafted, the delivery plan is set. Phase 3 will roll out the training. Phase 2 is where it gets designed.
Month 12 milestone: critical remediations complete, accessibility policy formally adopted, inter-departmental coordination operational, document Tier 1 remediation underway, vendor VPATs being collected, complaint intake operational, training program designed.
Phase 3: Department Accessibility Training and Major Remediation
Major Remediation in SLG
Phase 3 addresses the broader tier of remediation.
Department website remediation. The department sites identified in the audit get addressed on a scheduled rotation. Parks this quarter. Library next quarter. Planning the quarter after. Each department's site remediation is scoped and timelined with the department's input.
Current-year meeting documents. All current-year board and council agendas, minutes, and staff reports either remediated as they are published (going-forward standard) or remediated in a batch for the content already published in the current year.
Current fiscal year regulatory documents. The current rate schedules, the current fee schedules, the current code versions. These are the operative legal documents governing residents' and businesses' rights and obligations in the agency's jurisdiction.
Secondary transactional workflows. The transactional workflows that were not critical but are significant — the less-used service applications, the secondary payment portals, the event registration systems.
Training Rollout in SLG
The training audiences in SLG span departments and roles.
The central web team. The agency's main web/IT staff responsible for the primary website and the shared infrastructure. Technical training on accessible component development, CMS configuration, and ongoing accessibility testing.
Department communications staff. The content managers in each department — the communications coordinator in planning, the social media manager in parks, the PIO in police and fire, the community engagement coordinator in planning. Role-specific training on accessible content publishing in the tools they actually use
Department administrative coordinators. The staff who upload meeting documents, agendas, and staff reports. This is the largest-volume document publishing role in most SLG agencies and the role with the most immediate impact on the accessibility of public documents.
IT and procurement staff. VPAT evaluation training, vendor contract language, the accessibility scorecard. This is a smaller audience in SLG than in higher ed but includes the departmental IT leads across the organization.
Department heads and the city/county/district leadership. The 30-minute briefing on the compliance program status, the agency's current posture, the ongoing work, and the support needed from leadership.
Council and board members. A brief orientation for elected officials on what the accessibility program is, what their role in governance is, and what they will see in quarterly reports. This is easy to skip and important not to. Elected officials who understand the program are less likely to defund it under budget pressure.
Month 18 milestone: major remediation on track across department sites and current-year documents, training rolled out to all content-creating roles with documented completion, leadership and elected officials briefed.
Phase 4: Accessibility Monitoring and Administrative Transition Protection
Monitoring in SLG
The monitoring cadence in state and local government reflects the operational rhythm.
Monthly automated scans across primary and department sites. Documented, archived, reviewed for new findings.
Quarterly manual testing of transactional workflows. The payment portals, the permit applications, the service request forms. Keyboard and screen reader testing by staff or by a rotating engagement with an accessibility vendor.
Monthly document monitoring. A sample of newly published documents each month evaluated against the going-forward standard. This catches backsliding in document publishing practices early.
Pre-agenda-posting document review. For meeting documents specifically, integrate accessibility review into the agenda posting workflow. The clerk's office (or equivalent) confirms document accessibility before posting, not after.
Annual vendor review. Each vendor tool re-tested annually with VPAT status refreshed. This aligns with most vendor contract review cycles.
Post-election program briefing. After any council or board election, the new members receive the accessibility program briefing as part of their onboarding. This is the intentional transition protection.
The Transition Protection Package
At Month 20, the program owner should assemble a specific package designed for administrative transition protection.
The policy record. The adopted accessibility policy with the formal resolution number and adoption date.
The program history. A brief written history of the program — when it was initiated, what has been accomplished, what is in progress, what the current-year budget commitment is.
The compliance posture summary. The current audit findings, the remediation progress, and the ongoing activities.
The obligation context. A brief memorandum from the agency attorney summarizing the Title II compliance obligation, the risks of non-compliance, and the basis for the program's continued investment.
The public-facing evidence. The published accessibility statement, the complaint log with responses, the records of accessibility-related inquiries handled.
This package is designed to be handed to a new administration — a new city manager, a new department head, a new council majority — as the introduction to the program. It answers the questions a new leader will have: what is this, why do we do it, what does it cost, what are the risks of stopping it. With the package available, the program has a strong institutional defense. Without it, the program is vulnerable to simple defunding by an administration that does not inherit the context.
Month 24 milestone: validation audit complete, transition protection package assembled, monitoring cadence in steady state, program transitioning from initial build to sustained operation.
The Budget Conversation in SLG
Because budget calendars are a specific constraint in SLG environments, a note on how to structure the budget conversation for the accessibility program.
Multi-year budget framing. The accessibility program is not a single fiscal year project. Present it as a two-to-three-year program with specific annual budget requirements. Year one is the baseline audit, the critical remediation, and the governance build. Year two is the major remediation, the training rollout, and the initial monitoring. Year three is the validation audit, the sustained operations, and the document library progression. Show the total commitment and the annual breakdown.
The cost of alternatives. The budget conversation benefits from specific comparison to what non-compliance costs. ADA Title II settlement figures in comparable agencies. The cost of emergency remediation following an enforcement inquiry. The cost of a consent decree with court-supervised compliance monitoring and third-party auditing requirements. These numbers make the accessibility program's cost contextually reasonable.
Phased funding approach. If the full program cannot be funded in a single budget cycle, propose phased funding that aligns with the four-phase playbook. Phase 1 (baseline audit, initial remediation) can be a smaller funding package that produces visible results and builds support for subsequent phase funding. Phase 2 and 3 funding requests can build on demonstrated progress from Phase 1.
Coordination with existing technology and compliance budgets. The accessibility program does not need to be an entirely new budget line. Portions of it can be absorbed in existing IT, communications, and compliance budgets — the baseline audit as a contracted professional service, the training as part of existing staff development budgets, the CMS configuration work as part of existing web operations. Structuring the program this way reduces the new budget footprint while still achieving the program objectives.
Where SLG Programs Most Commonly Go Wrong
Five deviations specific to state and local government that recur across agencies.
The audit scope is too narrow. The agency audits the main website, gets clean results or a short finding list, and thinks the job is largely done. The parks department site, the library site, the permit portal, the document library — all of the places where the actual exposure lives — were not in scope. The fix: audit scope must include every department-level digital surface and the document library from the start.
The document library is deprioritized as "too big." The agency looks at thousands of PDFs and decides to focus on website content instead. Twelve months later, the website is partially remediated and the document library is untouched. The documents are where the largest share of exposure lives. The fix: apply the tier-based triage framework from Day One and start working the queue — not after everything else is done, but as a parallel track.
Vendor tools are treated as vendor problems. The agency concludes that the billing platform, the permit system, and the records management system are the vendors' responsibilities and that nothing can be done centrally. The fix: request VPATs, open the vendor conversations, write accessibility language into renewals. The agency cannot remediate the vendor platforms directly but has significant contractual and procurement leverage that goes unused when the work is abdicated.
Training is centralized and not department-specific. A single generic accessibility module is pushed to all staff. Completion rates look high. Nothing changes in what gets published. The fix: role-specific training built around what each department and each role actually does, with quick reference cards and pre-publication checklists that reinforce the training in the workflow.
The transition vulnerability is unaddressed. The program is built strong under the current administration and has no institutional defense for administrative transitions. Two years in, a new city manager asks why the agency is spending money on this and there is no package to hand over. The fix: build the transition protection deliberately in Phase 4 — the policy record, the program history, the posture summary, the obligation memo, the public-facing evidence.
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: SLG ADA Compliance and the Extended Runway
How does the ADA Title II extension affect cities, counties, and special districts? The DOJ's Interim Final Rule extends both compliance tiers by one year. Cities, counties, and other state and local government entities serving populations of 50,000 or more now have until April 26, 2027. Smaller entities and all special district governments regardless of size have until April 26, 2028. The underlying WCAG 2.1 AA technical standard is unchanged, the Title II compliance obligation itself is unchanged, and state-level accessibility requirements continue to operate on their own timelines independent of the federal extension. The extension provides additional runway to build a defensible program, not relief from the requirements.
What is the biggest difference between SLG accessibility programs and general public sector programs? State and local government environments are characterized by decentralized technology procurement (different departments own different vendor relationships), massive document publishing volumes (meeting documents, public notices, regulatory documents produced continuously as a core function of government), and political calendar risk (administrative and elected leadership transitions that can disrupt multi-year programs). Effective SLG accessibility programs are designed around these realities — distributed rather than centralized execution, document library remediation as a first-tier workstream, and deliberate transition protection built into the program structure.
How should an SLG agency scope its baseline accessibility audit? The audit scope must include the primary agency website, every department-level website and microsite, every transactional workflow across departments, a representative sample of the document library reflecting the true distribution of document types and ages, every department-level third-party vendor tool, any mobile apps operated by the agency, and the agency's use of social media where information is communicated only through those platforms. A narrow audit of just the main website addresses the most visible surface and misses the places where the largest share of compliance exposure actually lives.
How should an SLG agency handle the document library in its compliance program? The document library is typically the largest single component of SLG compliance programs by volume. Apply tier-based triage — active service forms, current regulatory documents, and active public notices as Tier 1; current meeting documents and current informational content as Tier 2; recent historical content as Tier 3; older archival content on rolling schedules; and obsolete content as candidates for removal rather than remediation. Establish a going-forward publication standard simultaneously so the library does not continue growing inaccessible documents while backlog remediation is underway.
How should an SLG agency approach vendor accessibility when procurement is decentralized across departments? The accessibility program acts as a coordination function rather than a direct ownership function. Request VPATs from every vendor identified in the department-level technology ownership map. Evaluate each VPAT and document known gaps. Open remediation conversations with vendors whose tools have significant accessibility issues. Write accessibility language into every contract renewal, which over a two-to-three year cycle will flow through most of the agency's vendor relationships. Establish accessibility requirements in new procurement RFPs as a standard provision. The centralized accessibility program provides the consistency of approach; the department procurement process provides the contractual leverage.
What should an SLG agency do to protect its accessibility program across administrative transitions? Build deliberate transition protection into the program structure. Formally adopt the accessibility policy through council or board action so it becomes an institutional instrument rather than an administrative preference. Document the program history — initiation date, accomplishments, current posture, budget commitment — in a form that can be handed to new leadership. Maintain an obligation memo from the agency attorney summarizing the Title II compliance obligation and the risks of discontinuation. Brief new elected officials after each election cycle on the program as part of their onboarding. These elements make the program durable through the administrative transitions that happen predictably in state and local government.