Office of Accessibility Services

VPAT & ACR Evaluations

The Office of Accessibility Services evaluates vendor-produced Accessibility Conformance Reports (ACRs) for UVM units who are considering purchasing external products. Vendors complete a VPAT template; the completed document is referred to as an Accessibility Conformance Report (ACR).

About ACR Evaluation

What's a VPAT, what's an ACR, and why are they important?

Body

A VPAT is a Voluntary Product Accessibility Template (VPAT). It's a standardized form provided by the Information Technology Industry Council so that vendors can evaluate and share how well their products adhere to the accessibility guidelines of the WCAG and Section 508 of the Rehabilitation Act. 

VPATs come in four different types:

  • WCAG edition - For reporting compliance to the W3C Web Content Accessibility Guidelines 2.1 or 2.2.
  • 508 edition - For reporting compliance to the U.S. Revised Section 508 standards
  • EU edition - The European edition used for reporting compliance to the EN 301 549 standard
  • INT edition - The international edition used for reporting compliance to all three standards

When a vendor fills out a VPAT, the resulting document is called an Accessibility Conformance Report (ACR). 

VPATs and the resulting ACRs are important so that organizations like UVM can ensure that the products they buy are accessible to people with disabilities.

When should you ask for an ACR evaluation?

Body

Any UVM department that is considering purchasing a product for use at UVM must go through an IT Contract Review process before making the purchase. An ACR review is part of the IT Contract Review process.

And while some accessibility issues can be worked around, the majority of major accessibility issues cannot. Therefore, it's best to get an ACR review done early in the process, to ensure that the project you want to purchase for use at UVM can actually be purchased and used with equity across UVM. 

Reach out to OAS as early in the purchasing process as possible.

What happens if the review indicates a product is not accessible?

Body

If, at the end of the review, the product turns out to have major or multiple accessibility issues, or there are major issues with the ACR itself, then one of two things can happen:

  1. If there are multiple areas in the ACR where the vendor admits that the product does not meet WCAG 2.1 AA-level guidelines, then OAS will return to the vendor and ask them to share a timeline for when they are planning on remediating the outstanding issues. Depending on the timeline, and how the timeline lines up with the planned use of the product at UVM, that can be sufficient.
  2. Otherwise, if the vendor is not currently planning on remediation but the overwhelming majority of the campus would benefit from access to one particular product that is not 100% accessible, OAS can work with the vendor to create an Equally Effective Alternative Access Plan (EEAAP). An EEAAP details how UVM will provide equal access to the product or for completion of the task despite the product's accessibility issues.

If accessibility risk cannot be reasonably addressed, UVM may be unable to approve the purchase.

How does an evaluation work?

Body

The OAS Web & Digital Accessibility Specialist will read through the vendor's Accessibility Conformance Report (ACR) and grade it based on an industry-standard rubric. 

The OAS rubric looks at:

  • Who did the vendor's accessibility testing
  • What kind of accessibility testing the vendor did for the ACR
  • When the last round of testing was done
  • Which template was used
  • Which aspects of the product were tested
  • How well the accessibility successes and failures have been documented
  • Whether there are any major accessibility failures documented in the ACR.

Each item on the rubric will be assigned one of two states: Pass or Fail. Then at the end of the grading process, the ACR will be assigned a letter grade from A through to F. Letter grades are determined by the percentage of items with a Pass.

A copy of the evaluation can be provided to both the department and the vendor.

Expected timelines for ACR evaluations

Body
The three types of ACR evaluations, how long each one takes, and when OAS uses each
Type of ReviewTime NeededAppropriate For:
Baseline / Default Review10-15 business days (2-3 weeks)

A complete, high-quality ACR/VPAT with: 

  • Clearly defined product/version scope
  • No major ambiguities
  • Minimal need for vendor follow-up
Extended Review(3-5 weeks)
  • The VPAT is vague, outdated, or missing key details
  • There are many "Partially Supports / "Does Not Support" items requiring analysis
  • OAS needs vendor clarification or remediation commitments
  • The product is complex (LMS, platforms, multi-module systems)
Expedited / Priority Review5-7 business days

Only available when: 

  • There is a documented business need or deadline
  • Procurement and the requesting unit engage early
  • Expectations are clear that review depth may be triaged / risk-based

If a review of the ACR indicates multiple areas where accessibility needs are unmet, OAS will reach out to the vendor to ask for a timeline for the remediation of these needs. If the vendor is unable to provide one, OAS may need to draft an Equally Effective Alternate Access Plan (EEAAP) specifying how UVM will provide resources to address the accessibility gaps. This will affect the ultimate timeline for delivery.

