The landscape of educational technology (EdTech) is constantly evolving, with a growing emphasis on ensuring that digital tools are accessible to all learners, including those with disabilities. A critical component in this endeavor is the Voluntary Product Accessibility Template (VPAT), a document designed to outline a product’s compliance with accessibility standards. However, research and insights from the NCADEMI EdTech Accessibility Directory project reveal a concerning trend: many EdTech vendors are not making their VPATs readily available, creating potential obstacles for institutions seeking to procure inclusive technology. This practice, while seemingly counterintuitive, stems from a complex interplay of vendor concerns related to information customization, competitive intelligence, and accuracy.
Understanding the VPAT and its Purpose
The Voluntary Product Accessibility Template (VPAT) is a standardized document developed by the Information Technology Industry Council (ITI). Its primary function is to translate 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 clear, actionable testing criteria for technology products and services. When a vendor completes a VPAT for their product, the resulting document is known as an Accessibility Conformance Report (ACR). While technically distinct, the terms VPAT and ACR are often used interchangeably in industry discussions.
The genesis of the VPAT can be traced back to the growing need for transparency and accountability in the procurement of accessible technology. A 2021 post by ITI highlighted the persistent challenge faced by individuals with disabilities who rely on technology to participate fully in the workplace and educational settings. Despite the existence of minimum legal standards for accessibility, both domestically and internationally, evaluating whether a product truly meets the diverse needs of employees and students can be a formidable task. The VPAT aims to bridge this gap by providing potential users and customers with crucial insights into a product’s accessibility features and limitations.
The Enigma of Restricted VPAT Access
The NCADEMI EdTech Accessibility Directory project, which aims to identify and catalog accessible EdTech products, has brought the issue of VPAT availability to the forefront. A significant observation from this research is that a majority of product vendors who possess VPATs do not make them publicly accessible. Instead, they require potential customers to formally request these documents. This approach has raised a pertinent question: why would a vendor invest resources in creating a VPAT only to erect a barrier for individuals or institutions actively seeking to engage with their offerings?
To explore this question from the vendor’s perspective, AI agents were consulted to identify legitimate reasons for requiring potential clients to request a product’s VPAT. The synthesized responses pointed to three primary categories of concern: the need for customized information, the protection of competitive intelligence, and the imperative to provide accurate information.
Customized Information: Ensuring Relevance
One frequently cited vendor concern revolves around the sheer volume and diversity of their product offerings. A vendor might state, "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." This concern is rooted in the fact that accessibility features and conformance levels can vary significantly between different versions, configurations, or even specific modules of a software product.
While the VPAT template itself encourages vendors to specify the relevant product version or configuration, the challenge arises when accessibility does not substantially differ across multiple iterations. In such cases, a single VPAT could theoretically cover a range of versions. However, the current practice of requiring requests can be interpreted as a way for vendors to engage directly with a prospect and tailor the information provided, potentially guiding them towards specific, more accessible versions or highlighting the accessibility of the exact configuration they are interested in. The argument is that this direct engagement ensures the customer receives the most pertinent and up-to-date accessibility data for their specific needs.
However, from an accessibility advocate’s standpoint, this approach can be viewed as an unnecessary hurdle. The expectation is that vendors should proactively provide current and properly scoped VPATs, rather than shifting the burden of information retrieval onto potential customers, who are already demonstrating interest by seeking out accessibility data.
Competitive Information: Safeguarding Proprietary Data
Another significant reason cited for restricting public access to VPATs relates to the protection of competitive information. A common vendor sentiment might be, "We can’t make proprietary information available publicly. We even require prospects to sign a non-disclosure agreement (NDA)." This concern suggests that vendors may believe that their VPATs contain sensitive details about their product development processes, internal testing methodologies, or even specific vulnerabilities that could be exploited by competitors.
This perspective, however, is often challenged by accessibility advocates and procurement professionals. The California State University San Marcos, for instance, directly addresses this concern on their VPAT Vendor Requirements page. Their stance is clear: "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." They further elaborate that the accessibility conformance of any product is inherently observable through its interface. Consequently, institutions like CSUSM maintain a policy of not signing vendor NDAs to receive accessibility conformance documentation, emphasizing that such information should be readily available. This highlights a fundamental disagreement on what constitutes proprietary information within a VPAT.
Correct Information: Navigating Diverse Requirements
The third category of vendor concern pertains to ensuring that prospects receive the "correct" information, particularly when dealing with a diverse customer base spanning multiple countries and sectors. A vendor might articulate this as, "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." This concern is amplified by the fact that different regions and industries adhere to varying accessibility standards and legal frameworks.
The VPAT itself offers a solution to this complexity through its multiple editions, which are aligned with different standards: Section 508 (U.S.), EU/EN 301 549 (European Union), WCAG (Web Content Accessibility Guidelines), and an International edition. Furthermore, within the WCAG framework, there are distinct versions (e.g., WCAG 2.0, 2.1, 2.2) and conformance levels (A, AA, AAA). Vendors can leverage these different VPAT editions to provide targeted information that aligns with a specific customer’s contractual requirements or regulatory obligations. Additionally, providing supplemental guidance, such as plain-language accessibility statements or remediation roadmaps, can further clarify accessibility conformance for diverse audiences. The argument here is that by controlling access to the VPAT, vendors can ensure that the prospect receives the most relevant and legally compliant document for their jurisdiction and industry.
The Pervasiveness of the Problem: Supporting Data
To gauge the extent of this issue, the NCADEMI EdTech Accessibility Directory project undertook a focused AI-driven research initiative. Given that the directory currently features a limited number of published products, a broader dataset was compiled. This included a list of over 231 K-12 EdTech products identified through AI-driven research as having at least "moderate usage." The web pages and documentation for these products were then analyzed using Google Gemini to detect references to VPAT information.
The findings were sobering. Out of 186 unique vendors represented across the 231 products, a reference to VPAT information was detected for only 35 vendors, representing approximately 19% of the total. This suggests that a substantial majority of K-12 EdTech products do not readily advertise or provide access to their VPATs.
Even more concerning is the subset of these 35 vendors who did reference VPAT information. Among them, more than 22% required a prospect to request the VPAT rather than posting it publicly. While this AI-driven analysis is not a definitive audit, it strongly indicates that access to product VPATs is a significant challenge within the K-12 EdTech market, potentially hindering informed procurement decisions for accessibility.
Beyond Availability: The Quality of Publicly Available VPATs
The investigation also extended to the quality of VPATs that are made publicly available. While publishing a VPAT is a positive step, demonstrating an awareness of and commitment to accessibility guidelines, it does not automatically guarantee that the product itself is accessible. The NCADEMI project found that among the 27 vendors who had provided public access to their VPATs at the early stages of the directory’s development, a concerning proportion—six vendors—provided VPAT documents that failed an accessibility evaluation. This implies that even when vendors are willing to share their VPATs, the content of these documents may not accurately reflect the product’s true accessibility conformance.
Despite these challenges, it is important to acknowledge the 21 K-12 EdTech vendors who have made publicly available and accessible VPATs. Their proactive approach sets a positive example for the industry and contributes to greater transparency in the EdTech marketplace.
The Path Forward: Towards Greater Transparency and Accessibility
The existing infrastructure and best practices offer a clear roadmap for improving VPAT accessibility and utilization. Tools like OpenACR, developed by the U.S. General Services Administration (GSA) and CivicActions, are designed to transform VPAT data into searchable YAML and JSON formats. This allows buyers to efficiently compare vendors based on their accessibility conformance rather than laboriously sifting through individual VPAT documents.
For educational institutions that are serious about procuring accessible technology, the expectation extends beyond a bare VPAT. Best practices advocate for pairing VPATs with plain-language accessibility statements that are easy for non-technical stakeholders to understand. Furthermore, for products that only partially support critical accessibility criteria, a comprehensive remediation roadmap with a clearly defined timeline for addressing these shortcomings is essential. This demonstrates a vendor’s commitment to continuous improvement and their understanding of the long-term needs of diverse users.
The current situation, where VPATs are often difficult to obtain or of questionable quality, not only impedes the procurement of inclusive technologies but also raises questions about the genuine commitment of some vendors to digital accessibility. As the digital divide continues to be a critical concern, ensuring that all educational tools are designed and documented with accessibility at the forefront is not merely a regulatory requirement but an ethical imperative. The conversation around VPATs underscores the need for greater vendor accountability, improved transparency, and a shared commitment to creating an equitable digital learning environment for all students. The NCADEMI EdTech Accessibility Directory project aims to be a catalyst in this ongoing effort, encouraging vendors to embrace accessibility as a core tenet of their product development and customer engagement strategies.
