The landscape of educational technology (EdTech) is increasingly reliant on digital tools and platforms, making accessibility a paramount concern for educational institutions. However, a significant hurdle exists for procurement officers and educators seeking to ensure these technologies are usable by all students, including those with disabilities: the often-inaccessible Voluntary Product Accessibility Template (VPAT). Research conducted in relation to the NCADEMI EdTech Accessibility Directory reveals a concerning trend where vendors frequently withhold VPATs, requiring potential customers to actively request them, thereby creating an unnecessary barrier in the procurement process. This practice not only complicates the evaluation of accessible technology but also raises questions about vendor transparency and commitment to inclusivity.
Understanding the Voluntary Product Accessibility Template (VPAT)
The VPAT, developed by the Information Technology Industry Council (ITI), is a standardized document designed to assist buyers in making informed decisions about the accessibility of information and communication technology (ICT) products and services. It translates complex accessibility standards, such as Section 508 of the Rehabilitation Act in the United States and the European standard EN 301 549, into specific, actionable testing criteria. A completed VPAT, often referred to as an Accessibility Conformance Report (ACR), details how a product conforms to these accessibility standards. While the terms VPAT and ACR are frequently used interchangeably, the former refers to the template itself, and the latter to the filled-out report.
The fundamental purpose of the VPAT is to provide transparency regarding a product’s accessibility features and limitations. This is crucial because, as highlighted by an ITI post from 2021, many individuals with disabilities rely on assistive technologies to navigate their work and educational environments. While legal frameworks establish minimum accessibility requirements, discerning whether a product truly meets the diverse needs of users can be a complex undertaking. The VPAT serves as a critical tool for potential users and customers to gain insight into a product’s accessibility conformance before making a purchase.
The Obstacle of Inaccessible VPATs: A Vendor Perspective Explored
The observation that most product vendors in the NCADEMI EdTech Accessibility Directory do not make their VPATs publicly available, instead requiring a customer request, is a point of significant friction. This practice prompts a critical question: why would a vendor create a document intended to demonstrate accessibility and then deliberately place it behind a barrier for interested parties? To understand potential vendor rationales, AI agents were consulted regarding the reasons a vendor might legitimately require a potential client to request a product’s VPAT. The synthesized responses pointed to three primary categories: customized information, competitive concerns, and ensuring the delivery of correct information.
Customized Information: The Nuance of Product Configurations
One stated concern from vendors is the need to provide the "right information" for a vast array of products, particularly when different versions or configurations of a single product exist. The argument is that accessibility features might vary across these variations, necessitating tailored VPATs.
However, the VPAT template itself is designed to accommodate this. It encourages vendors to specify the relevant product version or configuration. In instances where accessibility is consistent across multiple versions, a single, well-scoped VPAT can effectively cover these. Shifting the burden of requesting the correct VPAT to the customer, rather than proactively providing appropriately scoped and current documentation, appears to be an inefficient approach. The onus should be on the vendor to offer clear, version-specific accessibility information without requiring a customer to navigate this process.
Competitive Information: The Proprietary Data Dilemma
Another frequently cited reason for withholding VPATs is the perceived proprietary nature of the information contained within them, leading some vendors to request non-disclosure agreements (NDAs) from prospects. The argument suggests that the detailed breakdown of a product’s accessibility conformance could reveal insights into its development or testing processes that vendors wish to protect.
This concern is directly countered by established best practices and institutional policies. The California State University San Marcos, for example, explicitly states on its VPAT Vendor Requirements page that a VPAT "does not contain or disclose proprietary information." Their policy emphasizes that a quality VPAT accurately reflects a product’s current accessibility conformance, regardless of whether it is accessible or inaccessible. Furthermore, they assert that this information is generally discoverable by anyone interacting with the product’s interface. Consequently, CSUSM will not sign vendor NDAs to obtain accessibility conformance documentation, underscoring the view that accessibility information should be transparent.
Correct Information: Navigating Diverse Regulatory Landscapes
Vendors also express a need to ensure that prospects receive the "right information" due to the diverse international customer base and the varying regulatory environments they serve. This often involves different accessibility standards, such as Section 508 in the US, EN 301 549 in Europe, and Web Content Accessibility Guidelines (WCAG) internationally.
The VPAT framework addresses this through its various editions. Vendors can provide specific VPATs aligned with different standards – Section 508, EU/EN 301 549, WCAG, and an International edition, often with further variants within the WCAG editions. This allows for targeted information delivery. Beyond providing the appropriate VPAT edition, vendors can proactively offer additional guidance and context to their prospects, thereby ensuring clarity and compliance with diverse contractual and legal requirements.
Quantifying the Accessibility Gap: Data-Driven Insights
To ascertain the prevalence of this issue, research was conducted to gather data on VPAT availability within the K-12 EdTech sector. The NCADEMI EdTech Accessibility Directory, in its early stages with approximately 60 published products, served as a starting point. An expanded dataset was generated, identifying over 231 K-12 products with at least "moderate usage," based on AI-driven research. Google Gemini was employed to analyze the web pages and documentation of these products for any references to VPAT information.
The analysis revealed that out of 186 unique vendors associated with these 231 products, only 35 (approximately 19%) provided a reference to VPAT information. This indicates a significant portion of EdTech products do not readily disclose their accessibility status. Furthermore, among these 35 vendors, more than one in five (22%) required a prospect to request their VPAT rather than publishing it publicly. While this research is not a comprehensive assessment, it strongly suggests that accessing product VPATs is indeed a pervasive challenge for educational institutions.
The State of Publicly Available VPATs: A Mixed Bag
The vendors who do provide publicly accessible VPATs represent a subset of those aware of accessibility guidelines. However, even this group presents a mixed picture. Of the 27 vendors who have thus far made their VPATs publicly available, a concerning six (approximately 22%) provided VPAT documents that failed an automated accessibility evaluation.
This finding is significant because while publishing a VPAT does not inherently guarantee a product’s accessibility, it signifies an acknowledgment of the importance of transparency and the effort to communicate conformance. The fact that a portion of these publicly shared documents are themselves inaccessible raises further questions about the quality and rigor of accessibility self-reporting within the EdTech industry. Despite this, it is important to acknowledge the 21 K-12 EdTech vendors who have successfully provided publicly available, accessible VPATs, demonstrating a commitment to inclusive procurement practices.
Charting a Path Forward: Towards Greater Transparency and Accessibility
The infrastructure and best practices for improving VPAT accessibility and usability already exist. Initiatives 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 accessibility conformance rather than spending extensive time manually sifting through individual VPAT documents.
For educational institutions serious about procuring accessible technology, the standard is evolving beyond a bare VPAT. Best practices now advocate for pairing VPATs with plain-language accessibility statements that clearly articulate the product’s accessibility features and limitations in an easy-to-understand format. Furthermore, for products that only partially support critical accessibility criteria, a detailed remediation roadmap with a defined timeline for addressing these shortcomings is increasingly expected.
The implications of these findings are far-reaching. Without readily available and accessible VPATs, educational institutions are hampered in their ability to fulfill their legal and ethical obligations to provide equitable access to education for all students. This lack of transparency can lead to the procurement of inaccessible technologies, creating significant barriers for students with disabilities, increasing the burden on educators to find workarounds, and ultimately undermining the goals of inclusive education. Moving forward, a concerted effort from vendors to embrace transparency and proactively share accessible VPATs, coupled with institutional demand for comprehensive accessibility documentation, will be crucial in ensuring that educational technology truly serves every learner.
