---
title: accessiBe - The government org and agency accessibility procurement checklist
---

| ![accessiBe](https://lp.accessibe.com/hubfs/accessiBe%20Logo/brand=accessiBe%2c%20type=white%2c%20mono=true%2c%20by%20accessiBe=false%2c%20dark%20mood=true.svg) # Building a defensible procurement strategy under ADA Title II |
| --- |

![](https://lp.accessibe.com/hs-fs/hubfs/image%20(1)-Feb-16-2026-09-49-20-3178-AM.png?width=423&height=387&name=image%20(1)-Feb-16-2026-09-49-20-3178-AM.png)

The DOJ has extended ADA Title II compliance deadlines by one year — April 26, 2027 for larger entities, April 26, 2028 for smaller ones. The standard didn't change: all web content and mobile apps must conform to WCAG 2.1 Level AA. And the vendor accountability gap didn't move either. Most agencies rely on outside vendors for essential tools — and [under Title II, your organization is still responsible for the accessibility of those services](https://www.ada.gov/resources/small-entity-compliance-guide/#:~:text=If%20you%20have,under%20the%20ADA.), regardless of who built them.

**The deadline moved. The procurement obligation didn't**

## 01. Build leverage early

 If you wait until a website is built to think about accessibility, you have already lost your primary source of leverage.  You must decide that accessibility is a core requirement before you even start looking for a solution.  Once you’ve done that, you should:

Define the standard In every RFP and project brief, explicitly state that all deliverables must conform to WCAG 2.1 Level AA.

Assign weight to accessibility When scoring vendor bids, give accessibility the same importance as security or cost. If a product isn't accessible, it isn't functional.

Set the expectation Make it clear to potential partners that accessibility defects are showstoppers that can pause project milestones or payments.

![](https://lp.accessibe.com/hubfs/lightbulb.svg)

 Why this matters  Procurement is the decisive moment where your agency either builds leverage or inherits long-term remediation debt. [Under the DOJ's Title II rule, you are legally responsible for accessibility even when services are delivered through third-party platforms](https://scholarworks.sfasu.edu/cgi/viewcontent.cgi?article=1031&context=txdla_jdl). If WCAG 2.1 Level AA requirements are not in the contract upfront, you lose power to compel fixes later and your staff is stuck with manual workarounds while the agency carries the legal risk.

## 02. Share the responsibility correctly

 A successful strategy relies on a clear division of labor. By defining roles upfront, you ensure that when a barrier is found, there is a clear path to a fix rather than a cycle of finger-pointing.  In practical terms, this means dividing ownership as follows:

The vendor's job (The Platform) The vendor is responsible for the code, navigation menus, and overall framework.  They must ensure their ״engine״ supports your WCAG 2.1 AA obligations.

Your job (The Content) Your team is responsible for the content you put inside that engine. This includes the text you write, the images you upload (ensuring they have alt text), and the accessibility of any PDFs or videos you post— including any content created using AI tools, which isn't accessible by default.

![](https://lp.accessibe.com/hubfs/lightbulb.svg)

 Why this matters  Shared responsibility does not mean shared liability. [Under the ADA, the public entity remains accountable for the citizen experience](https://www.ada.gov/resources/small-entity-compliance-guide/). A clear division of labor prevents "structural risk," where accessibility barriers fall into gray areas and never get fixed. By defining these roles, you ensure the vendor owns the platform-level code while your team focuses on content governance. This creates a defensible "evidence trail" showing regulators that you are exercising active oversight rather than relying on blind faith in a vendor.

## 03. Write accountability into the contract

 Don't rely on a vendor's verbal promise. Your contracts should include enforceable language that protects your agency and provides a safety net if a product falls short of the required standards.  To create this legal protection, your agreements should include:

A commitment by the vendor to fix any accessibility bugs in their software at their own expense, not yours.

A rule that future software updates must not break or remove any existing accessibility features.

A "gatekeeper" clause that allows you to delay a launch if the product fails a final accessibility test.

![](https://lp.accessibe.com/hubfs/lightbulb.svg)

 Why this matters Contractual accountability is the only way to shift the cost of remediation back to the vendor. Without these clauses, accessibility barriers become a permanent "remediation debt" that your agency must pay for through manual workarounds or expensive third-party retrofitting. Treating accessibility as a standard product defect—with defined fix timelines and "go-live" authority—ensures that accessibility issues have a clear owner and a resolution deadline, transforming them from legal liabilities into manageable technical tasks.

## 04. Verify vendor claims

 Most vendors will provide a VPAT (Voluntary Product Accessibility Template) to show their product is accessible. Once a vendor fills out a VPAT, it becomes an ACR (Accessibility Conformance Report).  You must treat this document as a starting point, not a guarantee.  To ensure you aren't stuck with a vendor's mistakes, you should:

Verify the version Check that the report matches the exact software version you are buying. If a vendor gives you a report from an older version, ask for the current one.

Look for ״remarks״ A reliable report doesn't just say "Supports"—it explains how the feature works for people with disabilities in the "Remarks" column. If the notes are blank, the product hasn't been properly tested.

Challenge ״perfect״ scores No complex software is 100% accessible. If a vendor claims total support with zero known issues, ask them to provide their testing methodology or a roadmap for future fixes.

![](https://lp.accessibe.com/hubfs/lightbulb.svg)

 Why this matters Vetting vendor paperwork is the final check against "reactive" risk management. A VPAT is only as good as the audit that created it; empty "supports" columns or outdated version numbers are red flags that the vendor has not done the work. By verifying these claims, you ensure your agency is purchasing enforceable accountability rather than a paper shield. accessiBe can support this step by providing expert manual audits and helping you fill out an accurate VPAT, turning your ACR into a living, public record of your due diligence and proactive compliance strategy.

To help you maintain a defensible posture, accessiBe provides professional support for your documentation and auditing needs.

Our experts conduct manual testing to identify barriers that automated tools might miss and help you fill out a VPAT accurately. Once completed, these ACRs live on your website as a public record of your accessibility efforts and a key piece of your compliance strategy, ensuring your documentation remains current as your digital services evolve.

## Conclusion: What a strong strategy looks like for 2027

With the April 2027 deadline now set, a defensible strategy isn't about achieving instant perfection. It's about proving your agency has an active, documented process for managing accessibility risk — and using this window to build it.