Procurement Language That Actually Works

The highest-leverage thing you'll do all year, and it costs nothing.

I said in an earlier piece that your city mostly buys rather than builds, and I want to sit on that for a second because it's the single most important fact about this job that nobody tells you up front. You are not, mostly, in the business of fixing broken things. You are in the business of a few hundred vendor contracts, most of which were signed by someone who never thought about accessibility for a second, and every one of which is going to get renewed eventually — which means every one of them is a chance to fix the problem permanently instead of patching it forever.

That chance happens exactly once per contract: the moment of signature. After that, you're negotiating from nothing. Before that, a clause costs you literally nothing to ask for. Same document, same signature, same lawyer reading it either way. The only difference is whether accessibility was in the document when it got signed.

Here are the five clauses that do the actual work.

The standards representation

The product, as configured for you — not the marketing site, not the demo, the actual instance you're going to be using — meets WCAG 2.1 AA (opens in new window) or later, warranted, with a current conformance report per interface. I want to underline "as configured for you," because I've seen more than one vendor point to a beautiful accessibility statement about their platform in general while the specific modules your department actually uses were never tested. The representation has to be about your deal, not their brochure.

The remediation commitment

Defects get fixed at the vendor's expense, on a stated timeline by severity, and that commitment survives future upgrades. Without that last part, you'll fix something, the vendor pushes an update six months later, and you're right back where you started — except now it's a change order instead of a warranty claim. Get it in writing that this doesn't reset every release.

Acceptance testing

You test the final, actually-configured deliverable before you sign off. Not the demo instance, not a sales environment set up to look good. The thing you're actually going to run. This sounds obvious until you realize how often it doesn't happen, because everyone's excited to launch and testing feels like the thing slowing down the finish line.

Remedies with actual teeth

Cure period, cost deduction, non-renewal, termination, and indemnification if they misrepresented what they sold you. A promise with no consequence attached isn't a promise. It's marketing copy with a signature block.

The silence default

This one's my favorite, and it's borrowed language — Texas administrative code, if you want to look it up. One sentence: if a vendor can't produce credible accessibility documentation, the product is treated as non-conforming. That's it. That's the whole clause. What it does is take "we'll get back to you on that" — which every vendor has said to every coordinator, probably this week — and turn it from a shrug into a finding. Silence stops being free.

None of this is legal advice, and none of it should go into a contract without your counsel reading it first. But the concepts are yours to bring to that conversation, and most counsel I've talked to are relieved someone finally handed them specific language instead of a vague ask to "make sure it's accessible."

The part everybody forgets: the calendar

Here's the thing about clauses — they only fire the moment a contract gets signed. Which means the second procurement artifact you need isn't a clause at all. It's a calendar. Every digital contract you've got, its renewal date, its notice window, and whether it's already carrying these clauses or not.

Ninety days before each renewal, the vendor gets the accessibility documentation request and the clause language, together, before the renewal conversation starts. Miss that notice window and your leverage goes back to sleep for another contract term — sometimes years. I've watched a coordinator lose an entire renewal cycle because the notice window closed while the request was still sitting in a draft folder. The calendar isn't paperwork for its own sake. It's the only thing that lets one person run procurement pressure across dozens of vendors without becoming a full-time contract lawyer.

What this actually buys you

I want to be honest about the limits here, because overselling this would be its own kind of compliance theater. Procurement language doesn't fix what's already broken. It doesn't touch the backlog sitting behind you right now. What it does is stop the bleeding — every dollar you spend from today forward on something that already has these terms attached is a dollar that isn't buying you a new problem to add to the pile.

That's not a small thing. It's the difference between a backlog that's finite and one that keeps growing faster than you can work it down. Get the clauses into your standard templates this month, not after the next renewal. It costs you an afternoon and a conversation with your attorney. It is, genuinely, the highest-leverage thing available to you, and it's sitting right there, free, waiting on a signature you were going to get anyway.

Before you send a request-for-proposal out the door, it's worth checking what an Accessibility Conformance Report (opens in new window) actually looks like so your RFP language asks for the right thing — the next piece in this series walks through reading one. And if a vendor hands you a report you want a second opinion on before you take it to counsel, ask Luke to check it against what you were actually promised. See our methodology for how we verify claims like these.

Previous: document inventory and triage · Next: how to read a VPAT

---

Sources: Web Content Accessibility Guidelines (WCAG) 2.1 (opens in new window) · Accessibility Conformance Report (ACR) overview (opens in new window) · How to Create an ACR Using a VPAT (opens in new window) · U.S. Access Board — Revised 508 Standards (opens in new window)