Title II of the Americans with Disabilities Act governs public entities, and one of the most persistent questions I encounter is whether a state or local government can outsource its ADA obligations when it hires a private contractor to deliver services, run programs, build websites, operate transit, or manage public facilities. The short answer is no. A government may contract out work, but it cannot contract away the duty to provide people with disabilities equal access to programs, services, and activities. That principle sits at the center of Title II compliance, and it matters because modern government depends heavily on vendors. Cities use software companies for online payments, counties hire medical providers for jails, school districts retain transportation companies, and public universities rely on third-party platforms for admissions, learning management, and events. When accessibility breaks down in any of those settings, the public entity remains legally responsible.
Title II applies to public entities, meaning state and local governments and their departments, agencies, special purpose districts, and instrumentalities. Its core command is that qualified individuals with disabilities cannot be excluded from participation in or denied the benefits of public services, programs, or activities, nor be subjected to discrimination by a public entity. Key concepts include program accessibility, effective communication, reasonable modification of policies, procedures, and practices, accessible facilities, and integration in the most appropriate setting. The governing regulations appear primarily at 28 C.F.R. Part 35, with transportation rules also addressed through Department of Transportation regulations. In practice, Title II reaches both physical and digital government functions, from sidewalks and polling places to emergency alerts and online tax portals.
The contractor question matters for risk, procurement, budgeting, and public trust. I have seen agencies assume that accessibility belongs solely in the vendor’s statement of work, only to discover too late that residents still blame the government, investigators still contact the government, and courts still analyze the government’s duties first. A city that outsources paratransit dispatch, for example, must still ensure equivalent service and nondiscriminatory eligibility practices. A county that uses a third-party web platform for permit applications must still ensure accessible forms, keyboard navigation, captions, and compatibility with screen readers. This article explains how Title II works, why outsourcing does not shift ultimate responsibility, and what public entities should do to manage contractors without creating avoidable ADA violations.
What Title II Covers and Why Contractors Do Not Break the Chain of Responsibility
Title II is broad by design. It covers anything a public entity does: direct services, contracted services, benefits administration, licensing, education, policing, corrections, courts, public meetings, transportation, recreation, and digital access. The Justice Department has consistently interpreted “services, programs, or activities” expansively, and courts generally do the same. That breadth is why a contractor relationship rarely changes the basic analysis. If the function is governmental in substance or delivered on the government’s behalf, the public still experiences it as a government program.
The legal logic is straightforward. Title II imposes duties on the public entity, not merely on the people it directly employs. The regulations also prohibit a public entity from using “criteria or methods of administration” that have the effect of discrimination. If an inaccessible vendor platform, exclusionary transportation policy, or poorly managed call center blocks access, the public entity cannot defend itself by pointing to the contract. The government chose the delivery method and remains accountable for the outcome.
This does not mean contractors are irrelevant. A contractor may have direct obligations under other laws, including Title III of the ADA if it operates a place of public accommodation, Section 504 if it receives federal financial assistance, Section 508 in certain federal technology contexts, state disability laws, or contract-based indemnity provisions. But as a matter of Title II, the public entity remains the hub of responsibility. That is why procurement language, oversight, testing, and complaint handling are as important as the original accessibility standard.
Core Title II Duties Public Entities Must Meet Through Contractors
Public entities must provide program access when viewed in its entirety. For existing facilities, that does not always require every building to be fully accessible, but the program as a whole must be accessible. For new construction and alterations, technical standards such as the 2010 ADA Standards for Accessible Design apply. If a city leases a community center run by a nonprofit contractor, inaccessible restrooms, routes, service counters, or seating remain the city’s problem unless corrected. The same principle applies to contracted polling locations, parks concessions integral to public recreation, and courthouse annexes managed by vendors.
Effective communication is another nondelegable duty. Governments must ensure communication with people with disabilities is as effective as communication with others, which may require auxiliary aids and services such as qualified sign language interpreters, real-time captioning, accessible electronic documents, Braille, large print, or screen-reader-compatible web content. If a hospital operated by a public authority uses a video interpreting vendor with frequent outages, or a town hall streamed through a contractor lacks captions, the public entity bears the compliance risk because residents are being denied meaningful access to communication.
Reasonable modification duties also persist when services are contracted out. A public transit agency cannot avoid modifying an eligibility rule for a rider with a disability simply because a private operator handles intake. A county jail cannot ignore disability-related medication access, mobility needs, or communication supports because correctional healthcare was outsourced. Agencies must also avoid unnecessary surcharges. They cannot make disabled users pay extra because a contractor charges more for accessible document remediation, alternate formats, or accessible transportation features required by law.
Common Contractor Scenarios Under Title II
The clearest examples arise in technology. Governments increasingly use third-party platforms for utility billing, court payments, permit applications, benefits enrollment, school communications, and virtual public meetings. If those platforms lack proper heading structure, form labels, focus indicators, captions, or error identification, residents with disabilities may be effectively shut out. Since April 2024, the Justice Department’s digital accessibility rule under Title II has provided specific technical expectations for web content and mobile apps, generally aligning with WCAG 2.1 Level AA, making vendor oversight even more urgent.
Transportation is another frequent pressure point. Public entities often contract for fixed-route operations, paratransit, shuttle services, or dispatch. Yet Department of Transportation ADA rules still require accessible vehicles where applicable, proper securement, maintenance of lifts, stop announcements, training, and nondiscriminatory service levels. I have reviewed contracts where the vendor promised compliance in a single sentence, but there were no audit rights, no response-time metrics, and no process for rider complaints. That is not governance; it is hope disguised as procurement.
Corrections and law enforcement create high exposure because disability access intersects with medical care, safety, communication, and due process. Counties regularly outsource jail healthcare, food service, transportation, and phone or video systems. Still, the jail must provide accessible housing, interpreters, TTY or equivalent communication access, mobility accommodations, and policies that do not punish disability-related conduct without individualized assessment. Similar issues arise in courts using third-party filing systems or remote hearing platforms that are incompatible with screen readers or lack live captioning.
| Contracted government function | Typical accessibility risk | Public entity duty |
|---|---|---|
| Online payments and forms | Inaccessible documents, unlabeled fields, keyboard traps | Procure accessible platforms, test regularly, remediate defects quickly |
| Paratransit operations | Denials, long trips, lift failures, poor driver assistance | Monitor equivalency, training, maintenance, and complaint data |
| Public meetings and events | No captions, no interpreters, inaccessible registration | Provide auxiliary aids, accessible venues, and advance request processes |
| Jail healthcare and communications | No interpreters, inaccessible medication procedures, inaccessible tablets | Integrate disability accommodations into operations and oversight |
| Parks and recreation management | Barrier routes, inaccessible counters, exclusionary rules | Ensure program access and modify policies when required |
What the Law and Enforcement Record Show
Several legal sources reinforce the rule that outsourcing does not eliminate Title II duties. The ADA statute itself imposes obligations on public entities. The Title II regulation at 28 C.F.R. Part 35 contains the anti-discrimination framework, including the ban on discriminatory methods of administration and the requirements for reasonable modifications, integrated settings, and effective communication. The 2010 ADA Standards govern new construction and alterations, and the 2024 web and mobile app rule clarifies digital compliance expectations. Federal agencies, especially the Department of Justice and Department of Transportation, have repeatedly enforced these obligations against public entities even where private companies delivered the challenged service.
Olmstead v. L.C., decided by the Supreme Court in 1999, is not a contractor case, but it remains foundational because it confirms Title II’s broad mandate against unjustified segregation and reinforces that public systems must be structured to provide access in integrated settings. Tennessee v. Lane, decided in 2004, underscored the seriousness of access to courts, a principle that extends to contracted courthouse functions such as remote appearance platforms and records systems. In more routine enforcement, DOJ settlement agreements often require municipalities, counties, school systems, and transit agencies to revise procurement practices, train staff, appoint responsible officials, and audit vendors instead of merely demanding contractor promises.
The practical lesson from enforcement is consistent: agencies get in trouble when they treat accessibility as a warranty rather than an operating requirement. A city may buy an accessible product that becomes inaccessible after an update. A county may have a compliant contract but no one reviewing monthly performance reports. A public university may provide interpreter services in classrooms but forget accessibility in athletics, orientation apps, housing portals, or emergency alerts. Title II compliance is operational, not ceremonial.
How Public Entities Should Structure Contracts and Oversight
The most effective approach starts before procurement. Agencies should define accessibility requirements in solicitations, not as an afterthought in boilerplate. For technology, that means naming the technical standard, requiring a current accessibility conformance report using the Voluntary Product Accessibility Template format, reserving rights to test with automated and manual methods, and making remediation timelines material terms. For built environments, it means tying design and construction work to the 2010 ADA Standards, state codes, and inspection checkpoints. For services, it means specifying interpreter availability, response times, training requirements, and complaint escalation procedures.
Contracts should allocate tasks clearly, but they should also preserve government control. Include representations of compliance, prompt notice of barriers, cooperation in investigations, records access, cure rights, and meaningful remedies for persistent failures. Avoid vague clauses stating only that the vendor will “comply with all applicable laws.” That language helps little when a resident cannot submit a permit application or board a vehicle. The contract should identify who provides auxiliary aids, who pays, how fast they must be delivered, and who can approve exceptions. If those decisions are left ambiguous, they are usually made too late.
Oversight must continue after award. I advise agencies to designate an ADA coordinator or accessibility lead for each major contract, run acceptance testing before launch, sample real user experiences, track complaints by disability issue, and review changes before deployment. Training is essential because procurement teams, IT staff, transit managers, detention administrators, and communications personnel each control different parts of compliance. Public entities should also maintain an accessible grievance process and publish contact information so residents can report barriers without navigating another barrier.
Limits, Defenses, and Hard Cases
Title II is demanding, but it is not absolute. Public entities do not have to take actions that would fundamentally alter a service, program, or activity, or impose undue financial and administrative burdens. However, those defenses are narrow, must be based on real evidence, and do not permit agencies to do nothing. Officials must consider alternative steps that would still provide access. In my experience, agencies invoke burden too quickly in contractor disputes, especially with legacy technology. Yet replacing a system may be costly while still legally necessary if the inaccessible platform is the main doorway to public services.
There are also edge cases about whether a function is sufficiently tied to a public program. A concessionaire in a park, for instance, may have its own separate obligations and may not always define the outer limit of the government’s program. But if access to the concession is effectively part of the public recreational offering, or if the contractor controls key points of entry to a public benefit, the risk to the public entity increases. The safest approach is to analyze the user journey from the resident’s perspective, because that is how exclusion occurs.
Another hard issue involves overlapping statutes. A school district, public hospital, or housing authority may face Title II and Section 504 simultaneously. Transportation providers may answer to DOT rules that are highly specific. State procurement laws may limit negotiation flexibility. None of that changes the central point. The government must build accessibility into vendor selection, contract administration, and service delivery from the start.
Why This Title II Hub Matters
As a hub for Title II: Public Entities, this page sets the framework for more detailed discussions about public websites, transportation, courts, policing, emergency management, schools, parks, voting, and correctional settings. Every one of those topics returns to the same rule: the public entity owns the ADA obligation even when a private company touches the resident experience. If you remember one sentence, make it this one: outsourcing work can redistribute tasks, but it cannot redistribute accountability under Title II.
The operational benefit of understanding that rule is enormous. Agencies that treat accessibility as a governance issue make better purchasing decisions, avoid emergency fixes, respond faster to complaints, and serve more residents effectively. They also reduce litigation exposure because they can document standards, testing, training, and corrective action. By contrast, agencies that rely on generic vendor promises often discover accessibility only after launch, after injury, or after an enforcement letter arrives. At that point, remediation is more expensive, public confidence is weaker, and the agency has less leverage over the contractor.
Use this article as your starting point for every Title II question involving vendors, delegated services, or third-party platforms. Review your contracts, map the public-facing user journey, test your highest-risk systems, and assign internal responsibility for oversight. Governments cannot outsource their ADA obligations, but they can manage contractors well enough to meet them. That is the practical path to lawful, durable, and genuinely inclusive public service.
Frequently Asked Questions
Can a state or local government avoid ADA Title II liability by hiring a private contractor?
No. A public entity cannot avoid its obligations under Title II of the ADA by delegating work to a private company. If a state agency, city, county, school district, transit authority, court system, or other public entity chooses to use a contractor to deliver services or operate programs, the public entity remains responsible for ensuring that people with disabilities have equal access. In practical terms, outsourcing does not change who must answer for discrimination, inaccessible systems, ineffective communication, or barriers that prevent meaningful participation in government programs and services.
This principle matters because governments now rely heavily on outside vendors for essential functions, including website development, call centers, transportation operations, parks and recreation management, detention healthcare, benefits administration, elections technology, and public-facing software platforms. Even when the contractor is the day-to-day operator, the program is still often a government program for Title II purposes. The public should not lose civil rights protections simply because the government chose to structure delivery through a contract rather than direct staffing.
That is why public entities need to treat contractor oversight as part of ADA compliance, not as a separate procurement issue. The government should build accessibility requirements into the contract, set clear performance standards, monitor compliance, respond to complaints, and require corrective action when problems arise. A contractor may create the barrier, but the public entity still carries the legal duty to make sure its programs, services, and activities are accessible.
If the contractor is the one that actually caused the accessibility problem, who is responsible?
In many cases, both the contractor and the public entity may face consequences, but the key point under Title II is that the public entity remains responsible for the accessibility of its own programs, services, and activities. If a private vendor runs a city website that is unusable with screen readers, if a contractor operating public transit fails to provide required accommodations, or if a third-party call center cannot communicate effectively with people who are deaf or have speech disabilities, the government generally cannot defend itself by saying, “That was the contractor’s fault.” From the perspective of the individual denied access, it is still a government service that was inaccessible.
Responsibility often depends on the legal claim being asserted, the role of the contractor, and the facts of the arrangement. A contractor might have direct obligations under other laws or under the contract itself, and indemnification clauses may allocate financial risk between the parties. But those private arrangements do not erase the government’s public-law obligations. Courts and enforcement agencies usually focus on whether the public entity ensured meaningful access, effective communication, reasonable modifications when required, and the absence of unnecessary eligibility barriers.
That is why governments should not rely on blame-shifting after a complaint is filed. The smarter approach is front-end prevention: accessible design standards, testing requirements, training, complaint procedures, remediation deadlines, and audit rights. If the public entity has no practical mechanism to identify and fix contractor-created barriers, it is taking on serious legal and operational risk. In ADA compliance, “the vendor caused it” is rarely a satisfying answer.
What kinds of contractor-operated services are most likely to create Title II accessibility issues?
The highest-risk areas are usually the ones the public uses every day or relies on for essential civic participation. Websites, mobile apps, online payment systems, permit portals, court access platforms, public meeting livestreams, digital documents, and emergency notification systems frequently generate accessibility problems because they are often built or maintained by outside technology vendors. If these systems are not accessible to screen reader users, people with low vision, people who are deaf or hard of hearing, or individuals with mobility or cognitive disabilities, the public entity may be denying equal access to core government functions.
Transportation is another major area. When a contractor operates fixed-route buses, paratransit, shuttle services, or dispatch systems for a public agency, accessibility failures can have immediate real-world consequences. Problems may include lift failures, improper securement, refusal to accommodate service animals, breakdowns in reservation systems, or staff who are not trained to assist riders with disabilities. The fact that operations are outsourced does not reduce the government’s duty to ensure accessible transportation services are actually being delivered.
Physical facilities are also common trouble spots. Contractors that manage parks, recreation centers, polling sites, libraries, healthcare services in public institutions, or public housing functions may create barriers through inaccessible routes, counters, restrooms, signage, communication practices, or policies that fail to allow reasonable modifications. Even seemingly administrative functions like outsourced intake, scheduling, document processing, and customer support can become barriers if they exclude people who need alternative formats, auxiliary aids and services, or flexible procedures. The lesson is simple: if the public interacts with it as a government service, it should be reviewed through a Title II accessibility lens, even if a private company runs it.
What should a government include in its contracts to help meet Title II ADA obligations?
A strong contract should do much more than contain a generic statement that the contractor will “comply with the ADA.” That kind of boilerplate is usually not enough. The contract should identify specific accessibility obligations tied to the service being provided. For digital services, that may include technical accessibility standards, testing protocols, remediation deadlines, user acceptance criteria, accessibility documentation, and ongoing maintenance duties. For transportation, facilities, customer service, or program operations, it may include training requirements, communication protocols, accommodation procedures, equipment maintenance standards, and incident reporting obligations.
Just as important, the contract should give the public entity meaningful oversight tools. These may include audit rights, inspection rights, complaint tracking requirements, mandatory cooperation in investigations, corrective action plans, service-level metrics, and consequences for noncompliance. If accessibility is important enough to promise the public, it should be important enough to measure and enforce. A contract that lacks monitoring and enforcement mechanisms leaves the government in the weak position of having legal responsibility without operational control.
Governments should also think carefully about how accessibility will be maintained after launch or deployment. Many failures occur not because the initial product was inaccessible, but because updates, staffing changes, third-party integrations, or new policies eroded access over time. A good contract addresses training, change management, subcontractors, records retention, accessibility support contacts, and prompt remediation obligations. In short, the contract should reflect the reality that accessibility is an ongoing performance requirement, not a one-time procurement checkbox.
What practical steps can public entities take to make sure they do not “contract away” accessibility in real life?
The first step is to recognize that ADA compliance must be integrated into procurement, implementation, and oversight from the beginning. Accessibility should be part of vendor selection, not an afterthought once the service is already live. That means asking detailed questions during the bidding process, requiring evidence of accessibility competence, evaluating past performance, and making accessibility a scored criterion where appropriate. Governments should avoid selecting vendors based solely on cost when the result is a program that excludes people with disabilities.
Once a contractor is engaged, the public entity should establish clear internal ownership for ADA oversight. Someone needs responsibility for reviewing accessibility deliverables, receiving complaints, coordinating remediation, and ensuring departments do not assume “the vendor is handling it.” Public entities should also provide training to their own staff so they understand that outsourcing does not transfer away civil rights duties. Procurement officers, IT teams, program managers, communications staff, and legal counsel all need to be aligned on this point.
Finally, governments should create systems for continuous monitoring and fast correction. That includes accessibility testing, user feedback channels, periodic audits, accommodation procedures, and documented escalation paths when barriers are reported. If a problem affects access to a public program, the entity should act quickly to provide an alternative method of access while the issue is fixed. The core legal and practical takeaway is straightforward: a government may hire a contractor to help deliver services, but it cannot outsource accountability for equal access. Under Title II, the obligation stays with the public entity.
