Accessibility, VPAT, ACR in questions and answers

Learn about VPAT and ACR in questions and answers.

The VPAT® and ACR play a vital role in promoting accessibility in technology. They provide transparency for consumers and organizations, allowing them to make informed decisions about the products they choose. Additionally, these documents help organizations comply with legal requirements and foster an inclusive environment for all users.

VPATs and ACRs are like guides that show you how a product claims to be accessible. They give you information about how well a product says it works for everyone, including people with disabilities. This helps you understand what features are included, and make a decision based on that information.

However, VPAT and ACR are often confused due to their close relationship, but they serve distinct purposes in the realm of digital accessibility.

Once completed, the VPAT serves as an Accessibility Conformance Report (ACR), which can be shared with potential customers, including government agencies and organizations subject to accessibility regulations, to demonstrate the product’s accessibility features and compliance with government requirements, essentially providing a report that shows whether your product is easy to use for everyone, including people with disabilities.

Key differences

Nature

1. VPAT: a blank template used to assess and document accessibility.
2. ACR: a filled-out VPAT that provides a detailed report on a specific product’s accessibility.

Purpose

1. VPAT: serves as a guideline for manufacturers to evaluate their products against accessibility standards.
2. ACR: acts as a formal declaration of a product’s accessibility status, often used in procurement processes.

Usage

1. VPAT: can be used by any organization to create an ACR.
2. ACR: typically requested by customers or government agencies to understand a product’s accessibility features.

Key components of a VPAT

• Product or service description: basic details about the product, including name, version, and vendor information.
• Accessibility standards: a list of applicable accessibility standards against which the product is evaluated.

• Conformance levels: a description of how the product meets each criterion, typically categorized as Supports, Partially supports, or Does not support.

  Worth mentioning that in the context of a VPAT, Partially supports means that a product or service partially meets the requirements of a specific accessibility standard or criterion, but may not fully meet all the requirements, indicating that some accessibility features or functionalities are present, but others are missing or incomplete.

• Remarks and explanations: additional comments that provide context or clarification regarding the product’s accessibility features.

VPAT editions

The VPAT template includes several editions tailored to different regions and standards:

• VPAT 2.5Rev EU (April 2025). This template is used for documenting accessibility in the European Union, aligning with the EN 301 549 standard and includes EU-specific accessibility criteria.
• VPAT 2.5Rev INT (April 2025). This template is used for international accessibility reporting, covering global accessibility standards, combining elements from WCAG, Section 508, and EU requirements.
• VPAT 2.5Rev 508 (April 2025). This template is used for documenting accessibility in the United States, specifically for compliance with Section 508 of the Rehabilitation Act.
• VPAT 2.5Rev WCAG (April 2025). This template is used for documenting accessibility based on the Web Content Accessibility Guidelines (WCAG), which provide a set of guidelines for making web content more accessible.
• VPAT 2.5Rev Change Tracking (April 2025). This template is used to track changes made to previous VPAT versions, allowing for easier identification of updates and revisions.

Is a VPAT or an ACR required for a mobile app?

To determine whether a Voluntary Product Accessibility Template (VPAT) or an Accessibility Conformance Report (ACR) is required for a mobile app, it is essential to consider the context in which the app will be used.

In general:

1. Government contracts: if the mobile app is intended for use by U.S. government entities, a VPAT or ACR is generally required to demonstrate compliance with accessibility standards, particularly Section 508.
2. Private sector: for mobile apps marketed to private sector companies, while a VPAT or ACR is not strictly required, having one can be beneficial. It demonstrates a commitment to accessibility and can facilitate procurement discussions.
3. Use case specifics: the necessity of a VPAT or ACR can depend on the specific use case of the app. If the app is designed to be accessible under Section 508 or if procurement teams specifically request an ACR, then it is advisable to complete one.
4. General best practices: making an ACR can be a good idea, even if you’re not forced to. It can help sell your app by showing that you care about making it usable for everyone, including people with disabilities.

Here’s a quick overview of who might be involved in completing a VPAT:

1. Product managers: they often oversee the process to ensure that the product’s features are accurately represented.
2. Accessibility specialists: these professionals conduct thorough accessibility audits and evaluations of the product to provide accurate information in the VPAT.
3. Quality assurance teams: they may assist in testing the product to ensure it meets the stated accessibility criteria.
4. Legal and compliance teams: they ensure that the VPAT meets all necessary legal requirements and standards.

