Introduction

A VPAT (Voluntary Product Accessibility Template) is a standardized document that reports how well your product conforms to accessibility standards like WCAG 2.2 and Section 508. VPATs are essential for government contracts, enterprise sales, and demonstrating commitment to accessibility compliance.

In this comprehensive guide, you'll learn everything about VPATs: what they are, why they matter, how to create them, what to document, and best practices for accuracy and credibility. You'll discover how VPATs help you win contracts and build trust with accessibility-conscious customers.

Create VPATs instantly: Use our VPAT Generator to create professional Accessibility Conformance Reports based on WCAG 2.2 and Section 508. It's free, works offline, and requires no signup!

What is a VPAT?

A VPAT (Voluntary Product Accessibility Template) is a document format that helps vendors document their product's conformance to accessibility standards. Modern VPATs are now called ACRs (Accessibility Conformance Reports).

VPAT Components

1. Product Information

• Product name and version
• Report date
• Contact information
• Evaluation methods used

2. Conformance Summary

• WCAG 2.2 Level A, AA, AAA
• Section 508
• EN 301 549 (European standard)

3. Success Criteria Tables

• Each WCAG criteria
• Conformance level (Supports, Partially Supports, Does Not Support, Not Applicable)
• Remarks and explanations

4. Legal Disclaimer

• Scope of evaluation
• Testing methodology
• Date of testing

VPAT Versions

VPAT 2.5 (Current - August 2023)

• WCAG 2.2 Level A, AA
• Section 508 (Revised 2017)
• EN 301 549 (2021)
• Optional: WCAG 2.2

Earlier Versions:

• VPAT 2.4 (March 2020) - WCAG 2.2
• VPAT 2.3 (October 2018) - WCAG 2.0
• VPAT 2.0 (April 2016) - First revised version

Generate ACR: VPAT Generator

Why VPATs Matter

Government Contracts

Required for:

• Federal government procurement (Section 508)
• State government contracts
• Educational institutions
• Healthcare organizations

Example:

RFP Requirement:
"Vendor must provide a current VPAT/ACR demonstrating
WCAG 2.2 Level AA conformance."
 
Without VPAT: Bid rejected
With VPAT: Eligible to compete

Enterprise Sales

Many large companies require VPATs:

• Fortune 500 companies
• Financial institutions
• Healthcare providers
• Educational institutions

Competitive Advantage

Legal Protection

• Documents your accessibility efforts
• Shows good faith compliance
• Provides defense against ADA lawsuits
• Demonstrates ongoing commitment

Customer Trust

• Transparency about accessibility
• Professional documentation
• Commitment to inclusive design
• Regular updates show maintenance

VPAT Structure

Header Section

Conformance Summary

Success Criteria Table

Conformance Levels

Supports:

• Functionality fully meets the criterion
• No known issues

Partially Supports:

• Most functionality meets criterion
• Some aspects don't conform
• Document specific issues

Does Not Support:

• Criterion not met
• Significant accessibility barriers
• Document impact

Not Applicable:

• Criterion doesn't apply to product
• Example: "Audio" criteria for text-only app

Creating a VPAT

Step 1: Conduct Accessibility Audit

Test your app: Accessibility Code Playground

Step 2: Document Findings

Check contrast: Contrast Checker

Step 3: Fill Out Template

Step 4: Review and Validate

Step 5: Publish and Maintain

WCAG 2.2 Level A & AA Criteria

Level A (30 criteria)

Perceivable (11 criteria)

• 1.1.1 Non-text Content
• 1.2.1 Audio-only and Video-only
• 1.2.2 Captions (Prerecorded)
• 1.2.3 Audio Description or Media Alternative
• 1.3.1 Info and Relationships
• 1.3.2 Meaningful Sequence
• 1.3.3 Sensory Characteristics
• 1.4.1 Use of Color
• 1.4.2 Audio Control

Operable (9 criteria)

• 2.1.1 Keyboard
• 2.1.2 No Keyboard Trap
• 2.1.4 Character Key Shortcuts
• 2.2.1 Timing Adjustable
• 2.2.2 Pause, Stop, Hide
• 2.3.1 Three Flashes or Below Threshold
• 2.4.1 Bypass Blocks
• 2.4.2 Page Titled
• 2.4.3 Focus Order
• 2.4.4 Link Purpose (In Context)
• 2.5.1 Pointer Gestures
• 2.5.2 Pointer Cancellation
• 2.5.3 Label in Name
• 2.5.4 Motion Actuation

