Procurement Language That Actually Works for Edtech

Jeff Fryer
procurementk12 accessibilityedtechnimasvendor management

Trust note

This article was written by a person and reviewed against accessibility.chat editorial standards. Treat it as research and education rather than legal advice. We prioritize primary sources and correct material errors.

Two young volunteers nurturing a potted plant. Man holding, woman watering.
Photo by Mikhail Nilov on Pexels

Dozens of vendors are your largest accessibility surface, and the district controls none of their code. This is the one lever you actually have.

I said in the law piece that edtech vendors are the sector gotcha here, and I want to make the case for why procurement language matters more in K-12 than almost anywhere else in this series. Your digital footprint isn't mostly built in-house. It's mostly bought — curriculum platforms, the LMS, communication tools, assessment software — and every one of those contracts renews eventually. The renewal is your chance to fix the problem permanently, and it happens exactly once, at signature.

The five clauses, plus one that's specific to this sector

Standards representation. The product, as configured for your district, meets WCAG 2.1 AA (opens in new window) or later, warranted, with a current conformance report per interface — not the vendor's marketing site.

Remediation commitment. Defects fixed at vendor expense, on a stated timeline, surviving future upgrades.

Acceptance testing. On the final, configured deliverable — the actual instance students and parents will use, not a sales demo.

Remedies with teeth. Cure period, cost deduction, non-renewal, termination, indemnification for misrepresentation.

The silence default. If a vendor can't produce credible accessibility documentation, the product is treated as non-conforming. One sentence that turns "we'll get back to you" from a shrug into a finding.

And the one specific to this sector: NIMAS contract language in every digital instructional-materials purchase, not just textbook adoptions. Federal guidance (opens in new window) has clarified that "print instructional materials" includes digital instructional materials, which means the timely-manner delivery requirement for students who need specialized formats applies to your curriculum platform purchases too — it's easy to assume NIMAS is only a textbook-adoption concern, and that assumption is exactly what leaves individual students waiting.

None of this is legal advice — bring these concepts to your district's counsel before anything goes into a contract, and at least one state now requires accessibility specifications and vendor conformance reports in every digital-tool bid directly by statute, so check your state's requirements too.

The renewal calendar

Every digital contract, its renewal date, its notice window, whether it carries these clauses yet. Ninety days before each renewal, the vendor gets the accessibility documentation request and the clause language together. Miss the window and your leverage sleeps for another contract term — sometimes years, across dozens of vendors, which is exactly why one person needs a calendar rather than trying to remember it all.

If a vendor hands you a report you want a second opinion on before you take it to your technology director, ask Luke to check it. Our methodology covers 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) · NIMAS Regulation — 34 CFR 300.172 (opens in new window) · Accessibility Conformance Report (ACR) overview (opens in new window) · 34 CFR Part 104 — Section 504 Regulations (opens in new window)

About Jeff Fryer

Jeff Fryer spent years working kitchens before moving into ADA compliance work for local government. He writes from that experience -- direct, plainspoken, allergic to compliance theater. Contributing writer at accessibility.chat.

Jeff Fryer is a person, not one of the AI analyst lenses this site also publishes under. A named human is accountable for this article.

Specialization: Local government ADA compliance, contributed from direct field experience

Authorship and Editorial Process

Jeff Fryer wrote this article. AI was not used to draft it. It went through the same editorial checks as everything else published here.