Accessibility Clauses in Vendor and Agency Contracts: Shifting Risk Before It Lands

When a demand letter names your store, the barriers often came from a vendor or agency. Contract clauses that assign accessibility responsibility before the work starts.

A store owner who receives a demand letter quickly discovers whose code is actually on the page. The theme came from an agency, the chat widget from a vendor, the popup from an app, and the store signed for all of it. Courts and plaintiffs look at the business whose name is on the storefront, which is why the time to sort out accessibility responsibility is in the contract, before any of that code ships.

Good clauses do not need to be hostile. They need to be specific: a standard to meet, a duty to fix, and a paper trail. Here is what to put in writing with the partners who build and supply your store.

Name the standard and the scope

A clause that says a site will be accessible is nearly worthless. Name the benchmark, usually WCAG 2.2 AA, name what it covers, templates, custom components, content types, and changes made during the engagement, and state when conformance is measured, at launch and after major revisions. For app and widget vendors, ask the same question in procurement: what standard does the product meet, and where is that claim documented?

Assign the fix duty and the clock

When a barrier in a partner's work is found, who fixes it, how fast, and at whose cost? Put remediation duties in the agreement: the vendor or agency corrects barriers in their deliverables within a set period after notice, and the store's job is prompt notice and reasonable cooperation. Without that sentence, every fix becomes a new negotiation held while a legal deadline runs in the background.

Evidence, testing rights, and honest claims

Contracts should give the store the right to test deliverables with automated scans and manual checks, and to receive the partner's own test results where they exist. Ban unapproved accessibility claims in the other direction too: no partner should publish that your store is compliant, and no overlay or widget should be described as making it so. Overstated claims surface in disputes and help nobody who made them casually.

Indemnity that matches the real exposure

Indemnity and limitation clauses decide who ultimately pays when a partner's barrier triggers a claim. These deserve real legal review rather than template copying, because enforceability varies and the cheapest contract often excludes exactly this risk. At minimum, flag accessibility claims in the risk conversation with counsel when a contract is signed, not after a letter arrives and the paper says what it says.

Related reading

If this topic is useful, these earlier guides go deeper on connected questions: Preparing an Accessibility Evidence Pack for Insurance and Counsel, What to Document After an Accessibility Remediation Sprint So It Holds Up Later, and Are Your Accessibility Scan Logs Discoverable? A Privilege Primer.

Frequently asked questions

Can a store shift ADA responsibility to its agency or vendors?

Not entirely. The business operating the store remains the visible target for claims. Contracts can assign fix duties and share financial responsibility between the parties, which matters a great deal, but they do not make the store invisible to a plaintiff.

What standard should contracts name for accessibility?

WCAG 2.2 AA is the most commonly referenced benchmark in agreements and settlements. The clause should also name scope and timing: which deliverables it covers and when conformance is assessed.

What should a store ask an app vendor before installing?

Ask what accessibility standard the product meets, whether it has a current conformance report, how barriers are reported, and how quickly fixes ship. Get the answers in writing during procurement, not after an issue appears on your store.

Do contract clauses prevent demand letters?

No clause prevents a letter. Clauses change what happens next: fixes are faster, duties are clear, evidence exists, and cost sharing was agreed in advance. That is the difference between a managed problem and a scramble.