What Is a VPAT, and Is a VPAT Enough for K-12 Accessibility Compliance?
As school districts prepare for new ADA Title II accessibility requirements, one document is going to become increasingly important in the K-12 technology review process: the VPAT.
A VPAT gives districts a standardized way to understand how an educational technology product conforms to recognized accessibility standards. For districts managing hundreds or even thousands of applications, this information can play an important role in determining whether technology is appropriate for use by students, staff, parents, and the community.
The challenge isn't whether districts should use VPATs. They should.
The challenge is finding them, understanding what they say, and turning that information into something useful for the people responsible for approving technology.
That is especially important as districts prepare for WCAG 2.1 Level AA requirements under Title II of the Americans with Disabilities Act.
What Is a VPAT?
VPAT stands for Voluntary Product Accessibility Template. It was developed by the Information Technology Industry Council (ITI) to provide a standardized way for technology providers to document how their products conform to accessibility standards.
There is a technical distinction worth understanding. The VPAT is actually the template. When a vendor completes the template for a particular product, the resulting document is called an Accessibility Conformance Report, or ACR. In everyday use, however, most people simply refer to the completed document as a VPAT.
For school districts, the important part is the information contained in that report.
A completed VPAT can provide detailed information about how an educational technology product performs against specific accessibility criteria. Depending on the version used, the report can address standards such as the Web Content Accessibility Guidelines (WCAG) and Section 508.
For K-12 school districts preparing for the new ADA Title II requirements, WCAG 2.1 Level AA is particularly important because that is the technical accessibility standard established by the Department of Justice for covered web content and mobile applications.
Why Are VPATs Important for K-12 Schools?
For years, school districts have asked technology vendors questions about student data privacy and security before approving their products.
Accessibility now needs to become part of that same technology review process.
A VPAT gives districts a structured way to obtain accessibility information directly from the technology provider. Rather than relying on a general statement that a product is "accessible," the report can provide information about specific accessibility criteria and explain how the product supports them.
This can include important areas such as keyboard navigation, screen reader compatibility, text alternatives, color contrast, forms, page structure, navigation, and other functionality that can affect whether someone with a disability can use the technology.
For districts, that information is valuable.
The VPAT provides a common framework for asking vendors the same accessibility questions across many different products.
What Should Districts Look for in a VPAT?
A VPAT contains much more information than a simple yes-or-no accessibility statement.
For individual accessibility criteria, the vendor reports how its product conforms to the applicable standard. Depending on the VPAT version, districts may see terms such as Supports, Partially Supports, Does Not Support, and Not Applicable, along with remarks explaining the vendor's response.
Those details are where much of the value of a VPAT is found.
Two vendors may both provide VPATs, but the information contained in those documents may be very different. One product may support most applicable WCAG 2.1 Level AA criteria, while another may identify areas where accessibility is still being improved.
That doesn't make the VPAT less useful.
It makes the VPAT more useful.
The purpose is to give the district visibility into the accessibility of the technology so it can make an informed decision.
Rather than asking only, "Does this vendor have a VPAT?", districts should also be asking, "What does the VPAT tell us?"
How Current Is the VPAT?
The date of the VPAT is also important.
Educational technology changes quickly. Vendors introduce new interfaces, features, mobile applications, dashboards, AI functionality, and other changes throughout the life of a product.
A VPAT should therefore be reviewed in the context of the product version it describes and when the evaluation was performed.
If a vendor has recently updated its accessibility documentation, that information may provide a better picture of the product students will actually use today.
If the available VPAT is several years old, the district may want to ask whether a newer Accessibility Conformance Report is available.
This doesn't mean an older VPAT has no value. It means the age of the document is another piece of information districts should consider as part of the review.
How Was the Product Evaluated?
Districts can also look at the evaluation methods described in the Accessibility Conformance Report.
Depending on the vendor and product, accessibility evaluation may include automated testing, manual testing, assistive technology testing, or a combination of approaches.
The report may also provide information about the product version evaluated and other details that help the district understand the basis for the vendor's accessibility statements.
Again, the goal isn't to turn district technology staff into accessibility auditors.
It is to give them enough information to understand the vendor's accessibility documentation and make an informed technology decision.
Why VPATs Matter More Under the New ADA Title II Requirements
The importance of this information is increasing.
In 2024, the U.S. Department of Justice adopted a final rule establishing specific accessibility requirements for web content and mobile applications provided by state and local governments, including public schools.
The rule establishes WCAG 2.1 Level AA as the technical accessibility standard.
Following an extension announced by the Department of Justice in 2026, public entities with populations of 50,000 or more generally have until April 26, 2027 to comply, while smaller public entities generally have until April 26, 2028. School districts should review DOJ guidance to determine which deadline applies to them.
And this is about much more than the district website.
The requirements can apply to web content and mobile applications a public entity provides or makes available through contractual, licensing, or other arrangements.
For K-12 schools, that makes third-party educational technology an important part of the accessibility conversation.
Learning management systems, curriculum platforms, assessment tools, classroom applications, digital textbooks, communication platforms, instructional websites, and other technology may all need to be considered as districts prepare.
VPATs give districts an established way to begin collecting the accessibility information they need from those technology providers.
Is a VPAT Enough for K-12 Accessibility Compliance?
A VPAT is an important source of information for evaluating EdTech accessibility, but districts still need a process for reviewing and using the information it provides.
Think about student data privacy.
Obtaining a vendor's privacy policy is important, but the document becomes much more useful when someone reviews it, identifies the important provisions, and presents the findings in a way that helps the district make a decision.
The same concept applies to a VPAT.
A district needs to know whether a VPAT is available, which accessibility standard it addresses, when it was completed, and what the vendor reports about its conformance with the applicable accessibility criteria.
Then the district needs to determine what that information means for its technology approval process.
The VPAT provides the information.
The accessibility review makes that information usable.
The Bigger Challenge Is Scale
This is where accessibility review can become difficult for school districts.
Reviewing one VPAT is manageable.
Reviewing accessibility information for hundreds or thousands of educational technology products is something entirely different.
District staff may need to locate the vendor's accessibility documentation, determine whether a VPAT is available, identify the applicable WCAG standard, review individual criteria, identify areas of partial or non-support, document the findings, and then make that information available to the people approving technology.
And the process doesn't stop with new applications.
Districts also need visibility into the technology already being used throughout their schools.
For most technology departments, the problem isn't understanding that accessibility matters.
The problem is finding enough time to do the work.
How EdPrivacy Helps Districts Review VPATs
This is why we added Accessibility Review to EdPrivacy.
EdPrivacy helps districts take the accessibility information vendors already provide and make it easier to use as part of the technology vetting process.
When a VPAT or Accessibility Conformance Report is available for an application, EdPrivacy can help districts identify and organize that information and bring important accessibility findings into the same review process they already use for student data privacy and AI risk.
Instead of requiring district staff to locate a VPAT and work through a lengthy technical document every time a teacher requests an application, EdPrivacy helps make the relevant information easier to understand and use.
That is particularly important when districts are reviewing large numbers of applications.
The goal isn't to replace the vendor's VPAT or make an independent accessibility certification.
The goal is to help districts get more value from the VPAT by turning a technical accessibility document into practical information that can support a technology decision.
With EdPrivacy, accessibility can become part of the same technology vetting workflow districts use to evaluate privacy and AI risk.
One application. One review process. Better information for the district.
Make VPAT Review Part of Your Technology Approval Process
As the new ADA Title II deadlines approach, school districts should begin incorporating accessibility into the way they evaluate educational technology.
Asking vendors for a VPAT is an important step.
The next step is making sure the information contained in that VPAT actually reaches the people who need it.
Districts need to know which applications have accessibility documentation, what that documentation says, where potential accessibility concerns have been identified, and whether additional information from the vendor may be needed.
For a district managing hundreds or thousands of applications, that requires more than a folder full of VPATs.
It requires a process.
VPATs provide the accessibility information. EdPrivacy helps districts put that information to work.
