The process of identifying and vetting products for the NCADEMI EdTech Accessibility Directory has illuminated a significant hurdle: the often-obscured Voluntary Product Accessibility Template (VPAT). For many product vendors, the VPAT, a critical document detailing a product’s compliance with accessibility standards, is not readily available. Instead, it is sequestered behind a request process, a practice that raises questions about vendor transparency and the ease with which educational institutions can procure accessible technology. This hidden-in-plain-sight approach to accessibility information appears to be a systemic issue, potentially hindering the widespread adoption of inclusive digital learning tools.
Understanding the Voluntary Product Accessibility Template (VPAT)
At its core, the VPAT is a standardized document designed to bridge the gap between technical accessibility standards and practical product evaluation. Developed by the Information Technology Industry Council (ITI), it translates complex legal frameworks, such as Section 508 of the Rehabilitation Act in the United States and international standards like EN 301 549, into actionable testing criteria. 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 frequently used interchangeably in industry discourse.
The purpose of the VPAT is to provide potential users and customers with a clear understanding of a product’s accessibility features and limitations. As an ITI blog post from 2021 highlighted, the proliferation of digital tools in the workplace necessitates robust accessibility solutions for employees with disabilities. Despite existing legal mandates for accessible technology in both the U.S. and internationally, discerning whether a product truly meets the diverse needs of all users can be a complex undertaking for purchasers. The VPAT aims to simplify this evaluation process, offering a structured overview of a product’s conformance to various accessibility criteria.
The Gatekeeping of Accessibility Information: Vendor Perspectives
The common practice of requiring potential customers to formally request a VPAT, rather than making it publicly accessible, has prompted an investigation into the underlying vendor motivations. To understand these reasons, a query was posed to several AI agents: "Why might a vendor legitimately need to require a potential client 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 or proprietary information, and the assurance of providing correct, context-specific information.
Customized Information: Ensuring Relevance and Accuracy
One frequently cited vendor concern is the need to provide tailored information, especially for companies with extensive product lines. The hypothetical statement, "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," reflects a genuine logistical challenge. Accessibility features and conformance levels can vary significantly between different versions, modules, or configurations of a single product.
However, the VPAT template itself is designed to accommodate this variability. It explicitly encourages vendors to specify the relevant product version or configuration for which the accessibility claims are made. In instances where accessibility is consistent across multiple iterations, a single, comprehensive VPAT can cover them. The implication here is that while version control is a valid concern, it should not necessitate a request from the customer. Instead, vendors can proactively address this by ensuring their publicly available VPATs are current, accurately scoped, and clearly indicate the specific product version they pertain to. This proactive approach alleviates the burden on potential buyers, allowing them to access relevant information without an additional administrative step.
Competitive Information: Addressing Proprietary Concerns
Another significant reason articulated by vendors for withholding VPATs publicly revolves around the protection of proprietary information. The statement, "We can’t make proprietary information available publicly. We even require prospects to sign a non-disclosure agreement (NDA)," suggests a broader concern about intellectual property. Vendors may view the detailed technical specifications within a VPAT as potentially revealing trade secrets or competitive advantages.
However, this argument is increasingly being challenged by institutions and accessibility advocates. The California State University San Marcos (CSUSM) directly addresses this issue on their VPAT Vendor Requirements page. Their stance is unequivocal: "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." CSUSM further clarifies that the accessibility conformance of any product is, in principle, observable through its interface. Consequently, they assert, "CSUSM will not sign vendor NDAs to receive accessibility conformance documentation." This position underscores the belief that accessibility information, when properly documented in a VPAT, should be transparent and not subject to confidentiality agreements that could impede procurement processes. The accessibility of a product is not proprietary; it is a functional characteristic that should be openly shared.
Correct Information: Navigating Diverse Regulatory Landscapes
Vendors also express a need to ensure that prospective clients receive the "right information" due to the diverse nature of their customer base. The statement, "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," highlights the complexity of adhering to varied international and sectoral accessibility requirements.
The VPAT framework is designed to address this diversity. The ITI provides several editions of the VPAT, including those aligned with Section 508 (U.S.), EN 301 549 (EU), WCAG (Web Content Accessibility Guidelines), and a general International edition. Each edition corresponds to different standards and contractual obligations. Furthermore, within the WCAG editions, there are often variants catering to specific versions of the guidelines. By offering these different editions and providing clear guidance, vendors can effectively communicate their product’s accessibility conformance to a global and multi-sectoral clientele. Supplementing the VPAT with additional explanatory materials or dedicated accessibility support can further enhance clarity and ensure that customers receive the precise information needed for their specific context.
The Pervasiveness of the VPAT Accessibility Challenge
To gauge the extent of this issue, an AI-driven analysis was conducted within the context of the NCADEMI EdTech Accessibility Directory project. While the directory currently features a limited number of published products, a broader survey was undertaken. A list of over 231 K-12 educational technology products, identified as having at least "moderate usage" based on AI research, was compiled. Subsequently, Google Gemini was employed to analyze the web pages and available documentation for these products, specifically searching for references to VPAT information.
The findings were revealing. Out of 186 unique vendors represented across these 231 products, only 35 (approximately 19%) made any reference to VPAT information. This low percentage indicates that a significant majority of vendors do not proactively disclose their accessibility conformance. Even more concerning, among these 35 vendors, more than one in five (22%) required a prospect to request the VPAT, rather than posting it publicly. While this research is not exhaustive, it strongly suggests that access to product VPATs is indeed a pervasive challenge for educational institutions and other potential buyers seeking to ensure the accessibility of the technologies they procure.
Transparency and Accessibility: A Deeper Dive
The analysis also extended to examining the accessibility of the VPAT documents themselves, for those vendors who did provide public access. The results offered a mixed picture. Of the 27 vendors who had made their VPATs publicly available, a notable portion – six of them – provided documents that failed basic accessibility evaluations. This raises a critical point: simply publishing a VPAT does not automatically equate to an accessible product, nor does it guarantee that the VPAT itself is accessible.
Despite these shortcomings, it is important to acknowledge the 21 K-12 EdTech vendors who have demonstrated a commitment to transparency by providing publicly available and accessible VPATs. This proactive approach signifies an awareness of and a willingness to engage with accessibility guidelines, setting a positive example within the industry. Their efforts contribute to a more informed procurement landscape, allowing educators and IT professionals to make better-informed decisions about the technologies they integrate into learning environments.
The Path Forward: Towards Greater Transparency and Accountability
The existing infrastructure and technological solutions offer a clear path toward improving the accessibility of EdTech products and the transparency surrounding their conformance. The OpenACR platform, developed collaboratively by the U.S. General Services Administration (GSA) and CivicActions, is a prime example of such an innovation. OpenACR transforms VPAT data into searchable YAML and JSON formats, enabling buyers to efficiently compare vendors and products without the laborious process of manually sifting through individual VPAT documents.
For educational institutions that are serious about prioritizing accessibility, best practices extend beyond merely obtaining a VPAT. The ideal scenario involves pairing a VPAT with a plain-language accessibility statement that clearly articulates the institution’s commitment and the product’s capabilities. Crucially, for products that only partially meet critical accessibility criteria, a comprehensive remediation roadmap with a defined timeline for addressing these deficiencies is essential. This proactive approach ensures that accessibility is not an afterthought but an integral part of the technology adoption and integration lifecycle.
The ongoing challenge of accessing and evaluating VPATs underscores the need for greater vendor accountability and a more streamlined procurement process. By advocating for publicly available, accessible VPATs, and by supporting platforms like OpenACR, the education sector can collectively push for a future where accessible technology is not a hurdle to overcome, but a standard to be expected. The experiences and insights of educators, IT professionals, and accessibility advocates are vital in shaping this future, and sharing these perspectives can drive meaningful change.
