What does VPAT® stand for? VPAT® stands for Voluntary Product Accessibility Template. The VPAT is a template used to document how accessible an information and communication technology product (ICT) is as part of a procurement process. VPATs are used to evaluate compliance with accessibility standards for software, mobile applications, e-learning, web sites, documentation, and hardware.
Once the VPAT is complete, it becomes an Accessibility Conformance Report (also called an ACR). The Accessibility Conformance report is used by Federal and state agency contracting officials, buyers at educational institutions, and private sector buyers to assess ICT for accessibility to make a preliminary assessment of a technology product’s conformance based on the reported accessibility standards and guidelines. To effectively market your ICT product to the federal government, state government, or educational institutions, Vendors need to create an accurate VPAT.
The Information Technology Industry Council (ITI) is the industry group that maintains the VPAT. As indicated by its title, a VPAT is voluntarily attestation made available by vendors to purchasers. While a company has no legal mandate to create an ACR, purchasers under federal and many state laws must ask for an ACR. A vendor not wishing to complete an ACR will be required to provide an ACR attestation or choose not to respond to the solicitation.
Accessibility Conformance Reports focus on the standards relevant to specific laws and organization requirements. These standards include:
- Section 508 Amendment of the Rehabilitation Act of 1973
- Web Content Accessibility Guidelines (WCAG) versions 2.0/2.1 – The most commonly recognized accessibility guidelines in the United States.
- EN 201 549 – the European Union’s “Accessibility requirements suitable for public procurement of ICT products and services in Europe.”
The four available template editions are:
- VPAT 2.4 508: Based on revised Section 508 standards and includes WCAG 2.0 plus individual Section 508 chapters
- VPAT 2.4 WCAG: for reporting conformance based on WCAG 2.0 or 2.1.
- VPAT 2.4 EU: for reporting based on EN 301 549 requirements plus WCAG 2.0 or 2.1 or ISO/IEC 40500
- INT: Incorporate all three of the above standards
Which VPAT edition should I use?
Your customers’ requirements will drive the decision on which VPAT edition to use. When preparing a VPAT for your product, here are some points to consider:
Is your primary market the U.S. Federal Government? The VPAT template initially began out of Federal agencies need to evaluate how digital content conforms to Section 508 requirements, so federal contracts often require the 508 edition for creating an ACR. It is interesting to note that the 508 edition is directly tied to the Section 508 Amendment of the Rehabilitation Act of 1973. This piece of legislation currently mandates the use of WCAG 2.0 Level AA and identified chapters.
Does your product include hardware or non-web software? If so, then the Section 508 template is for you. Only the 508 edition has specific chapters for hardware, software, and support documentation and services.
How important is mobile to your customers? Market sectors such as Higher Education have a particular interest in mobile web, and mobile app accessibility since students rely heavily on mobile devices. These customers will likely ask for the VPAT WCAG edition and request conformance reporting to the WCAG 2.1 Level AA guidelines.
Do you sell internationally? Companies that sell internationally may prefer to use the INT edition because it includes all three main international standards in a single template.
As you can see, selecting a VPAT edition can be a challenge. In response to this, many vendors are electing to fill out multiple versions such as the 508 edition, WCAG edition, or just relevant sections of the International edition. Whichever editions you use, be aware each edition comes with its own set of specific instructions.
What does a VPAT look like?
The VPAT document is provided as a Microsoft Word file that can be used as-is or reproduced in other formats. The VPAT® includes two major sections. The first section includes extensive instructions for completing the VPAT, including essential requirements, best practices, posting instructions, etc.
The second section, the VPAT Template, which you will complete and make available to buyers, as the Accessibility Conformance Report (ACR). The ACR is what is made available as documentation of a product’s conformance to accessibility requirements.
The second section of the VPAT Template provides more detailed views of criteria for various platforms. Within the template:
- Column one describes the accessibility criteria.
- Column two describes the conformance level.
- The last column contains any additional remarks and explanations regarding the testing methodology and/or conformance.
Data within the second column includes the status of the ICT with regard to each of the accessibility criteria. The conformance levels are as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can only be used within Level AAA criteria.
The answers need to be clear with respect to what individual criterion the answer applies to. It is possible to either use a summary, selecting the worst case for the criteria, or to have separate answers or even tables for software, support documentation, authoring tools, etc., so long as the methodology used is made clear.
It might seem obvious, but when you created an ACR, make sure you make it accessible if you transform it into another format, such as Adobe PDF.
How do customers use the ACR?
One of the most common misconceptions is how a customer evaluates accessibility during the procurement process. An ACR and other accessibility attestations are used to facilitate conversations within the organization. These conversations center around risk and usage.
In general, the Request for Purchase (RFP) process will follow a general pattern:
- Your ACR is reviewed by an in-house team member or outside consultant with expertise in technology and accessibility.
- If the ACR reports defects or the team discovers defects during the evaluation, the results are shared with the requestor.
- If there are defects, the requestor has the option of utilizing an exception process. The exception process generally includes a Corrective Action Plan or similar vehicle that outlines how the requestor or organization will handle defects. There may be no perfectly accessible product to meet a given business need, however with proper research and/or modifications to configurations and settings, users with disabilities may still be able to utilize it effectively.
- These exception processes usually have several options. For example, the requestor can take ownership of the necessary remediation tasks. The exception process can be the basis for engaging the vendor who will commit to remediate the product or ask for an exception or exemption from the accessibility policy.
- It is important to note that an ACR with defects is not an automatic disqualifier. Having an accurate ACR allows the organization to make an informed decision.
What are some of the limitations of the VPAT?
A VPAT can only attest to products. A VPAT is not appropriate for services such as creating a website or soft deliverables such as a study.
A VPAT is only as credible as the person who completed it. Historically VPATs were completed by salespeople or other non-technical staff. This led to highly inaccurate VPATs. The task was then moved to the development groups who were creating the product. This led to an issue where the teams who created the defects could not subsequently identify them. In short, a VPAT must be completed by someone who understands the WCAG and Section 508 requirement.
Why is an accurate VPAT important?
A product without a VPAT is excluded from U.S. federal government solicitations, many state solicitations, the majority of U.S. institutions of higher education, and private organizations that prioritize accessibility both as part of product development and/ or promote the hiring and inclusion of people with disabilities.
Procuring accessible products for both product development and internal use is the best way for your customers to avoid litigation and promote an inclusive environment.
And finally, an incomplete or inaccurate ACR can put you at contractual risk. Your customers rely on you to self-evaluate and report levels of accessibility compliance on your ACR. Because ACRs are provided as part of an official procurement contract, they represent your formal claim regarding your products and services’ accessibility. Increasingly, organizations are holding vendors responsible for accessibility claims made in their ACR.
How do you complete the VPAT?
Completing a VPAT generally starts with a Section 508 audit by experts familiar with accessibility concepts, guidelines, and testing methodologies. While you can train internal teams to do this, creating an accurate VPAT, the accessibility domain knowledge is something that most organizations don’t have access to internally.
Many organizations initially research Section 508 to bring all VPAT creation activities in-house. After gaining a full understanding of the challenges involved in Section 508 testing, opt to use a knowledgeable consultant to create VPATs for them.
Once the degree of the product’s accessibility is evaluated, the VPAT is completed by a person who understands the rules and guidelines associated with the individual template. If you do not have trained accessibility experts in-house, you may consider hiring a consultant to guide you through the VPAT process.
Using Microassist to create the VPAT?
To create a VPAT, Microassist audits your application to determine compliance with accessibility standards and acquire the data needed to create a VPAT. Your needs will determine the scope and timeline of the audit. This ensures a proper compliance baseline is established with all applicable portions of the Section 508 standards. This audit can take as little as one week and as long as several months for web-based products. Audits require auditors with expertise in manual and automated accessibility testing. The auditing task becomes even more complicated when a product includes custom hardware or desktop software.
Each audit report identifies and prioritizes all accessibility errors within the product or application, defines the method for addressing the issues, and documents its
A caution, a vendor to start the VPAT process after an RFP has been issued will likely not have enough time to complete the template prior to the solicitation due date.
Get more information on having Microassist create a VPAT for your product. Contact our accessibility evaluation services team today and see how we can help.
How often do you update an ACR?
There is no set timeline, but in general, you need to update the ACR every 12 to 16 months, when significant features are released or if the user interface has undergone a substantial change. Your obligation is to provide an accessibility compliance report that your VPAT accurately reflects your product’s current level of compliance.
The VPAT was developed to provide a standard reporting format and make it easier for procurement departments to have conversations regarding your product’s accessibility.
Not having an ACR (completed VPAT) will exclude you from many solicitations in both the public and private sectors. Having an ACR with noted defects does not disqualify you from consideration. An accurate ACR allows the purchaser to compare your product to the competition and pursue a variety of actions, including deciding to purchase your product, undergoing an exception process, or working with you to remediate the product so that it meets requirements.
An inaccurate or misleading ACR represents a significant contract risk.
And finally, you should realize that the VPAT is one component of a robust internal accessibility program that will involve in-depth conversations with your third-party vendors, testing with assistive technology users, testing by accessibility experts, and regular reviews to make sure the information provided is up to date.