Vendor responsibilities and procurement

The procurement angle

Procurement is the lever public entities have to push accessibility upstream into vendor products and services. Title II does not directly bind vendors. It binds the public entity. But every vendor selling to public entities operates in a market where the buyer is now accountable for accessibility, which changes vendor incentives and reshapes what reasonable contract terms look like.

Two procurement realities follow from Title II coverage of third-party content:

1. The entity needs to evaluate vendor accessibility before buying. A contract with a vendor whose product has known accessibility failures imports those failures into the entity's compliance posture.
2. Contract language needs to address accessibility prospectively: at delivery, on updates, on remediation timelines for newly discovered issues, on documentation.

What Title II changes for vendors

The 2024 rule does not impose direct obligations on vendors as private entities. (Private vendors are covered by Title III of the ADA, not Title II.) What changes for vendors is the market: public entity buyers now have a regulatory reason to require accessibility, evaluate it during procurement, and walk away when it is not present.

Several practical consequences:

• VPATs and Accessibility Conformance Reports become standard procurement artifacts, not optional addenda
• RFPs include explicit WCAG 2.1 AA conformance requirements with documentation expectations
• Contracts include accessibility representations, ongoing reporting, and remediation obligations
• Renewal decisions consider accessibility track record alongside other vendor performance metrics
• Vendors who serve public entity markets without addressing accessibility face progressively fewer winning bids

Products, platforms, and content in scope

The vendor accessibility question applies broadly to anything the entity provides through a vendor arrangement:

Platforms and software

Content management systems, learning management systems, student information systems, ERP/finance systems, HR portals, document management systems, library catalogs, application platforms. The vendor's product is in scope where the entity uses it to provide content to the public or to employees.

Authoring tools

Tools that the entity uses to author content. An authoring tool that produces inaccessible output by default forces the entity into manual remediation. An authoring tool with accessibility built in (good defaults, validation, support for alt text and headings) shifts effort upstream.

Vendor-supplied content

Documents authored by a vendor and delivered to the entity for publication: vendor reports, study results, technical evaluations, white-label materials. The entity is responsible for accessibility once it publishes them; procurement language should require accessible delivery rather than imposing remediation cost on the entity post-receipt.

Hosted services

Services where the vendor hosts the content (video platforms, survey tools, form builders, scheduling systems). The vendor's UI and platform-level accessibility are part of what the entity is providing to users.

How contracts should address accessibility

A contract that addresses accessibility seriously typically covers:

Conformance representation at delivery

The vendor represents that the product or content conforms to WCAG 2.1 Level AA at delivery, supported by a current VPAT or ACR.

Ongoing conformance during the term

The vendor represents that updates, new releases, and ongoing content additions will maintain WCAG 2.1 AA conformance. Updates that introduce new accessibility issues are remediation triggers, not new normal.

Remediation timelines

For accessibility issues identified during the contract term, the vendor commits to remediation within defined timelines (e.g., 30 days for blocking issues, 90 days for non-blocking issues). The timelines should match the operational impact, not be vendor-favorable defaults.

Documentation obligations

The vendor provides current VPATs or ACRs annually, or on substantial product change. The vendor provides remediation plans when conformance gaps are identified.

Reporting

The vendor reports accessibility issues identified by the vendor's own testing or by user feedback, on a defined cadence. Hidden issues become contract issues.

Audit rights

The entity retains the right to commission independent accessibility audits and to share findings with the vendor with defined remediation expectations.

Termination for material accessibility failure

Sustained failure to meet accessibility conformance, after remediation opportunities, is a material breach that supports termination. This is the procurement lever that gives the other terms force.

What vendor responsibility means in practice

Vendor responsibility is contractual responsibility, not legal-liability transfer. Three implications:

The entity remains the responsible party under Title II

A contract clause that "assigns" Title II liability to the vendor is not legally effective. If the public-facing content is inaccessible, the public entity is the one DOJ, OCR, or a private plaintiff sues. Contract claims against the vendor are a separate matter, brought after the entity has addressed the underlying accessibility issue.

Vendor remediation cost recovery is contract law, not ADA law

When a vendor's product fails accessibility expectations, the entity's recourse is the contract: remediation obligation, credits or refunds, termination, indemnification clauses where present. None of this happens automatically; it requires the contract to provide for it.

Vendor selection compounds across the portfolio

A vendor that takes accessibility seriously reduces the entity's ongoing accessibility cost across every interaction with that product over the contract term. A vendor that does not increases it. The procurement decision is a long-tail cost decision, not a one-time check.

Next steps