The journey to compile the NCADEMI EdTech Accessibility Directory has illuminated a significant bottleneck in the procurement of accessible educational technology: the Voluntary Product Accessibility Template (VPAT). As researchers meticulously identify and evaluate products, the prevalence of VPATs, or rather the lack thereof, has become a central concern. A striking observation is that the vast majority of vendors offering products within the directory either do not make their VPATs publicly available or require potential customers to initiate a specific request. This practice raises a critical question: why would a vendor invest resources in creating a document that is intended to facilitate a sale, only to introduce an unnecessary hurdle for interested parties?
Understanding the Voluntary Product Accessibility Template (VPAT)
At its core, the Voluntary Product Accessibility Template (VPAT) is a standardized document developed by the Information Technology Industry Council (ITI). Its purpose is to translate complex accessibility requirements and legal frameworks, such as Section 508 of the Rehabilitation Act in the United States and broader international standards like EN 301 549, into actionable criteria for evaluating the accessibility of technology products and services. A completed VPAT, often referred to as an Accessibility Conformance Report (ACR), serves as a declaration by the vendor regarding their product’s compliance with these established standards. While the terms VPAT and ACR are frequently used interchangeably, the VPAT is the template, and the ACR is the completed report based on that template.
The need for such a template arose from the growing imperative to ensure that technology is usable by individuals with disabilities. As highlighted in a 2021 ITI blog post, the challenge for organizations, particularly those in the federal sector, lies in determining whether a product truly meets the diverse needs of employees with disabilities. While minimum legal standards exist, discerning the practical implications of these standards for day-to-day usability can be a complex undertaking. The VPAT aims to bridge this gap by providing a structured format for vendors to detail their product’s accessibility features and any known limitations.
The Role and Significance of VPATs for Consumers
For potential users and customers, a VPAT offers crucial insights into a product’s accessibility. It allows them to assess whether a particular technology aligns with their organization’s accessibility policies, legal obligations, and, most importantly, the needs of their end-users. In educational settings, this is particularly vital, as students and educators with disabilities rely on accessible tools to fully participate in learning and teaching. A well-maintained VPAT can inform purchasing decisions, prevent the adoption of inaccessible technologies, and foster a more inclusive digital learning environment.
Vendor Perspectives: Why the Request Barrier?
The common practice of requiring customers to request a VPAT, rather than making it readily accessible, prompts an exploration of vendor motivations. To gain a clearer understanding, a synthesized analysis of responses from AI agents was conducted, identifying three primary categories for this vendor behavior: the need for customized information, concerns over competitive information, and the desire to provide correct information.
Customized Information: Ensuring Product-Specific Accuracy
One frequently cited reason is the sheer volume and complexity of product portfolios. Vendors often offer multiple versions or configurations of their software or hardware. The concern, from a vendor’s perspective, is ensuring that a potential customer receives the most accurate VPAT pertaining to the specific product and its version or configuration that they are considering. The VPAT template itself includes fields designed to specify the product version or configuration. The argument is that without this specificity, a generalized VPAT might be misleading.
However, this concern can be effectively addressed through proactive vendor practices. If accessibility conformance remains largely consistent across various versions or configurations, a single, well-scoped VPAT can encompass these. The burden of ensuring accuracy should ideally lie with the vendor in providing up-to-date and appropriately scoped VPATs, rather than placing the onus on the customer to navigate this process. Shifting this responsibility can inadvertently create a barrier, particularly for smaller institutions or those with limited procurement resources.
Competitive Information: Safeguarding Proprietary Data
Another significant concern voiced by vendors revolves around the protection of proprietary information. Some vendors express apprehension about making their VPATs public, citing that these documents might inadvertently reveal sensitive aspects of their product development or internal processes. This concern is often linked to the practice of requiring potential clients to sign Non-Disclosure Agreements (NDAs) before any detailed product information, including accessibility data, is shared.
This argument, however, faces robust counterpoints. As articulated by California State University San Marcos on their VPAT Vendor Requirements page, a well-constructed VPAT is not intended to disclose proprietary information. Instead, it should accurately reflect the product’s current accessibility conformance, regardless of whether that conformance meets or falls short of established standards. The accessibility status of a product is, in many ways, observable through its user interface and functionality. Consequently, institutions like CSUSM have adopted the stance that they will not sign vendor NDAs solely to receive accessibility conformance documentation, emphasizing that such information should be transparent. This position underscores a growing expectation that accessibility data, while detailing product specifications, does not inherently constitute trade secrets.
Correct Information: Addressing Diverse Regulatory Landscapes
Vendors operating in a global market often sell their products to a diverse clientele across various countries and sectors, each with potentially different regulatory requirements and accessibility standards. The concern here is ensuring that prospects receive the VPAT edition that is most relevant to their specific legal and contractual obligations. For instance, a customer in the United States might require a VPAT aligned with Section 508, while a European customer would likely need one adhering to the EN 301 549 standard.
The VPAT framework itself offers a solution to this challenge through its multiple editions. The standard VPAT typically includes versions tailored to specific standards, such as Section 508 (US federal), EN 301 549 (European Union), Web Content Accessibility Guidelines (WCAG), and an International edition. By providing the appropriate edition, vendors can cater to the diverse needs of their global customer base. Furthermore, offering supplementary guidance or documentation alongside the VPAT can further assist prospects in understanding the accessibility conformance of a product within their specific context.
The Pervasiveness of the VPAT Access Challenge: Data Insights
To gauge the extent of this VPAT access issue, the NCADEMI EdTech Accessibility Directory project initiated a focused research effort. While the directory itself currently lists approximately 60 published products, a broader survey was conducted. AI-driven research identified over 231 K-12 educational technology products with at least "moderate usage," based on an analysis of their online presence and documentation.
The findings were revealing. Out of 186 unique vendors associated with these products, only 35 (approximately 19%) referenced VPAT information on their web pages or in their documentation. This suggests that a significant majority of EdTech vendors do not proactively provide information about their products’ accessibility conformance.
Furthermore, among those 35 vendors who did mention VPATs, more than one in five (22%) stipulated that prospects must request the VPAT. This indicates that even when accessibility documentation exists, it is often not readily available, reinforcing the notion that access to crucial accessibility information can be a substantial challenge for educational institutions and other potential buyers.
Vendors Offering Public VPATs: A Glimpse of Progress and Pitfalls
Despite the challenges, some vendors are making their VPATs publicly accessible, signaling an awareness of and commitment to accessibility guidelines. As of the latest data from the NCADEMI project, 27 vendors have provided public access to their VPATs. This proactive approach is commendable, as it demonstrates transparency and a willingness to facilitate informed purchasing decisions.
However, the data also revealed a concerning trend among these publicly available documents. Out of the 27 vendors, a notable six (approximately 22%) provided VPAT documents that failed an independent accessibility evaluation. This highlights a critical distinction: while publishing a VPAT is a positive step towards transparency, it does not automatically guarantee that the product itself is accessible. The quality and accuracy of the VPAT are paramount. Nevertheless, it is important to acknowledge and celebrate the 21 K-12 EdTech vendors who have successfully provided both publicly available and accessible VPATs, setting a positive example for the industry.
Moving Forward: Enhancing Accessibility Documentation and Procurement
The infrastructure and best practices for improving accessibility documentation and procurement are already in place. Tools like OpenACR, developed by the U.S. General Services Administration (GSA) in collaboration with CivicActions, are designed to transform VPAT data into searchable formats, such as YAML and JSON. This technology allows buyers to efficiently compare vendor accessibility claims rather than laboriously sifting through individual VPAT documents.
For educational institutions and other organizations committed to procuring truly accessible technology, best practices extend beyond simply obtaining a VPAT. A comprehensive approach typically involves pairing the VPAT with a plain-language accessibility statement that clearly articulates the vendor’s commitment and understanding of accessibility. Furthermore, in instances where a product only partially meets critical accessibility criteria, a detailed remediation roadmap, complete with a realistic timeline for addressing the identified gaps, is essential.
The current landscape suggests a significant opportunity for improvement. Vendors who proactively provide accessible and accurate VPATs, along with supplementary accessibility statements and remediation plans, will not only meet regulatory expectations but also build trust and demonstrate a genuine commitment to inclusive technology. This will ultimately benefit not only their customers but also the diverse populations who rely on accessible digital tools to participate fully in education and society. The path forward requires a collective effort from vendors, procurement officers, and accessibility advocates to ensure that accessibility is not an afterthought but a foundational element of technology development and acquisition.