Expectations for Vendors

What to know about the ACR evaluation process

Body

The University of Vermont depends on accurate, informative Accessibility Conformance Reports from vendors in order to make plans to support all students, staff, faculty, and visitors with disabilities in the campus community. We appreciate the time and effort it takes vendors to produce these documents and keep them updated.

Each ACR is reviewed by a staff member in the Office of Accessibility Services. We're looking for ways to anticipate what the University may need to provide in order to make it possible for people with disabilities to use all the products that make UVM function. We are not looking to disqualify or reject any products. When UVM wants to use a product but there are items labeled Partially Supports or Does Not Support, the Office of Accessibility Services tries to figure out ways we can provide additional resources or workarounds to make sure all people with disabilities can use the product. We do this by writing a UVM-internal document known as an Equally Effective Alternate Access Plan (EEAAP).

When the Office of Accessibility Services reviews an ACR, we use an industry-standard review template and review procedure. Our process allows us to generate a letter grade based on the rigor of the ACR (in other words, how much confidence we have in its accuracy), as well as reviewing all areas where a product may not support full accessibility. When we finish the report, we provide copies of our report to both the requesting UVM department, and to the vendor.

At this time, we need vendors to complete ACRs using the Information Technology Council's official template. We can only accept one of the templates labeled as version 2.5: 

  • VPAT Rev 2.5 EU
  • VPAT Rev 2.5 INT
  • VPAT Rev 2.5 508
  • VPAT Rev 2.5 WCAG

VPAT Rev 2.5 508 is preferred, as UVM must meet all WCAG and Section 508 requirements.

During the review process, if the Office of Accessibility Services identifies any items labeled Partially Supports or Does Not Support, we may need to contact the vendor with a list of questions for additional information. We do this so that we have all the information we need to determine what UVM can do to bridge any accessibility gaps with additional resources.

 

Evaluating the Rigor of an ACR

Body

The Office of Accessibility Services assigns each ACR a letter grade, based on how many of 16 different criteria the ACR passes. Every ACR starts at 100%; every criteria where an ACR fails to meet our standards decreases that final score.

ACR Scoring Rubric Details

A list of criteria for the ACR letter grade, plus explanations of pass and fail states
CRITERIAPASSFAIL
Version: does the VPAT template being used include the Section 508 criteria?If so, then pass.If not, then fail.
Date: was the VPAT updated in the last 24 months?If so, then pass.If not, then fail.
Template: is the VPAT template being used one of the 2.5 versions?If so, then pass.If not, then fail. Please note: as of 2026, VPAT Template 2.4 is no longer being accepted.
NDA: Are individuals required to sign an NDA before accessing the completed ACR?If not, then pass.If so, then fail. If individuals are required to provide additional information or register with the vendor, then fail. ACRs should be readily available from a vendor's website.
Product Information: Is the product name and version correct?If so, then pass.If either the Product name or version are missing, then fail.
Contact information: does the ACR contain accurate contact information for follow-up?If ACR contains an individual’s name, email, and phone number, and there is an indication that they have some connection to accessibility, then pass.If the ACR contains no contact information, then fail. If the ACR contains generic contact information or contact information for the sales department only, then fail.
Evaluation Party: Was the evaluation conducted by a respected third party? If testing was done by an independent accessibility auditing company or a dedicated accessibility specialist within the company (name and contact details provided), then pass.If testing was done in-house by the vendor by non-accessibility personnel, then fail. If there is no information about who did the testing, then fail.
Evaluation Method: Is the evaluation method specified?If testing includes both automated and manual testing, including assistive technology details, then pass.If testing does not include automated and manual testing with details of assistive technology, then fail.
Conformance Levels: Are conformance levels noted and explained?If conformance levels are noted, and include either WCAG 2.1 or WCAG 2.2 A and AA, as well as Section 508 then pass.

If conformance levels are not noted, or do not include WCAG 2.1 or WCAG 2.2 A and AA, then fail. 

If conformance levels are WCAG 2.0, or are missing Section 508 requirements, then fail.

