When the Justice Department pushed back the ADA Title II web and mobile app deadlines in April 2026, a lot of public entities heard “one more year.” The first new date, 26 April 2027, is now about five months away. For most state and local governments and public colleges, the hardest part of meeting it is not the pages their own staff build. It is the payment portal, the permit system, the learning platform, the agenda software and the mobile app that someone else built and the entity merely licenses.
A 2 November commentary in Route Fifty made this point well: procurement is where Title II compliance is quietly won or lost. This post is the practical follow-up. It sets out what the rule actually says about vendors, what to require in contracts, how to read a vendor’s Accessibility Conformance Report (ACR) critically, and a short clause checklist. If you want the background on the extension itself, our earlier guide to the deadline extension covers it.
A note before the detail: this is general information, not legal advice. Contract terms, especially indemnity and limitation of liability, depend on your state’s procurement law and your existing terms. Talk to your counsel and procurement office before adopting any language.
The rule at a glance
- Regulation: 28 C.F.R. part 35, subpart H (sections 35.200 to 35.205), adopted by the Justice Department in April 2024.
- Standard: WCAG 2.1, Level A and Level AA success criteria and conformance requirements.
- Compliance dates: 26 April 2027 for public entities with a total population of 50,000 or more; 26 April 2028 for entities under 50,000 and for all special district governments. These come from an interim final rule published on 20 April 2026, which extended each date by one year and, in the department’s words, did not alter any other provision of the 2024 rule.
- Who is responsible: the public entity, for web content and mobile apps it provides or makes available “directly or through contractual, licensing, or other arrangements” (35.200).
- Still open: the department has said it plans further rulemaking on the rule’s substance and may issue a proposed rule during the extension period. Separately, the National Federation of the Blind sued in May 2026 asking a federal court in Maryland to vacate the extension. As far as we know that case is pending. Either could change the picture, which is one more reason not to plan around the latest possible date.
Why the vendor’s product is your problem
The phrase “contractual, licensing, or other arrangements” appears in both the general requirement and the dated compliance requirement in 35.200. The department’s own guidance on ADA.gov spells out what it means in practice: a public entity remains responsible for the accessibility of its web content and apps even when it outsources the work, and it cannot contract away its ADA responsibilities. Its examples are ordinary. A university that sends students to a third-party site to pay tuition is providing that page through an arrangement, so it needs to pick an accessible one. A township that offers residents a parking app it did not build and does not own generally must choose one that meets WCAG 2.1 AA.
The exceptions in 35.201 do not offer a way out either. The exception for content posted by a third party expressly excludes third parties posting because of a contractual, licensing or other arrangement with the entity. The ADA.gov fact sheet lists calendars, maps, reservation systems and payment systems as examples of third-party tools that are not exempt. The other four exceptions (archived content, older documents not used to access services, individualized secured documents, and older social media posts) do not cover the systems residents use to get things done.
Three other provisions matter when you negotiate. Section 35.202 allows a conforming alternate version only where technical or legal limitations make direct accessibility impossible, so a vendor offering “a separate accessible version” instead of fixing the main product should be asked which limitation applies. Section 35.203 permits alternative designs that give substantially equivalent or greater accessibility and usability. Section 35.204 lets an entity rely on undue burden or fundamental alteration, but only through a written statement of reasons reached by the head of the entity or a designee, and the entity still has to provide access to the maximum extent possible. A vendor’s cost is not your undue burden. And 35.205, which excuses defects with only a minimal impact on access, is a narrow safety valve, not a contract standard.
What the Justice Department says has worked
Action Step 10 of the department’s “First Steps” guidance for state and local governments is about vendor contracts. It tells entities to review existing contracts and decide whether a vendor can produce accessible content or needs replacing. It then lists approaches that public entities reported using successfully during the rulemaking: requiring detailed accessibility information before signing, asking for a warranty of conformance with technical standards and accessibility laws, prohibiting vendors from disclaiming those warranties, requiring indemnification for breach, and testing vendor products and publishing the results. The department adds that it does not recommend or endorse any particular approach. Action Step 3 makes a related point: procurement staff, not just IT, decide whether accessible products get bought.
Borrow from federal Section 508 procurement, with one fix
Federal agencies have bought accessible technology under Section 508 for years, and GSA publishes the playbook on Section508.gov. Its Accessibility Requirements Tool (ART) generates customised solicitation language, and its sample clauses cover custom development, installation and configuration, maintenance upgrades, hosting, validation testing, conformance reporting and non-compliance. Several are directly reusable: upgrades and replacements must not reduce the level of conformance at award; hosting must not reduce the conformance of the agency’s content; the agency reserves the right to test independently before acceptance; and non-conforming items are repaired or replaced at no cost within a period the contracting officer sets.
The fix: the Revised 508 Standards incorporate WCAG 2.0, while Title II requires WCAG 2.1. WCAG 2.1 added 12 Level A and AA success criteria, including reflow, non-text contrast, text spacing, orientation, input purpose and status messages. If you paste in federal language unchanged, or accept an ACR that only reports against WCAG 2.0, those 12 criteria fall out of the contract. Replace “Revised 508 Standards” with “WCAG 2.1 Level A and AA” (or a later version) wherever it appears.
A real state example: Idaho
Idaho’s Office of Information Technology Services published contract language in March 2026 that it says must go into all agreements where a deliverable is a digital asset. It requires WCAG 2.1 AA as a minimum; an accurate ACR built on the VPAT Revised Section 508 Edition, version 2.3 or higher, based on the current product version; vendor testing with both automated tools and manual methods, including screen readers, with barriers fixed before final acceptance; remediation of known violations during the term at no cost to the state; advance documentation of how updates will affect accessibility; and accessible training materials. Remedies include withholding payment, termination without penalty and remediating at the vendor’s cost, and an optional indemnification clause is offered.
What to require: a clause checklist
Use this as a list of topics for your counsel and procurement office, not as finished wording.
- Standard and scope. Conformance with WCAG 2.1 Level A and AA for everything the public will use, including admin-facing screens your staff need, documents the system generates, emails, and mobile apps. Name later versions as acceptable.
- Warranty for the full term. A warranty that the product conforms at delivery and continues to conform through every release during the contract, with no disclaimer of that warranty elsewhere in the vendor’s terms.
- An ACR before award. Built on the current ITI VPAT (version 2.5Rev, released April 2025), using the WCAG or International edition, or a 508 edition that reports the WCAG 2.1 criteria. It must cover the exact product and version you are buying.
- Your right to test. The right to test the product yourself or through an independent third party, before acceptance and at any time during the term, with access to a test environment.
- Remediation timelines. Defined fix windows by severity (for example, a shorter window for barriers that block a task entirely), a written remediation plan for any known gap at signing, and fixes at no additional cost.
- Updates and new features. Updates must not reduce conformance, the vendor must tell you in advance how a change affects accessibility, and the ACR must be refreshed when the product changes materially.
- Accessible support. Accessible documentation and training, and a way for residents and staff to report accessibility problems that reaches the vendor.
- Remedies. Acceptance tied to accessibility, plus payment withholding, cure periods, termination rights and the right to remediate at the vendor’s cost.
- Indemnity: talk to counsel. DOJ and Idaho both mention indemnification for breach of accessibility warranties. Whether it is enforceable or worth the price in your state, and how it interacts with liability caps, is a legal question. It also does not move your ADA responsibility to the vendor: you remain the one residents can complain about.
How to read an ACR without being fooled
ITI is clear that there is no official certification or approval for a VPAT or ACR, and that ITI does not review completed reports. An ACR is the vendor’s own claim. GSA’s guidance on vendor claims explains the conformance terms: “Partially Supports” means the product does not conform to that criterion, “Not Evaluated” provides no assurance at all, and “Not Applicable” should come with a reason. GSA also advises purchasers to verify claims with independent testing wherever possible. With that in mind, these are the red flags we look for:
- Every row says “Supports”. Almost no real product of any complexity fully conforms to every criterion. A clean sweep usually means nobody tested carefully.
- No evaluation method. The VPAT asks for the evaluation methods used. A blank, or a single sentence naming an automated scanner, is a problem. Automated tools find only part of WCAG failures; keyboard use, focus order, screen reader output and meaningful alt text need people.
- No date, version or author. An undated ACR for “the platform” could describe a product that no longer exists. Ask who prepared it, when, and against which release.
- Only WCAG 2.0 criteria. Check that the 12 WCAG 2.1 A and AA criteria appear. If they are missing, the report does not address the Title II standard.
- Remarks that say nothing. A “Partially Supports” with no explanation tells you nothing about whether the gap blocks a resident from paying a bill. Ask for the specific issues and a fix date.
- Excluded features. Watch for scope notes that leave out the parts residents actually use, such as checkout, file upload or the mobile app.
Then test the parts that matter. You do not need a full audit of every vendor before award. A focused check of the main task flows with a keyboard and a screen reader, plus an automated scan, will tell you quickly whether an ACR is credible. Our URL accessibility auditor can handle the automated part for public pages, and the automated versus manual testing guide explains what a scan cannot catch.
What to do before April 2027
- Inventory every system that residents, students or applicants use and that a vendor supplies or hosts. Note contract end dates and renewal windows.
- Request current ACRs for the highest-traffic and highest-stakes systems first: payments, applications, permits, benefits, courts, enrollment and learning platforms.
- Spot-test those systems against the red flags above, and log the gaps you find.
- Use renewals and amendments to add accessibility terms, and put the clause checklist into every new solicitation now.
- Train procurement staff, whom the department’s guidance names as key players.
Further reading on Accessibility.build
- Our guide to VPATs and ACRs walks through the template section by section.
- See how the ADA applies to digital services on our ADA compliance page.
- For the federal side, read our Section 508 overview.
- The court decisions behind digital ADA coverage are collected in our ADA case law reference.
- Track how disability litigation is trending in the accessibility lawsuit tracker.
If you would rather start from editable documents than a blank page, our ADA Title II Web Accessibility Compliance Kit includes procurement clauses and vendor letters alongside the policy, notice and 35.204 statement templates. As with everything here, have your counsel review the final wording.
Sources
- eCFR: 28 C.F.R. part 35, subpart H, Web and Mobile Accessibility, sections 35.200 to 35.205 as amended 20 April 2026 (XML, current text)
- Federal Register: Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities, interim final rule, 91 FR 20902 (20 April 2026)
- US Department of Justice, ADA.gov: State and Local Governments: First Steps Toward Complying with the ADA Title II Web and Mobile Application Accessibility Rule (8 January 2025, updated April 2026)
- US Department of Justice, ADA.gov: Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments (April 2024, updated for the 2026 extension)
- GSA, Section508.gov: Buy Accessible Products and Services (reviewed October 2026)
- GSA, Section508.gov: Define Accessibility Criteria in Contracts (reviewed March 2026)
- GSA, Section508.gov: Understanding Vendor Claims in Accessibility Conformance Reports for Section 508 Conformance
- GSA, Section508.gov: How to Create an ACR with a VPAT
- Information Technology Industry Council: VPAT (VPAT 2.5Rev, April 2025)
- Idaho Office of Information Technology Services: Digital Accessibility Agreement Language (Ver. 1, rev. 3/26)
- W3C Web Accessibility Initiative: What’s New in WCAG 2.1
- Brown, Goldstein & Levy: Complaint, National Federation of the Blind v. Department of Justice, No. 1:26-cv-02007 (D. Md., filed 21 May 2026)
- Route Fifty: Extended ADA Title II deadline demands a focus on procurement (commentary, 2 November 2026)