The digital landscape is rapidly evolving, and with it, the critical need for accessible technology, particularly within educational institutions. As researchers delve into identifying products and tools for inclusion in initiatives like the NCADEMI EdTech Accessibility Directory, a significant hurdle has emerged: the often-guarded Voluntary Product Accessibility Template (VPAT). For many potential customers seeking to ensure their technology purchases meet stringent accessibility standards, the requirement to actively request a VPAT, rather than finding it readily available, presents a puzzling and often frustrating obstacle. This practice, while perhaps rooted in vendor strategy, creates an unnecessary friction point for organizations actively seeking to invest in inclusive solutions.
Understanding the Voluntary Product Accessibility Template (VPAT)
At its core, the VPAT is a document designed to provide a standardized way for technology vendors to report their product’s conformance with accessibility standards. Developed by the Information Technology Industry Council (ITI), this template translates complex accessibility requirements, such as those mandated by Section 508 of the Rehabilitation Act in the United States and international standards like EN 301 549, into actionable testing criteria. A completed VPAT, often referred to as an Accessibility Conformance Report (ACR), serves as a crucial tool for buyers to assess whether a product will meet the needs of individuals with disabilities.
The genesis of the VPAT can be traced back to the growing recognition of the importance of accessible technology in empowering all individuals, especially within the workplace. A 2021 ITI blog post highlighted the persistent challenge: "Many employees living with disabilities rely on internet-, hardware-, and software-based accessibility solutions to help empower them in their workplaces. Although minimum U.S.-based and international legal standards exist for accessible technologies, determining whether a product will fully meet employees’ needs can be challenging." The VPAT was conceived as a solution to this challenge, offering a structured method for vendors to communicate their product’s accessibility posture.
The Paradox of Inaccessibility: Why Vendors Restrict VPAT Access
The most perplexing aspect of the VPAT landscape, as observed by those involved in directory projects, is the prevalence of vendors who do not make their VPATs publicly accessible. Instead, they mandate that potential customers initiate a request, often involving a formal inquiry or even a sales conversation. This practice raises a fundamental question: why would a vendor invest resources in creating a document designed to facilitate informed purchasing decisions, only to then erect a barrier for interested parties who are, by definition, looking to become paying customers?
To gain insight into this seemingly counterintuitive approach, researchers have explored potential vendor motivations. Synthesized responses from AI agents and industry observations point to three primary categories for this guarded access:
-
Customized Information: Vendors often manage a diverse portfolio of products, with numerous versions, configurations, and feature sets. The argument here is that a one-size-fits-all VPAT might not accurately reflect the specific accessibility conformance of a particular product variant a customer is considering. A vendor might contend that they need to ensure the customer receives the most relevant and accurate information tailored to their specific inquiry.
- Vendor Concern (Hypothetical): "We have an extensive list of products and need to make sure that potential customers have the right information based on which version or configuration of a product they are considering."
- Analysis: While the VPAT template itself encourages vendors to specify product versions and configurations, the burden of providing this clarity should ideally fall on the vendor through readily available documentation. Requiring a customer to request this information shifts an unnecessary administrative load onto the buyer. Best practices dictate that vendors should provide current and properly scoped VPATs proactively, rather than demanding customer initiative for what is essentially a basic product specification.
-
Competitive Information: Another frequently cited reason for restricting VPAT access revolves around concerns about proprietary information. Some vendors may view the detailed information within a VPAT, particularly concerning specific technical implementations that contribute to or detract from accessibility, as sensitive. They might argue that such details could be exploited by competitors. This concern is often amplified by the practice of requiring potential customers to sign Non-Disclosure Agreements (NDAs) before sharing any detailed product information.
- Vendor Concern (Hypothetical): "We can’t make proprietary information available publicly. We even require prospects to sign a non-disclosure agreement (NDA)."
- Analysis: This justification is largely contradicted by established practices and the very nature of VPATs. As highlighted by California State University San Marcos on their VPAT Vendor Requirements page, "A VPAT does not contain or disclose proprietary information; instead, quality VPATs will faithfully represent a product’s current accessibility conformance, whether accessible or inaccessible." The accessibility status of a product’s interface is generally observable to users. The university’s stance that they "will not sign vendor NDAs to receive accessibility conformance documentation" underscores the principle that accessibility information should not be treated as proprietary and subject to restrictive agreements.
-
Correct Information: Vendors operating in a global marketplace with diverse regulatory frameworks may also cite the need to ensure customers receive information aligned with their specific regional or contractual requirements. The VPAT has evolved to accommodate various standards, including Section 508, EN 301 549 (European Union), WCAG (Web Content Accessibility Guidelines), and an international edition. The argument is that by requiring a request, vendors can direct customers to the most appropriate VPAT edition.
- Vendor Concern (Hypothetical): "We sell our products to customers from a range of countries across public and private industries. We need to make sure that our prospects get the right information."
- Analysis: This concern can be effectively addressed by the existence of multiple VPAT editions and the provision of clear guidance. Vendors can proactively offer these different editions and provide accompanying documentation that explains which standard applies to which region or type of contract. This approach facilitates informed decision-making without imposing an unnecessary request process on the customer.
The Pervasive Nature of the Problem: Data from the EdTech Landscape
The anecdotal observation that VPATs are not readily available is supported by emerging data. In the context of the EdTech Accessibility Directory project, which aims to catalog accessible educational technology, researchers have been actively collecting data on product accessibility. An AI-driven analysis of over 231 K-12 products, identified as having at least "moderate usage," revealed a significant lack of publicly accessible VPAT information.
- Supporting Data: Out of 186 unique vendors associated with these products, references to VPAT information were detected on the web pages or in the documentation of only 35 vendors, representing approximately 19% of the total.
- Further Complication: Among these 35 vendors, a substantial portion – over 22% – still required prospects to request their VPAT, rather than posting it publicly.
- Implication: While this AI-driven research is not a definitive audit, it strongly suggests that access to product VPATs is indeed a pervasive challenge within the EdTech sector, potentially hindering procurement processes for institutions prioritizing accessibility.
A Glimmer of Hope: Vendors Who Embrace Transparency
Despite the prevailing challenges, there are vendors who recognize the importance of accessibility and make their VPATs readily available. These organizations, by implicitly demonstrating an awareness of accessibility guidelines, provide a valuable service to their potential customers. However, even among those who publish their VPATs, not all documents meet a high standard of accessibility themselves.
- Observation: Within the early stages of the NCADEMI EdTech Accessibility Directory, which currently features a limited set of products, 27 vendors had provided public access to their VPATs.
- Disappointing Finding: Of these 27 vendors, six provided VPAT documents that failed basic accessibility evaluations, meaning the documents themselves were not usable by individuals who rely on assistive technologies.
- Acknowledgement: This highlights that while publishing a VPAT is a positive step, it does not automatically guarantee that the product is fully accessible, nor does it guarantee the accessibility of the reporting document itself. The researchers acknowledge and commend the 21 K-12 EdTech vendors who have successfully provided publicly-available and accessible VPATs.
Moving Forward: Towards Greater Transparency and Accountability
The infrastructure for a more streamlined and transparent approach to accessibility reporting already exists. Initiatives like OpenACR, developed by the U.S. General Services Administration (GSA) and CivicActions, aim to transform VPAT data into searchable formats like YAML and JSON. This allows buyers to compare vendor offerings more effectively, moving beyond the laborious process of individually scrutinizing lengthy VPAT documents.
For educational institutions and other organizations that are serious about procuring accessible technology, best practices extend beyond simply obtaining a VPAT. A truly robust accessibility procurement process pairs the VPAT with a clear, plain-language accessibility statement. Furthermore, for products that only partially meet critical accessibility criteria, vendors should provide a clear remediation roadmap, complete with realistic timelines for addressing identified gaps.
The current landscape, where vital accessibility information is often hidden behind request forms and NDAs, is a significant impediment to creating a truly inclusive digital environment. By fostering greater transparency, encouraging vendors to proactively publish accessible VPATs, and demanding more than just a perfunctory report, institutions can drive meaningful change and ensure that technology serves all users equitably. The conversation must shift from "if" a product is accessible to "how" accessible it is, and what concrete steps are being taken to achieve full conformance.
