HECVAT is a higher-education vendor-risk questionnaire; VPAT® is an accessibility reporting template whose completed, test-backed product report is an ACR. A buyer may request both. Before reusing either document, check which product, modules, deployment and release it describes—and whether that matches what the institution is buying.
For a SaaS vendor, that last step matters as much as knowing the acronyms. A report about your public website does not automatically describe your authenticated application. A questionnaire covering a shared cloud service may need explanation before a buyer can apply its answers to a separately deployed product.
This article focuses on that document-to-product match. Our separate VPAT versus ACR explanation covers the template/report distinction in detail.
HECVAT vs VPAT: compare the jobs they perform
EDUCAUSE describes HECVAT as a questionnaire for assessing vendor risk across cybersecurity, privacy, IT accessibility and related areas. ITI describes the VPAT as a way to record accessibility testing results for a product or service. The completed report is an Accessibility Conformance Report.
| Question | HECVAT | VPAT / completed ACR |
|---|---|---|
| What is being communicated? | Answers about the solution and the vendor practices relevant to it | How the specified product or service was evaluated against accessibility criteria |
| What does the reader receive? | A completed workbook and supporting information | An ACR identifying the evaluated product and its accessibility findings |
| Who contributes? | People who know the relevant product, security, privacy and accessibility details | People with the product knowledge and testing evidence needed to support the report |
| What needs a clear boundary? | Which products, deployment arrangements and answers are covered | Which product version, interfaces, functions and evaluation methods are covered |
| What does submission establish? | That information has been supplied for the institution’s review | That the report makes the stated accessibility findings within its documented scope |
The practical distinction: HECVAT is broader than accessibility, while an ACR gives accessibility detail. Neither file name tells you whether the material covers the exact product being purchased.
Keep the two connected without treating them as interchangeable. A statement about an accessibility process in a questionnaire is a different kind of evidence from a finding about a tested interface.
Does one HECVAT cover every product from the same vendor?
There is no useful universal answer based only on the vendor’s company name. Start with the receiving institution’s instructions and the response’s actual scope.
EDUCAUSE’s corporate FAQ says knowledgeable people should answer the questions applicable to the product or solution. It also explains that the institution evaluates responses against its own policies and risk appetite. That calls for a solution-specific reading, even where several products share infrastructure or organizational practices.
A shared response can be reasonable when it explicitly identifies the products it covers, distinguishes meaningful differences and is accepted by the buyer. Conversely, splitting a file into several copies does not improve the evidence if every copy repeats the same unexplained answers.
Two current institutional examples show why the request matters:
| Institution’s published guidance | What it means for a vendor responding there |
|---|---|
| University of Arkansas requests both HECVAT and VPAT/ACR for each individual product being purchased. Its guidance also provides pathways for alternative or missing documentation. | Follow that product-level request. Do not treat a general company document as automatically satisfying it, or assume missing documentation means no review can begin. |
| University of Michigan lists VPAT and HECVAT documentation, along with its supplier accessibility questionnaire. It asks reviewers to examine currency, methods, supported criteria and gaps. | Read the specific sourcing request and explain the evidence’s limits. Listing an accepted document type does not mean every submission of that type is sufficient. |
These are examples of their published processes, not a rule for every college or university. Ask the receiving reviewer how a multi-product or shared-service response should be presented.
Four product-scope mismatches to resolve
The following scenarios are invented illustrations, not Curbcut client cases, measured procurement outcomes or examples of a named vendor’s conduct. They show how apparently relevant documents can leave different questions unanswered.
1. Shared infrastructure, different applications
Imagine a vendor sells a course-planning application and a separate scheduling application on shared infrastructure. Some security or organizational answers may apply to both. Their user interfaces, features and accessibility findings may differ.
A shared HECVAT should make that coverage understandable rather than leaving the reader to infer it from the company name. The accessibility report should identify the product it evaluates. If the institution requests a submission for each product, clarify how the shared material relates to each response.
The unresolved question is not simply “Do we have a HECVAT?” It is “Which answers apply to this solution, and where are the exceptions?”
2. An evaluated web application, an unevaluated mobile companion
Suppose an ACR describes the browser application, but the proposed purchase also includes a mobile companion. The existence of the web report does not establish findings about the mobile interface.
Identify whether the report includes that component. If it does not, state the boundary and determine what evidence the buyer needs for it. Do not silently expand a report’s conclusions because the two applications share a brand, subscription or back end.
ITI’s reporting guidance ties an ACR to the tested product or service. The important question is what was evaluated, not whether the marketing names look related.
3. A new release, an old evaluation
Suppose a report describes a release before a redesigned enrollment flow. A newly dated cover page would not, by itself, show whether that changed flow was evaluated.
Explain the relationship between the evaluated release and the offered release. Separate findings that still apply from changes whose accessibility remains unevaluated. Record the evidence and limitations rather than implying that either all prior findings are invalid or all new behavior is covered.
The same distinction applies to a fix: “a change was implemented” and “the changed behavior was retested” are different statements. Report the stage actually supported.
4. The standard product, a different campus configuration
Imagine the evaluated product excludes an optional integration, while the campus intends to use that integration in a required workflow. Or the report covers one user role while the institution needs evidence about another.
Make the inclusion or exclusion visible. Identify whether the relevant interface belongs to the vendor’s product, a separately supplied component or an institution-controlled configuration. Then agree what evidence is needed for the proposed use.
This is not a claim that every possible configuration needs a separate report. It is a reason to describe the evaluated configuration clearly and avoid making unsupported inferences about another one.
HECVAT’s accessibility answers need evidence too
HECVAT 4 is not just an older security form with accessibility left elsewhere. EDUCAUSE’s explanation of its accessibility changes describes a dedicated IT Accessibility tab, screening for whether a solution has an interface, and questions about an ACR, issue management and an accessibility roadmap.
A roadmap describes planned work. A test finding describes observed behavior. A process explains how issues are managed. They can support the same review, but one does not establish the others.
For example, a statement that keyboard issues are tracked does not establish that all relevant workflows work with a keyboard. If an ACR records a barrier, the questionnaire and any roadmap should explain that same known limitation rather than making an unexplained contradictory assertion.
This is where SaaS accessibility work connects to documentation: the evidence must describe the application people will actually use, including the relevant authenticated interfaces.
When the missing piece is an accessibility evaluation
First identify the missing evidence. A generic document generator can help structure a draft; it cannot create observations about behavior that nobody evaluated.
If you need a test-backed report for a particular product, Curbcut’s VPAT / ACR service is the relevant route to discuss accessibility evaluation and report preparation. Keep the product, requested standard or edition, and report scope explicit.
That accessibility work does not complete the vendor’s security or privacy assessment, and it does not decide the institution’s procurement outcome. The objective is accurate, usable evidence for the buyer’s review.
Primary sources
Sources checked on 31 October 2026, Pakistan time. Follow the institution’s current request if its published instructions change.
- EDUCAUSE: HECVAT overview and current downloads
- EDUCAUSE: HECVAT FAQs for corporations
- EDUCAUSE Review: Accessibility in Technology Acquisition with HECVAT 4
- ITI: VPAT and Accessibility Conformance Reports
- University of Arkansas: cybersecurity and accessibility review requirements
- University of Michigan: compliance documentation