Additionally, tools like SiteLint can assist with the process by helping to identify and report on accessibility issues, making it easier to complete the VPAT.

VPAT is typically needed by organizations that:

• Sell products or services to the US federal government, as they are required to comply with Section 508 of the Rehabilitation Act.
• Develop or procure information and communication technology (ICT) products or services that must comply with accessibility standards and guidelines.
• Provide products or services to educational institutions, which are subject to accessibility requirements under the Americans with Disabilities Act (ADA) and Section 504 of the Rehabilitation Act.
• Operate in industries that are subject to accessibility regulations, such as healthcare, finance, and transportation.
• Want to demonstrate their commitment to accessibility and inclusivity.

Specifically, the following types of organizations may need a VPAT:

• Software developers and vendors
• Hardware manufacturers
• Website and mobile app developers
• Educational technology providers
• Healthcare technology providers
• Financial institutions
• Government agencies
• Non-profit organizations
• Companies that provide products or services to government agencies or educational institutions

Where can I find VPAT/ACR documents?

You can typically find VPAT/ACR documents in a few places:

• Vendor’s website: check the website of the product vendor. Look for sections like Accessibility, Compliance, or About Us, usually in the footer’s of the page or application. They often have VPATs/ACRs available for download.
• Product documentation: sometimes, the VPAT/ACR is included in the product’s official documentation or help files.
• Request directly from the vendor: if you can’t find it online, contact the vendor and request a copy of the VPAT/ACR.
• Government websites: if the product is used by a government agency, the VPAT/ACR might be available on the agency’s website or through a government procurement portal.
• Third-party accessibility repositories: some organizations maintain repositories of accessibility information, which might include VPATs/ACRs.

When searching, be specific about the product name and version number to ensure you get the correct VPAT/ACR.

Steps to create an ACR from a VPAT

The process involves several steps:

• Downloading the VPAT template from the ITI website.
• Completing the ACR title page with company information, product details, and evaluation methods used.
• Understanding the three columns of the VPAT tables: Criteria, Conformance Level, and Remarks and Explanations.
• Completing the Success Criteria tables (Levels A, AA, and optionally AAA) if the product falls under certain categories like web content, electronic documents, software, or authoring tools.
• Evaluation methods used to assess accessibility, as included in the ACR and VPAT, typically involve a combination of automated testing tools, manual testing, and expert evaluation to assess conformance with accessibility standards and guidelines, such as WCAG 2.1 and Section 508.
• Review and finalize to ensure that all information is accurate and complete before finalizing the ACR.

One liner summary

• VPAT (Voluntary Product Accessibility Template) and ACR (Accessibility Conformance Report) are essential for promoting accessibility in technology, providing transparency for informed consumer decisions.
• VPAT serves as a guideline for assessing product accessibility, while ACR is the completed document that outlines a product’s accessibility features and compliance.
• Organizations often request VPATs to evaluate products’ accessibility, especially when dealing with government contracts or educational institutions.
• The VPAT is not mandatory but is practically necessary for vendors to sell products, particularly to entities that require accessibility compliance.
• ACRs are generated from completed VPATs and serve as formal declarations of a product’s accessibility status.
• VPATs include key components such as product descriptions, applicable accessibility standards, conformance levels, methods used to assess accessibility, and remarks for clarification.
• Organizations that develop or sell ICT products, especially those working with the federal government, typically need a VPAT to demonstrate compliance with accessibility standards.
• The VPAT and ACR can be utilized for auditing and compliance purposes to identify areas for improvement in accessibility.
• Updates to the ACR and VPAT are necessary whenever significant product changes occur or when new accessibility standards are released.
• Completing a VPAT is recognized as the industry-standard method for documenting digital product accessibility, reinforcing a commitment to inclusivity.

Conclusion

In summary, accessibility is a fundamental aspect that ensures inclusivity for all users. The VPAT and ACR are important documents that help companies show how accessible their products are and find ways to make them better for everyone, including people with disabilities, which can help organizations demonstrate their dedication to making products that everyone can use.

Example ACR from VPAT version 2.4

Here is an Example Accessibility Conformance Report from VPAT version 2.4.