VPAT Creation Guide: How to Complete a Voluntary Product Accessibility Template

A Voluntary Product Accessibility Template (VPAT) documents a product's accessibility conformance. Enterprise buyers, government agencies, and educational institutions increasingly require VPATs during procurement. Understanding how to create an accurate, useful VPAT helps vendors demonstrate accessibility commitment and win business.

What Is a VPAT?

Definition

A VPAT is a standardized document reporting how a product conforms to accessibility standards. The completed document is called an Accessibility Conformance Report (ACR).

VPAT: The template/format ACR: The completed document

Why VPATs Matter

Procurement requirements:

• Federal agencies require Section 508 conformance
• Many enterprises mandate VPATs
• Educational institutions require accessibility documentation
• Government contractors need compliance evidence

Competitive advantage:

• VPATs differentiate products
• Show accessibility commitment
• Enable sales to accessibility-conscious buyers

VPAT Versions and Standards

ITIC VPAT 2.x

The Information Technology Industry Council (ITI) maintains VPAT templates:

VPAT 2.4 Rev (Current):

• Section 508 criteria
• WCAG 2.0/2.1 criteria
• EN 301 549 criteria

Template editions:

• 508: U.S. federal requirements
• EU: European requirements
• WCAG: International web standards
• INT: International combined

Standards Covered

Section 508: U.S. federal accessibility requirements based on WCAG.

WCAG 2.1: Web Content Accessibility Guidelines.

EN 301 549: European standard for ICT accessibility.

VPAT Structure

Product Information

Required elements:

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

Conformance Levels

Each criterion receives a conformance level:

| Level                  | Meaning                            |
|------------------------|------------------------------------|
| **Supports**           | Fully meets the criterion          |
| **Partially Supports** | Some functionality meets criterion |
| **Does Not Support**   | Does not meet criterion            |
| **Not Applicable**     | Criterion doesn't apply            |
| **Not Evaluated**      | Has not been tested                |

Remarks and Explanations

For each criterion:

• Describe how product meets criterion
• Explain partial support details
• Note exceptions and workarounds
• Document planned improvements

Creating a VPAT

Step 1: Conduct Assessment

Complete accessibility evaluation:

• Automated testing
• Manual testing
• Assistive technology testing
• User flow testing

Document findings:

• Issue inventory
• Severity ratings
• Affected functionality

Step 2: Map to Criteria

For each WCAG criterion:

1. Review relevant product functionality
2. Assess conformance level
3. Document supporting evidence
4. Note any exceptions

Step 3: Complete Template

Download appropriate template: ITI provides templates at itic.org/policy/accessibility/vpat

Complete each section:

• Fill product information
• Enter conformance levels
• Write remarks for each criterion

Step 4: Review and Finalize

Quality checks:

• Accuracy of conformance claims
• Completeness of remarks
• Consistency across sections
• Clear, honest language

Writing Effective Remarks

Good Remarks

Specific and actionable:

Criterion: 1.1.1 Non-text Content

Conformance: Partially Supports

Remarks: All product images have alt text. Some
user-uploaded content may lack alt text. Users
are prompted to add alt text during upload.
Admin dashboard includes alt text audit tool.

Poor Remarks

Vague and unhelpful:

Criterion: 1.1.1 Non-text Content

Conformance: Partially Supports

Remarks: Most images have alt text.

Documenting Partial Support

Be specific about what works and what doesn't:

Conformance: Partially Supports

Remarks:
- All navigation elements are keyboard accessible
- Custom date picker requires mouse (alternative
  text input available)
- Modal dialogs trap focus appropriately
- Some third-party widgets lack keyboard support
  (using vendor version X.Y, update pending)

Common Mistakes

Overstatement

Claiming "Supports" when issues exist damages credibility. Auditors will verify claims.

Under-documentation

Sparse remarks leave readers guessing. Provide enough detail for informed decisions.

Stale VPATs

Products change; VPATs must be updated. State evaluation date clearly.

Missing Context

Not explaining product scope or evaluation limitations leaves gaps.

VPAT Maintenance

Update Triggers

• Major product releases
• Significant feature additions
• Remediation milestones
• Standards updates (e.g., WCAG 2.2)
• Annual review

Version Control

• Date each version
• Track changes between versions
• Archive previous versions
• Note what changed

Taking Action

VPATs demonstrate accessibility commitment and enable procurement success. Create accurate, detailed VPATs based on thorough evaluation, update regularly, and use them as tools for continuous improvement.

TestParty's monitoring provides the accessibility assessment data needed for accurate VPAT creation.

Schedule a TestParty demo and get a 14-day compliance implementation plan.

Related Resources

• Website Accessibility Audit Guide
• WCAG 2.2 Level AA Checklist
• Section 508 Compliance Checklist
• EN 301 549 Compliance