Understanding VPAT (Voluntary Product Accessibility Template)

Digital accessibility is now a key priority for organizations of all sizes. From government agencies to startups, businesses are expected to ensure their digital products are usable by everyone, including people with disabilities. That’s where the VPAT comes in.

This article covers the essentials of VPAT, including what it is, why it matters, and how to create one effectively.

Understanding VPAT

A VPAT (Voluntary Product Accessibility Template) is a standardized document that helps vendors outline how their digital products or services comply with recognized accessibility standards, such as WCAG (Web Content Accessibility Guidelines), Section 508 (in the U.S.), and EN 301 549 (in the EU).

When completed, the VPAT becomes an Accessibility Conformance Report (ACR), detailing which accessibility criteria the product meets, partially meets, or does not meet, along with clear explanations for each assessment.

This transparency helps businesses assess whether a product is suitable for users with disabilities and ensures compliance with accessibility requirements.

Why is a VPAT Important?

A VPAT is crucial for ensuring digital accessibility and compliance with established standards. It is a key tool for transparency, helping organizations, especially in regulated sectors like government and healthcare, assess whether a product or service meets necessary accessibility requirements.

By completing a VPAT, companies demonstrate their commitment to inclusive design, responsible product development, and equal access for users with disabilities.

In the U.S., VPATs are often mandatory for federal contracts, making them essential for vendors seeking to do business with government agencies.

Globally, they are becoming an industry standard for companies that prioritize accessibility. They help prevent the exclusion of users with disabilities and ensure a broader, more inclusive user base.

Why Companies Use VPATs

Companies use VPATs for multiple reasons:

• To Win Contracts: Many enterprises and government entities require a VPAT as part of the procurement process.
• To Demonstrate Compliance: VPATs show your product’s alignment with laws like Section 508 or the ADA.
• To Stand Out in the Market: A well-documented VPAT can be a competitive differentiator in accessibility-conscious markets.
• To Drive Internal Improvements: Completing a VPAT often reveals accessibility gaps, prompting necessary fixes and product improvements.

What Does a VPAT Include?

A VPAT typically includes the following sections to provide a comprehensive assessment of a product’s accessibility:

• Product Information: Details about the product or service being evaluated, including its name, version, and a brief description of its features.
• Applicable Standards: Lists the accessibility standards the product is being evaluated against, such as WCAG, Section 508, or EN 301 549.
• Evaluation Criteria and Results: A breakdown of the product’s compliance with specific accessibility criteria, indicating whether the product fully, partially, or does not meet each criterion.
• Test Methods and Notes: Explains the methods used for testing the product’s accessibility and any specific considerations or notes related to the evaluation.
• Summary Table: A concise table summarizing the product’s conformance to each accessibility standard, providing a clear overview of its accessibility status.

How to Create a VPAT

Creating a VPAT isn’t just about filling in a form; it requires proper accessibility testing, documentation, and a solid understanding of accessibility standards.

1. Gather Relevant Product and Testing Information

The first step in creating a VPAT is to gather all necessary product information and accessibility testing results. This forms the foundation for your VPAT and ensures that the data you provide is accurate and comprehensive.

• Product Details: Document the product’s name, version, platform, and any unique features.
• Accessibility Testing Results: Collect results of tests, highlighting identified issues and their severity.
• Test Methods and Tools: Document the testing methods used, such as automated scans, manual testing, and usability evaluations with assistive technologies.
• Issues and Resolutions: Note any accessibility issues found and categorize them based on severity and planned resolutions.

BrowserStack Accessibility testing platform is an excellent tool for this step. It allows you to test your product on real devices and browsers, helping to identify accessibility issues early in the process. With tools like automated compliance checks and screen reader integration, you can efficiently gather necessary data for your VPAT.

Talk to an Expert

2. Understand the Required Sections and Terminology

Before filling out a VPAT, it’s essential to familiarize yourself with its structure and key terminology to ensure accurate and consistent documentation.