Notes: Are detailed, accurate notes provided?If notes are detailed and accurate, then pass.If notes are missing or contain concerning statements (e.g., only automated testing was used, an application won’t be used by people with disabilities, or key parts of the product were excluded from the ACR because they weren’t accessible), then fail.
WCAG Tables: Are all WCAG tables included?If WCAG tables for all 13 guidelines are included, then Pass.If tables are incomplete, then fail.
Completed Tables: Are all tables completed in full?If all tables have been completed in full, then Pass.If not all tables have been completed in full, then fail.
Section 508: Are all requirements of Section 508 Chapters 3, 5, and 6 included and completed in full?If all requirements as laid out in Section 508 Chapters 3, 5, and 6 are included and completed in full, then pass.If not all requirements as laid out in Section 508 Chapters 3, 5, and 6 are included, then fail.
Not Applicable Remarks: Any items that have been marked “Not Applicable” have detailed notes, and make sense in the context of the product.If all items that have been marked “Not Applicable” have detailed notes and make sense, then Pass.

If any items that have been marked “Not Applicable” lack notes, then fail.

If any items that have been marked “Not Applicable” have confusing notes or seem to be actually applicable, then more details are needed.

Level Documentation: Are all items marked as Supports / Partially Supports / Not Supported accompanied by detailed notes?

If all items that have been marked as Supports / Partially Supports / Not Supported have detailed notes, then Pass.

These details should contain the following information based on support level: 

  • Supports: How the product supports the criterion (e.g., what accessibility features or techniques are implemented)
  • Partially supports: What accessibility techniques are implemented, and any exemptions (including the location of, and a description for, these exemptions)
  • Does not support: Which aspects of the product do not support the criterion (including a description of these aspects)  

If any items are marked as Supports / Partially Supported / Not Supported and lack detailed notes, then fail.

 

If any items are marked as Supports / Partially Supports / Not Supported and contain notes that indicate the reviewer may not understand the criteria, then More Details Needed.  

Conformance Matching: do any items marked as “Supports” contain notes that lead an evaluator to believe otherwise?If no items are marked as “Supports” but have notes that indicate otherwise, then mark as Pass.If any items are marked as “Supports” but have notes that indicate otherwise, then mark as Fail, and ask for more details.

Evaluating the Details of an ACR

Body

After evaluating the rigor of an ACR, Office of Accessibility Services reviewers go through each individual criteria included in WCAG A-level, WCAG AA-level, and Section 508 Chapters 3, 5, and 6. We look to see that the ACR includes every criteria, and that every criteria has notes explaining how it Supports, Partially Supports, Does Not Support, or is Not Applicable to the product. 

  • If notes are included and make sense, then the reviewer marks the item as a Pass.
  • If there are no notes included, or the notes do not make sense, the reviewer marks the item as a Fail.
  • If an item is missing entirely from the ACR, the reviewer marks the item as a Fail.

At the end of the review, the report sums up how many of the criteria pass, how many fail, and whether any are missing. This information is contained in a narrative section of the review report. 

The section looks like:

"This ACR passes:

  • [number] of 31 WCAG A-level criteria
  • [number] of 24 WCAG AA-level criteria
  • [number] of 9 listed Section 508 Chapter 3 criteria
  • [number] of 28 listed Section 508 Chapter 5 criteria
  • [number] of 5 listed Section 508 Chapter 6 criteria

There is [some / no] information missing for either WCAG or Section 508 criteria, and overall, this is a [letter grade] ACR."

After that, the reviewer writes up any questions that came up during the review, and lists any places where the Office of Accessibility Services will need more information in order to write their EEAAP. They may also assign a potential accessibility risk value to the product. 

Important note:

Reviewers are looking to find ways to approve every product for use at the University of Vermont. We are very aware of the amount of time and effort it takes departments to research and evaluate products for use at the University, and we seek to honor that effort -- at the same time, every product in use at UVM must be available for full use by people with disabilities on the campus.

UVM does not use the ACR review process to automatically reject products. The review helps UVM understand accessibility risk, request remediation information, and determine whether an Equally Effective Alternative Access Plan is needed.

How often does UVM review ACRs?

Body

Because of the rapid pace of software development, UVM reviews the ACRs of products in use at the University every 24 months, or whenever a contract renewal process is initiated.

UVM reviews the ACRs of products for potential use at the University during the purchase process.

Additionally, UVM requests that all vendors provide UVM with any updated ACR they produce, especially when new versions of products are released.

A note about WCAG conformance levels

Body

UVM aligns with current federal requirements for WCAG 2.1 AA and is actively working toward WCAG 2.2 AA as the institutional standard. Vendors are expected to provide WCAG 2.1 AA conformance and should include WCAG 2.2 AA information where available.

Report an Accessibility Barrier

Use our online form to report physical accessibility issues on the UVM campus.