Understandable (6 criteria)

• 3.1.1 Language of Page
• 3.2.1 On Focus
• 3.2.2 On Input
• 3.3.1 Error Identification
• 3.3.2 Labels or Instructions

Robust (1 criterion)

• 4.1.1 Parsing
• 4.1.2 Name, Role, Value

Level AA (20 criteria)

Perceivable (5 criteria)

• 1.2.4 Captions (Live)
• 1.2.5 Audio Description (Prerecorded)
• 1.3.4 Orientation
• 1.3.5 Identify Input Purpose
• 1.4.3 Contrast (Minimum)
• 1.4.4 Resize Text
• 1.4.5 Images of Text
• 1.4.10 Reflow
• 1.4.11 Non-text Contrast
• 1.4.12 Text Spacing
• 1.4.13 Content on Hover or Focus

Operable (6 criteria)

• 2.4.5 Multiple Ways
• 2.4.6 Headings and Labels
• 2.4.7 Focus Visible

Understandable (4 criteria)

• 3.1.2 Language of Parts
• 3.2.3 Consistent Navigation
• 3.2.4 Consistent Identification
• 3.3.3 Error Suggestion
• 3.3.4 Error Prevention (Legal, Financial, Data)

Robust (0 criteria)

• (All Level A already)

Common VPAT Mistakes

1. Being Too Optimistic

2. Vague Remarks

3. Missing Timeline for Fixes

4. Not Testing Thoroughly

5. Outdated Information

VPAT Best Practices

Be Honest and Transparent

Provide Specific Details

Include Testing Methodology

Document Known Issues

Keep it Updated

Section 508 Requirements

Revised Section 508 (2017)

Aligns with WCAG 2.0 Level A & AA, plus additional requirements:

Software:

• 502.3 Accessibility Services
• 502.4 Platform Accessibility Features

Hardware:

• 402 Closed Functionality
• 407 Operable Parts

Support Documentation:

• 602 Support Documentation
• 603 Support Services

Authoring Tools:

• 504 Authoring Tools

International Standards

EN 301 549 (Europe)

EU standard for ICT accessibility:

• Harmonized with WCAG 2.2
• Additional requirements for hardware
• Procurement standard for EU

ADA (United States)

Americans with Disabilities Act:

• No specific technical standard
• WCAG 2.2 Level AA considered best practice
• Legal requirement for public accommodations

VPAT vs Accessibility Statement

VPAT (ACR)

Purpose: Detailed conformance documentation

Accessibility Statement

Purpose: Public commitment to accessibility

Both are important! VPAT for B2B/procurement, statement for users.

Maintaining Your VPAT

Update Triggers

Version Control

Continuous Improvement

Conclusion

VPATs (ACRs) are essential for government contracts, enterprise sales, and demonstrating serious commitment to accessibility. Creating honest, detailed, and regularly updated VPATs helps you win business and build trust with accessibility-conscious customers.

Key Takeaways:

• VPAT = detailed technical conformance report
• Required for government procurement
• Be honest about conformance levels
• Document specific issues and timelines
• Update with each major release
• Combine with public accessibility statement
• Test thoroughly before documenting

Generate your VPAT: Use our VPAT Generator to create professional Accessibility Conformance Reports instantly!

What products will you document? Whether it's software, websites, or hardware, you now have the knowledge to create credible, compliant VPATs!

Related Tools & Resources

Document accessibility with these free tools:

• VPAT Generator - Create Accessibility Conformance Reports (WCAG 2.2 & Section 508)
• Accessibility Code Playground - Test and validate accessibility features
• PDF Accessibility Checker - Ensure documents are accessible
• Contrast Checker - Verify color contrast ratios

All tools are 100% free, require no signup, and respect your privacy.

Further Reading

• Getting Started with Web Accessibility
• Building Accessible Forms
• PDF Accessibility Guide

Official Resources

• ITI VPAT: https://www.itic.org/policy/accessibility/vpat
• Section 508: https://www.section508.gov/
• WCAG 2.2: https://www.w3.org/WAI/WCAG21/quickref/
• EN 301 549: https://www.etsi.org/deliver/etsi_en/301500_301599/301549/

Frequently Asked Questions

Document thoroughly! 📋