The landscape of educational technology is rapidly evolving, with institutions increasingly relying on digital tools to enhance learning and administrative processes. However, a critical component for ensuring equitable access to these technologies—the Voluntary Product Accessibility Template (VPAT)—is proving to be a point of contention and potential obstruction for many potential buyers. Research emerging from initiatives like the NCADEMI EdTech Accessibility Directory suggests that access to VPATs, crucial documents outlining a product’s compliance with accessibility standards, is not as straightforward as it should be, potentially hindering the procurement of inclusive technologies for individuals with disabilities.
Understanding the Voluntary Product Accessibility Template (VPAT)
At its core, the VPAT is a standardized document designed to help technology vendors communicate the accessibility features of their products and services. Developed by the Information Technology Industry Council (ITI), it translates complex accessibility requirements, such as those mandated by Section 508 of the U.S. Rehabilitation Act and international standards like EN 301 549, into specific, actionable criteria. When a vendor completes the VPAT for a particular 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 purchasers with a clear understanding of a product’s accessibility conformance. In an era where digital inclusion is paramount, especially within educational settings that serve a diverse student population, this transparency is vital. As highlighted in a 2021 ITI blog post, the challenge for many employees with disabilities is the difficulty in determining whether a product will genuinely meet their needs, even when minimum legal standards exist. The VPAT aims to bridge this gap by offering a standardized framework for reporting accessibility information.
The Unexpected Hurdle: Requiring VPAT Requests
A significant finding from ongoing research into the NCADEMI EdTech Accessibility Directory has raised concerns: a substantial number of technology vendors do not make their VPATs readily available on their websites. Instead, interested parties are often required to formally request these documents. This practice has generated surprise and questions within the accessibility community. The fundamental question arises: why would a vendor, in pursuit of sales, create an additional step—a "friction point"—for a potential customer who is already expressing interest and demonstrating a willingness to invest in their product?
To explore potential vendor perspectives behind this practice, an inquiry was posed to several Artificial Intelligence 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 vendor concerns: the need for customized information, the protection of competitive information, and the assurance of providing correct information.
Deconstructing Vendor Concerns
1. Customized Information:
Vendors sometimes express a need to ensure potential customers receive the most relevant accessibility information, particularly when dealing with a broad product portfolio that includes multiple versions or configurations. The argument is that accessibility features might vary, and a generic, publicly posted VPAT might not accurately reflect the specific product a customer is considering.
- Hypothetical Vendor 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."
- Analysis and Response: While the VPAT template does encourage vendors to specify product versions and configurations, this concern can largely be mitigated by vendors themselves. Providing current and properly scoped VPATs, which explicitly detail the version or configuration tested, addresses this. Shifting the onus to the customer to request this information seems an inefficient approach when the VPAT’s design already accommodates such specificity. The responsibility lies with the vendor to ensure their publicly available documentation is accurate and comprehensive for their offerings.
2. Competitive Information:
Another frequently cited reason for restricting public access to VPATs is the concern that the information within them might be considered proprietary or competitively sensitive. Vendors may worry about revealing details about their product development or specific conformance levels to competitors, leading them to require non-disclosure agreements (NDAs) as part of the VPAT request process.
- Hypothetical Vendor Statement: "We can’t make proprietary information available publicly. We even require prospects to sign a non-disclosure agreement (NDA)."
- Analysis and Response: This concern is directly addressed by established procurement policies from leading institutions. For instance, California State University San Marcos (CSUSM) explicitly states on their VPAT Vendor Requirements page that a VPAT "does not contain or disclose proprietary information." They further emphasize that a quality VPAT "faithfully represent[s] a product’s current accessibility conformance, whether accessible or inaccessible." The accessibility conformance of a product is inherently observable through its user interface and functionalities, making the claim of proprietary information in this context questionable. Consequently, institutions like CSUSM rightfully refuse to sign vendor NDAs solely for the purpose of receiving accessibility conformance documentation, asserting that such information should be transparent.
3. Correct Information:
Vendors operating in a global market, serving diverse customers across various countries and sectors (public and private), may feel the need to control the information flow to ensure prospects receive documentation tailored to specific legal frameworks and contractual requirements.
- Hypothetical Vendor 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."
- Analysis and Response: The VPAT framework itself is designed to accommodate this diversity. The ITI offers multiple editions of the VPAT, including those aligned with Section 508 (U.S.), EN 301 549 (European Union), WCAG (Web Content Accessibility Guidelines), and international standards. These variations, along with specific WCAG-version variants, allow vendors to provide documentation relevant to different regulatory environments. Beyond providing the appropriate VPAT edition, vendors can proactively offer additional guidance, context, and support to their prospects, further ensuring that the information provided is both accurate and applicable to the customer’s specific needs and jurisdiction.
Pervasiveness of the Issue: Emerging Data
To gauge the actual prevalence of these access barriers, preliminary research was conducted within the context of the NCADEMI EdTech Accessibility Directory project. With an initial focus on the K-12 education technology sector, a list of over 231 products from 186 unique vendors, identified as having "moderate usage" through AI-driven analysis, was compiled. Google Gemini was then employed to scan the web pages and documentation of these products for any references to VPAT information.
The findings suggest that access to VPATs is indeed a challenge. References to VPAT information were detected for only 35 of the 186 vendors, approximately 19%. Among these 35 vendors, a concerning trend emerged: over one-fifth (22%) required a prospect to actively request their VPAT, rather than making it publicly available. While this research is not exhaustive, it provides compelling evidence that obtaining product VPATs can be a significant hurdle for educational institutions and other potential buyers seeking to make informed, inclusive technology procurement decisions.
Challenges with Publicly Available VPATs
The issue extends beyond mere accessibility of the VPAT document itself. Even among the vendors who do provide public access to their VPATs—demonstrating at least an awareness of accessibility guidelines—a significant portion present documents that fail basic accessibility evaluations. In the early stages of the NCADEMI directory, of the 27 vendors who had provided public VPATs, six submitted documents that were found to be inaccessible.
While the publication of a VPAT does not automatically guarantee a product’s accessibility, it represents a commitment to transparency. The fact that some of these publicly available documents are themselves inaccessible highlights a deeper disconnect in understanding and implementing accessibility principles. Nevertheless, it is important to acknowledge 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: Towards a More Transparent and Accessible Future
The infrastructure for improving VPAT accessibility and usability already exists. Tools like OpenACR, developed by the U.S. General Services Administration (GSA) in collaboration with CivicActions, transform VPAT data into searchable YAML and JSON formats. This allows buyers to compare vendors more effectively, moving beyond the laborious process of sifting through individual VPAT documents.
Leading educational institutions and procurement offices are increasingly demanding more than just a bare VPAT. Best practices now advocate for pairing VPATs with plain-language accessibility statements. Furthermore, for products that only partially meet critical accessibility criteria, a clear remediation roadmap with a defined timeline for improvement is expected. This proactive approach ensures accountability and a commitment to ongoing accessibility enhancements.
The path forward requires a concerted effort from technology vendors to prioritize transparency and accessibility. Making VPATs readily and publicly available, ensuring these documents are themselves accessible, and proactively providing clear, comprehensive information about product conformance will not only benefit potential customers but also foster a more inclusive digital ecosystem for all users. The NCADEMI EdTech Accessibility Directory and similar initiatives serve as vital platforms for shedding light on these issues and driving positive change in the EdTech procurement landscape. Sharing experiences and engaging in open dialogue within the comments section of such articles can further contribute to a collective understanding and push for better practices.
