Questions · Procurement, updates and cost
A university wants an accessibility roadmap with our VPAT. What should it include?
One line for each barrier your ACR reports as Partially Supports or Does Not Support: what the barrier is, its repair status (planned, deferred…), a target date, and the workaround users have meanwhile. California State University San Marcos lists those four components; the University of Nevada, Reno also asks for your strategy and may require an alternative access plan.
What three public universities publish
- Cal State San Marcos: a roadmap gives the vendor’s expected timelines to correct the barriers in a product. Essential components: a description of the barrier, its current development status (planned, deferred, etc.), the timeline to complete, and existing workarounds. The CSU Accessible Technology Initiative offers vendors a roadmap template.
- University of Nevada, Reno: a VPAT or ACR is required for every ICT purchase and renewal. If any applicable criterion is “Partially Supports” or “Does Not Support”, the department must obtain a remediation plan that identifies the known barriers, describes the vendor’s strategy and gives target dates. A non-conformant product also needs an Equally Effective Alternative Access Plan (interim access, the vendor’s remediation commitments), which the vendor signs.
- University of Arizona: buyers collect vendor VPATs (WCAG 2.1/2.2 or EN 301 549), accessibility roadmaps and a demo recording with assistive technology, check that remediations have timelines, and write remediation milestones, reporting cadence and termination options into the contract.
Building it from your ACR
| Column | Source |
|---|---|
| Barrier | Each Partially Supports or Does Not Support row, whose remark should name the functions or features with issues |
| Status | Your own backlog: planned, in progress, deferred |
| Target date | A release or month you can keep, since a buyer may make it a contract milestone |
| Workaround | What a user can do today, and whom to contact |
Keep the roadmap and the ACR on the same product version and date them both. A deferred item with an honest workaround reads better than a date you miss at renewal.
How ACR Desk handles this
Our ACR gives every Partially Supports or Does Not Support row a specific remark, and the prioritized fix list names each issue, where it is, the criterion, who it affects and how to fix it: the barrier column of your roadmap, in priority order. You set the status and the dates; we don’t write your code or sign plans for you. One retest within 90 days updates the ACR. Web-based products only. $1,490 (WCAG edition) or $1,990 (Section 508, EU or INT), fixed, in 5 business days.
Last reviewed: October 26, 2026. Not legal advice: rules change, and your buyer’s solicitation or contract governs what they require.
Sources
Primary sources only. Each was read on October 26, 2026.
- VPAT Vendor Requirements (accessibility statement, accessibility roadmap, product demonstration) — California State University San Marcos, Instructional and Information Technology Services.
- ICT Procurement Process (VPAT, vendor remediation plan, EEAAP) — University of Nevada, Reno, Office of Digital Accessibility.
- Procurement & Vendors (VPATs, accessibility roadmaps, contract addendum) — The University of Arizona, Digital Accessibility.
- VPAT® 2.5Rev WCAG edition (April 2025) — template and Essential Requirements for authors (Word file) — Information Technology Industry Council (ITI).