ADA Title II compliance for county governments requires governing a decentralized digital ecosystem that includes department websites, board documents, vendor platforms, and public service portals.
County governments are not like other public agencies. And that distinction matters enormously when it comes to ADA Title II digital accessibility compliance.
A city has a website. A county has an ecosystem. Public health. Courts. Elections. Public works. Planning and zoning. Tax collection. Licensing. Emergency services. Animal services. Parks and recreation. Board of supervisors. Each of these functions operates with some degree of independence, publishes content through its own workflows, relies on its own set of vendor tools, and serves residents who depend on those services to participate in civic life.
That complexity is not a flaw in how counties are organized. It is the nature of what counties do. But it creates a compliance environment that is categorically more difficult to govern than a single-purpose agency — and one where accessibility risk accumulates through structural drift rather than negligence.
Most counties with significant ADA exposure are not in that position because they ignored accessibility. They are in that position because their digital environment grew faster than their governance did. Departments published independently. Vendors were onboarded without accessibility review. Board documents were generated and uploaded without standards. Seasonal staff came and went. Microsites were launched for elections and public health initiatives and then left up indefinitely.
Each of these events is ordinary county operations. Collectively, without governance, they build structural exposure that compounds every week.
This is what that looks like in practice and what governance at county scale actually requires.
1. Decentralized Publishing Is the Root ADA Accessibility Risk for Counties
In most county governments, the web is not managed centrally. It is managed departmentally. The elections office publishes its own pages. The health department maintains its own content. The assessor's office uploads its own documents. The parks department adds its own event listings. The public works department posts its own project updates.
This is operationally rational. No central web team could manage content at the volume and velocity that county operations require. Decentralization is not the wrong approach. Decentralization without governance is.
When departments publish independently without accessible content standards, without editor training, and without any review process, the accessibility of the county's digital environment becomes a function of individual editors' awareness and habits rather than organizational policy. Some departments will happen to publish accessibly. Others will not. The county has no consistent visibility into which is which.
What decentralized publishing without governance looks like in practice: a planning department coordinator scans a signed variance approval to PDF and uploads it to the public records portal because that is the format she received it in and there is no standard telling her otherwise. A health department communications staff member uploads a program flyer as an image file because it was designed in Canva and exported as a JPEG. An elections team member publishes a ballot measure summary page with color-coded tables as the only way to distinguish between yes and no vote tallies. A public works contractor adds a new interactive map to a project page without accessibility testing because the project timeline did not include it.
None of these people are negligent. They are working in a system that does not give them the information or the standards they would need to do it differently. That is a governance problem.
The structural requirements for managing decentralized publishing at county scale include: written accessible content standards that are specific enough to be actionable by non-technical staff, editor training programs with documented completion tracking, pre-publish checklists embedded in the content workflow where possible, template-level controls that make inaccessible publishing harder than accessible publishing, and recurring monitoring that catches what slips through anyway.
Without these structures, every department and every editor is an independent accessibility risk operating without guardrails.
2. Board Agendas and Public Meeting Documents Are High-Visibility, High-Risk
County boards generate document volume at a pace that creates continuous compliance exposure. A board that meets weekly or biweekly produces agendas, minutes, staff reports, budget attachments, public comment packets, and regulatory proposals every cycle. Each document is publicly accessible. Each document is directly tied to civic participation. And each document is a potential accessibility failure.
The failure patterns in board document accessibility are consistent across counties. Staff reports exported from Word without running accessibility checks, producing PDFs with no heading structure and no defined reading order. Minutes generated from meeting notes with complex tables that have no programmatic header associations. Budget documents with charts and graphs embedded as images with no text alternatives. Signed resolution documents scanned to flat image PDFs because the original was a physical document and scanning is the path of least resistance.
This last category is worth emphasis. A scanned PDF is an image. A screen reader cannot interpret an image as text. A county resident who is blind, trying to read the agenda for a public hearing where a decision will be made that affects their neighborhood, cannot access a single word of a scanned board packet. That is not a technical edge case. It is a denial of civic participation. And board documents are one of the most commonly cited document categories in ADA Title II accessibility complaints.
The scale of the problem compounds quickly. A county with biweekly board meetings produces more than two dozen meeting cycles per year. Each cycle may include ten to thirty documents. Without accessible document standards and a remediation program, a county is adding dozens of inaccessible documents to its public-facing document library every month, on top of whatever backlog already exists.
What a defensible board document program requires: a document inventory that establishes the scope of existing exposure, a risk classification that prioritizes active meeting documents over archival minutes from five years ago, accessible PDF creation and export standards distributed to every staff member who generates board materials, a pre-upload review process for high-visibility documents, and a remediation queue working through the historical backlog on a defined timeline.
3. Public Records Portals Carry Direct Civic Rights Exposure
Public records access is not a secondary county function. It is a core accountability mechanism that residents, journalists, attorneys, and advocacy organizations depend on. And the digital systems that provide that access are among the most consistently inaccessible surfaces in county digital environments.
Public records portals often combine legacy architecture with complex interactive functionality. Search fields, filter systems, paginated results tables, document download interfaces, case lookup tools, parcel search maps, and tax record systems — all of which need to be keyboard navigable, screen reader compatible, and operable by users with a range of assistive technologies.
What the accessibility failures in these systems actually look like: a property tax lookup system where the search results table has no column headers, meaning a screen reader user cannot determine what each column represents or how the data is organized. A court records portal where the document filter menus cannot be operated via keyboard and the only way to narrow results requires mouse-based interaction. A GIS parcel search tool that is entirely dependent on visual map interaction with no keyboard alternative and no accessible equivalent pathway. A CAPTCHA system on a public records request submission form with no audio alternative, blocking screen reader users entirely.
Each of these failures represents a barrier to a civic right. And because public records portals are frequently built on legacy systems or managed by specialized third-party vendors, they tend to receive less accessibility attention than the main county website — despite representing some of the most consequential access failures in the entire digital ecosystem.
Governance for public records systems specifically requires: direct testing of the full records request workflow using keyboard-only navigation and screen reader tools, evaluation of all search and filter functionality, review of how results and downloaded documents are presented to assistive technology, and vendor-specific VPAT review for any system that is hosted or managed by a third party.
4. Elections and Temporary Microsites Are Not Exempt
Counties launch temporary digital properties regularly. Election result dashboards. Public health initiative sites. Emergency response portals. Bond measure information pages. Community engagement surveys. These sites are built quickly, often under compressed timelines, and they almost universally receive less accessibility review than the main county site.
Temporary and seasonal sites are not exempt from ADA Title II. The law does not distinguish between a site that has been live for five years and one that was launched two weeks before election day. If a county is delivering public information or services through a digital property, that property carries the same accessibility obligations as any other part of the agency's digital environment.
The exposure risk for election-related sites is particularly significant because of their visibility. An inaccessible election results dashboard or ballot information page during an election cycle is the kind of failure that generates media coverage, advocacy organization attention, and complaint filings simultaneously. The temporal compression of election operations does not reduce the accessibility obligation. It increases the stakes of failing to meet it.
What a governance-aware county does differently: accessibility review is built into the launch checklist for any new digital property before it goes public. Not after. Before. The review covers color contrast on dynamic result displays, keyboard navigation of all interactive elements, screen reader compatibility for results tables and map components, caption requirements for any embedded video content, and accessibility of any documents linked from the site.
If the timeline does not accommodate accessibility review before launch, the timeline is the problem to solve — not the accessibility requirement to defer.
5. Vendor Proliferation Creates Fragmented Compliance Liability
The average county digital environment is not a single system. It is a collection of integrated platforms, each managed by a different vendor on a different release schedule, each with its own accessibility track record and its own VPAT documentation status.
Court case management portals. Property tax platforms. Recreation reservation systems. Licensing vendor tools. Public health reporting systems. Online payment processors. Scheduling software. GIS platforms. Meeting management tools. Each of these represents a vendor relationship that the county relies on for resident-facing service delivery. Each of them is part of the county's compliance obligation.
The vendor proliferation problem in county governments is specifically that the compliance surface expands with every vendor integration, and most counties have no systematic process for evaluating, contracting for, or monitoring vendor accessibility. Procurement decisions are made based on functionality and cost. Accessibility is rarely a scored evaluation criterion. VPATs are rarely requested. Contracts rarely include accessibility requirements or remediation obligations.
The result is a vendor portfolio of unknown accessibility quality that updates on cycles entirely outside county control. A court records vendor releases a platform update. Something in the update breaks keyboard navigation in the case search interface. No one at the county knows because no one is testing vendor tools after major releases. The failure persists until a resident files a complaint.
What vendor governance at county scale requires: accessibility as a defined evaluation criterion in RFPs with minimum conformance requirements that vendors must document. VPAT review for every vendor in the current portfolio, not just new procurements. Accessibility requirements and remediation obligations written into vendor contracts. A scheduled testing cadence for major vendor tools after significant releases. A centralized record of vendor accessibility status that is reviewed as part of the monthly compliance program.
The county cannot control what vendors build. It can control what it contracts for, what it monitors, and what records it maintains about vendor accessibility status.
6. Staff Turnover Dissolves Accessibility Knowledge Without Governance
Counties experience staff turnover at every level. Elected officials transition. Department directors change. Web administrators move on. Contracted digital staff rotate. Temporary publishing staff are brought in during high-demand periods and leave when the workload subsides.
When accessibility knowledge, standards, and process live inside individuals rather than documented systems, every departure is a compliance regression event. The web manager who understood WCAG requirements leaves. The developer who knew which templates had been remediated takes a position elsewhere. The department coordinator who had internalized accessible PDF creation standards retires. The next people in those roles inherit an environment they do not have the context to maintain.
This is not a hypothetical risk. It is a predictable outcome of any accessibility program that has not been institutionalized into documented standards, training protocols, and governance structures that survive the people who created them.
What institutionalized accessibility knowledge looks like at the county level: written accessible content standards that are specific enough to function as training materials, not just policy statements. Editor training programs with a defined curriculum, a delivery schedule, and documented completion records. Pre-publish checklists that embed accessible publishing requirements into the content workflow rather than relying on individual editors' memory. A central remediation log that gives any incoming staff member a complete picture of where the compliance program stands and what work is in progress. Defined role responsibilities for accessibility at every level — not just in IT, but across department administration, communications, and executive leadership.
The goal is a compliance program that any new team member can pick up and continue without a months-long transition period. That kind of durability is the difference between an accessibility program and an accessibility person.
7. Multi-Site and Subdomain Complexity Requires Holistic Governance
Many counties do not operate a single website. They operate an ecosystem of digital properties that collectively represent their public-facing digital environment. The main county site. The health department site on a separate subdomain. The elections microsite. The parks and recreation registration portal. The court self-help center. The public works project tracking page. The assessor's parcel search tool.
Each of these may use different templates. Different CMS instances. Different vendor integrations. Different publishing workflows. Different staff. And different levels of accessibility maturity.
The compliance reality is straightforward: if any part of this ecosystem contains barriers, the county has accessibility exposure. The fact that the main county site passed its last audit does not address the accessibility status of the elections subdomain or the health department portal. A complaint about an inaccessible document on the parks and recreation site is not mitigated by the main site's accessibility statement.
Governance must be holistic. It must account for the full ecosystem rather than treating each property as a separate compliance question. That means the baseline audit scope includes subdomains and microsites, not just the primary domain. The monitoring program covers the full ecosystem on a rotating schedule. The governance framework defines accessibility responsibilities for each property and each property owner. And the remediation log tracks issues across all properties in a single centralized system.
Counties that audit only their main site and consider their compliance program complete have evaluated a fraction of their actual exposure. The rest of it continues to accumulate unnoticed.
8. What Mature County Accessibility Governance Actually Looks Like
Counties that have built functional accessibility governance programs share a consistent set of structural elements. Not the same tools. Not the same org charts. But the same operational logic applied to their specific environment.
A centralized accessibility policy that is formally adopted, clearly defines scope across all county digital properties, assigns governance responsibilities at both the department and county leadership level, and is reviewed and updated on a defined schedule.
A baseline audit that covers the full ecosystem — main site templates, core transactional workflows, department subdomains, microsites, and a representative sample of the document library. The audit is not a one-time event. It is the starting point for an ongoing program, updated on a rolling basis.
A document accessibility program with an inventory of publicly accessible documents, a risk-based prioritization model distinguishing active service documents from archival content, accessible document creation standards distributed to all publishing staff, and a remediation queue working through the high-priority backlog.
A vendor governance framework that includes accessibility criteria in procurement, VPAT review for all current vendor tools, accessibility requirements in contracts, and a scheduled testing cadence for major vendor tools.
A centralized remediation log maintained across all county properties, updated in real time as issues are identified and addressed, reviewed monthly by the governance owner, and used as the primary evidence document for the compliance program.
A recurring monitoring program covering the full ecosystem on a rotating schedule, with monthly automated scans and quarterly manual QA of core transactional workflows.
A defined accessibility coordinator role with specific responsibilities, sufficient authority to enforce standards across departments, and regular reporting obligations to county executive leadership.
An executive reporting cadence that keeps county leadership informed of compliance status, risk trends, and remediation progress on a quarterly basis.
This is not a small program. It is appropriate to the complexity of the environment it is governing.
9. Complexity Is Not the Enemy. Ungoverned Complexity Is.
Counties cannot simplify themselves into a lower-risk accessibility environment. The complexity is the county. It is the nature of what county governments are and what they do.
The answer is not simplification. It is governance that is scaled to match the complexity.
Every county that has managed to build a defensible accessibility program has done it by accepting the complexity as the operating environment and building structures designed for that environment — not by pretending the environment is simpler than it is or by applying a single-agency governance model to a multi-department, multi-site, multi-vendor ecosystem.
Accessibility risk in counties is structural. The solution is structural. Monitoring. Remediation. Documentation. Centralized oversight with decentralized execution. Governance that is distributed enough to function in a department-managed environment but centralized enough to produce a coherent compliance record.
That structure is what turns an unmanaged accumulation of accessibility risk into a program that can be demonstrated, defended, and sustained.
If Your County Is Operating Without Centralized Accessibility Governance
Start by asking the questions that reveal where the gaps actually are. Do you have a centralized remediation log that covers all county digital properties? Are department uploads governed by written accessibility standards? Are board documents produced and reviewed against accessible document requirements before being posted? Have your vendor portals been tested with keyboard navigation and screen reader tools? Is accessibility status reported to county executive leadership on a regular schedule? Do you have a monitoring program that covers your subdomains and microsites, not just the main site?
If the answers are unclear or inconsistent, the next step is a structured assessment that maps the full scope of your digital ecosystem, identifies where exposure is concentrated, and produces a prioritized governance roadmap calibrated to county-scale complexity.
Accessibility at county scale requires governance at county scale. The starting point is knowing what you are actually governing.
FAQ: ADA Compliance for County Governments
Why are county governments at higher ADA risk than cities? County governments operate decentralized digital ecosystems that typically include multiple departments, independent publishing workflows, dozens of vendor-hosted systems, and several distinct digital properties like subdomains, microsites, and specialized portals. Unlike a single-purpose city department managing one primary website, counties are responsible for public health, courts, elections, public records, tax collection, licensing, emergency services, and more — each of which may publish content independently and rely on different vendor tools. That structural complexity creates more surfaces for accessibility failures to accumulate, more staff publishing without centralized oversight, and more vendor integrations introducing risk outside county control.
What county systems create the most accessibility risk under ADA Title II? The highest-risk surfaces in county digital environments are board meeting documents, public records portals, vendor-hosted transactional platforms, elections and temporary microsites, and online service applications for permits, licenses, and tax payments. Board documents are high-risk because of their volume, their civic significance, and the prevalence of scanned PDFs that screen readers cannot interpret. Public records portals carry direct civic rights exposure. Elections microsites are high-visibility and frequently built under compressed timelines without accessibility review. Vendor platforms are often the least-monitored part of the ecosystem despite representing core service delivery functions.
What governance structure reduces ADA exposure for county governments? Effective county-level accessibility governance requires five core components working together. A centralized accessibility policy that defines scope across all county digital properties and assigns governance responsibilities at both the department and leadership level. A centralized remediation log that tracks issues across all properties in one system, updated in real time and reviewed monthly. A vendor governance framework that includes accessibility criteria in procurement, VPAT review for existing tools, and contract language with remediation obligations. A recurring monitoring program that covers the full digital ecosystem including subdomains and microsites, not just the main county site. And an executive reporting cadence that keeps county leadership informed of compliance status on a regular schedule.
Do county elections sites and temporary microsites have to meet ADA accessibility standards? Yes. ADA Title II applies to all digital services delivered by a public entity regardless of how long the site has been live or how quickly it was built. Temporary and seasonal sites, including elections result dashboards, public health initiative pages, emergency response portals, and bond measure information sites, carry the same accessibility obligations as the main county website. Their higher public visibility during active periods actually increases the risk of complaint filings if accessibility barriers exist. Accessibility review should be built into the launch process for any new public-facing digital property before it goes live.
Are counties responsible for the accessibility of third-party vendor systems? Yes. Under ADA Title II, public entities remain accountable for the accessibility of services they deliver to the public regardless of whether a vendor built the underlying technology. If a resident cannot access a county service because a vendor's platform is inaccessible, the county bears that compliance responsibility. Counties should evaluate vendor accessibility during procurement using VPAT documentation, include accessibility requirements and remediation obligations in vendor contracts, and test vendor tools on a scheduled cadence after major platform updates to catch regressions before they generate complaints.
How should counties handle the document accessibility backlog? Most counties have accumulated a significant backlog of publicly accessible PDFs that have never been reviewed for accessibility. Attempting to remediate every historical document simultaneously is not realistic. The practical approach is to build a document inventory, classify documents by risk level distinguishing active service documents from archival content, and prioritize remediation starting with board meeting documents, public notices, permit forms, and any document required for public participation. A going-forward accessible document standard for all new uploads prevents the backlog from growing while historical remediation proceeds. The combination of active prioritization and a going-forward standard is what makes a document program sustainable at county scale.