• Sections in the VPAT: A VPAT typically includes sections such as product information, applicable accessibility standards, and test methods. Each section requires precise and detailed input, so understanding these categories is crucial for completing the template.
• Key Terminology:
• • Conformance Level: The degree to which your product meets accessibility standards, often categorized as “Fully Meets,” “Partially Meets,” or “Does Not Meet.”
  • Explanatory Notes: Provide detailed explanations or clarifications for each criterion to justify the product’s accessibility status.
  • Accessibility Standards: Standards like WCAG, Section 508, or EN 301 549 against which the product is being evaluated.

3. Check and Validate Your Product Against Accessibility Standards

Once you’ve gathered the necessary product information, the next step is to evaluate how well your product aligns with recognized accessibility standards.

• Choose the Right Standards: Identify the standards applicable to your audience or market. Common ones include:
  • WCAG (Web Content Accessibility Guidelines) – widely used globally
  • Section 508 – mandatory for U.S. federal agencies
  • EN 301 549 – standard for accessibility in the EU
• Run Comprehensive Tests: Use a mix of automated and manual testing to validate compliance. BrowserStack Accessibility helps streamline this step by checking for WCAG violations across real devices and browsers.
• Document the Findings: Record which criteria are fully supported, partially supported, or not supported at all. Add brief notes explaining why certain standards may not be met.

Tip: Use BrowserStack’s accessibility checklist to align with key compliance requirements and ensure thorough coverage.

4. Complete the Summary Table Thoughtfully

The summary table is one of the most visible parts of your VPAT. It offers a quick overview of how well your product supports each accessibility criterion.

• Be Objective and Consistent: Use standardized terms like “Supports,” “Partially Supports,” or “Does Not Support” based on your testing results. Avoid vague or overly optimistic statements.
• Include Supporting Notes: For each entry, provide a concise explanation. Clarify why a criterion is or isn’t met and reference test results where applicable.
• Avoid Overstatements: Don’t mark a feature as “Supports” unless it fully meets the standard across all relevant platforms and use cases. Transparency builds trust with buyers and regulators.
• Think from the User’s Perspective: Highlight practical accessibility features that impact real users, such as screen reader compatibility or keyboard navigation.

5. Provide Clear Explanations for Each Accessibility Criteria

Each accessibility criterion in your VPAT should include a brief but meaningful explanation that supports your conformance claim.

• Be Specific and Transparent: Explain how your product meets, partially meets, or does not meet each requirement. Mention relevant features, user flows, or behaviors observed during testing.
• Reference Testing Evidence: Use data from your accessibility testing (manual or automated) to justify your response. For example, if a form supports keyboard navigation but has inconsistent focus states, explain that clearly.
• Avoid Generic Language: Statements like “supports accessibility” are too vague. Instead, describe what was tested, how it performs, and any limitations.
• Clarify Partial Support: When marking “Partially Supports,” specify what works, what doesn’t, and in which environments or scenarios the issue appears.

6. Plan to Fix Accessibility Issues Identified

A VPAT is not just a compliance document; it’s also a roadmap for improving accessibility. Once gaps are identified, creating a clear plan for addressing them is important.

• Prioritize Critical Issues: Start with issues that severely impact usability for people with disabilities, such as missing alt text, keyboard traps, or unreadable screen reader content.
• Collaborate Across Teams: Work with developers, designers, and QA teams to assign fixes, establish timelines, and integrate accessibility improvements into your product roadmap.
• Document Planned Remediation: If an issue is known but not yet fixed, note it in the VPAT with a clear explanation and a projected resolution timeline.

7. Re-test and Update Your VPAT Regularly

Accessibility is not a one-time effort. As your product evolves, so should your VPAT.

• Re-test After Major Updates: Each time you release a new version or make significant UI changes, revalidate accessibility using tools like BrowserStack Accessibility to catch new issues.
• Keep the VPAT Current: Update your VPAT to reflect the latest testing results, fixes, and product features. An outdated VPAT can mislead buyers and affect procurement opportunities.

Who Should Create or Fill Out a VPAT?

Creating a VPAT is not just a copy-and-paste task; it requires careful coordination between multiple teams. Ideally, the document should be drafted or reviewed by individuals who:

• Understand the product’s functionality
• Are familiar with accessibility standards like WCAG 2.1, Section 508, or EN 301 549
• Have access to test results or firsthand knowledge of the product’s accessibility features (and limitations)

Typically, the responsibility for completing a VPAT falls to a cross-functional team that may include:

• Product Managers to provide feature-level context
• Developers to explain implementation details
• QA Engineers, especially those who handle accessibility testing
• Designers to clarify UX patterns and visual contrasts
• Compliance or Legal Teams to ensure the VPAT aligns with procurement and regulatory requirements
• Accessibility Consultants or Specialists to validate findings and guide language

Mistakes to Avoid

Even well-intentioned teams can fall into common pitfalls when creating a VPAT. Here are some mistakes that can reduce the document’s effectiveness, or worse, lead to failed procurement opportunities or legal risk:

• Copy-pasting from other VPATs without real testing: No two products are alike. Reusing someone else’s VPAT template or content can misrepresent your product’s compliance level and lead to inaccuracies that erode trust.
• Overstating compliance (e.g., marking everything as “Supports”): It might seem tempting to present your product as fully compliant. But unless you’ve done extensive testing to verify every WCAG criterion, avoid blanket “Supports” responses.
• Inconsistent Information: Your summary table, evaluation notes, and remarks must all align. For example, if you mark “Partially Supports” for a criterion, don’t write in the summary that all success criteria are met. Procurement teams scrutinize these inconsistencies.
• Not involving accessibility experts in the review: VPATs should not be authored in isolation. Involving accessibility experts ensures the report is grounded in proper testing, uses accurate terminology, and reflects real user experience, especially for assistive technologies.
• Ignoring updates after product changes or feature rollout: Your product is always evolving; your VPAT should, too. An outdated VPAT that doesn’t reflect new features or interface changes can be misleading and risk non-compliance.

How Accessibility Testing Supports Your VPAT

A VPAT is only as strong as the testing behind it. Without robust accessibility evaluations, the document becomes guesswork.

• Informs Accurate Reporting: Testing reveals how your product performs against WCAG or EN 301 549 criteria, ensuring your VPAT reflects real, tested results.
• Identifies Gaps and Fixes: By uncovering accessibility issues early, testing helps you document partial or non-conformance accurately and plan remediation.
• Strengthens Credibility: A VPAT backed by thorough, documented testing builds trust with procurement teams and users who rely on accessibility features.
• Supports Continuous Improvement: Ongoing testing ensures your VPAT stays aligned with your evolving product, helping you maintain compliance over time.

Why Choose BrowserStack for Accessibility Testing?

Ensuring accessibility compliance is a continuous effort that needs to be integrated into every phase of the development process.

BrowserStack Accessibility Testing provides powerful tools that help you identify and resolve accessibility issues early, ensuring your website or app meets the required accessibility standards, including WCAG guidelines.

Here’s why BrowserStack Accessibility Testing is an ideal choice:

• Automated Scanning: Quickly identify accessibility issues across your website and set up regular scans to monitor and maintain compliance proactively.
• Workflow Analyzer: Test user flows for common barriers, such as missing alt text, poor color contrast, or navigability issues, to ensure an accessible user experience.
• Assisted Testing: Easily discover complex accessibility issues with auto-generated prompts, making it simple for testers without deep accessibility knowledge to conduct thorough evaluations.
• Real-Device Screen Readers: Validate how your site works with popular screen readers like VoiceOver, NVDA, and TalkBack on real devices, ensuring accessibility for visually impaired users.
• Centralized Reporting Dashboard: View and manage all accessibility issues from one place. BrowserStack’s clear visual reports simplify tracking and fixing problems quickly.ibility health of your websites, schedule recurring scans, and stay audit-ready at all times.

Try BrowserStack Now

Conclusion

VPATs play a crucial role in advancing digital inclusivity. They allow organizations to demonstrate their commitment to accessibility, meet legal requirements, and unlock new business opportunities. More importantly, the VPAT creation process encourages teams to evaluate and enhance the user experience, ultimately benefiting all users.

With the right approach and reliable testing tools like BrowserStack Accessibility, you can create VPATs that are not just compliant but truly impactful. This helps build trust, broaden your audience, and contribute to a more inclusive digital world.