VPAT for Website / Web Applications :
Your web application must be accessible to every user. This includes those with disabilities. VPAT for Website / Web Application Ensuring accessibility is not only good practice but also often a matter of law. One of the best means of proving compliance is by preparing a Voluntary Product Accessibility Template (VPAT®).
This tutorial will guide you on preparing a VPAT for your web application. It covers various VPAT editions. It also includes accessibility testing and compliance mapping.

What is a VPAT?
VPAT for Website / Web Application : A VPAT (Voluntary Product Accessibility Template) is a formal document that assesses the extent to which an electronic product (like a web application) meets accessibility requirements including:
- WCAG 2.1/2.2 (Web Content Accessibility Guidelines)
- Section 508 (U.S. federal requirements)
- EN 301 549 (EU accessibility standards)
Organizations use VPATs to:
- Ensure compliance with legal requirements (e.g., Section 508, ADA, EU Web Accessibility Directive).
- Provide transparency to customers and government agencies.
- Spot and fix accessibility gaps before they become legal risks.
Step 1: Choose the Right VPAT Edition
There are several VPAT versions, each corresponding to different accessibility legislations. The most often VPAT for Website / Web Application used are:
VPAT Edition | Applies To | Standards Covered |
---|---|---|
VPAT 2.4 Rev 508 | U.S. federal contracts | Section 508 (Revised) |
VPAT 2.4 Rev EU | European market | EN 301 549 |
VPAT 2.4 Rev WCAG | Global compliance | WCAG 2.1/2.2 (Level A/AA) |
VPAT 2.4 Rev INT | Broad compliance | Combines 508, EN 301 549, and WCAG |
Which one do you need?
- If your web application serves U.S. government agencies, use VPAT 508.
- If targeting Europe, use VPAT EU (EN 301 549).
- For global compliance, use VPAT WCAG or VPAT INT (integrated).
Step 2: Conduct an Accessibility Audit
Before completing the VPAT, make sure your web application is tested for accessibility problems.
Key Areas to Review
- Keyboard Navigation (Are all functions usable without a mouse?)
- Screen Reader Compatibility (Sample with JAWS, NVDA, VoiceOver)
- Color Contrast & Readability (WCAG calls for 4.5:1 for regular text)
- Form Labels & Error Handling (Are fields adequately labeled?)
- Multimedia Accessibility (Captions for videos, transcripts for audio)
- Responsive Design (Does it work on mobile and desktop?)
Testing Tools
- Automated Testing: WAVE, Google Lighthouse
- Manual Testing: Keyboard-only navigation, screen reader tests
- User Testing: Engage people with disabilities for real-world feedback
Professional Accessibility Audit and Testing Services: Enabled.in offers comprehensive digital accessibility testing and audit services, including VPAT preparation and WCAG compliance validation
Step 3: Fill Out the VPAT Template
Download the current VPAT 2.4 from the ITI Website.
Example VPAT Structure (WCAG 2.1)
Criteria | Conformance Level | Remarks |
---|---|---|
1.1.1 Non-text Content (A) | Supports | All images have alt text |
1.2.1 Audio/Video Pre-recorded (A) | Partially Supports | Videos have captions but no audio descriptions |
1.3.1 Info & Relationships (A) | Supports | Proper HTML semantics used |
1.4.3 Contrast (Minimum) (AA) | Supports | Text passes 4.5:1 contrast ratio |
2.1.1 Keyboard Access (A) | Supports | All functionality keyboard-accessible |
2.4.4 Link Purpose (A) | Supports | Links are descriptive |
3.3.1 Error Identification (A) | Partially Supports | Form errors identified but not always clearly |
Conformance Levels:
- Supports (Fully compliant)
- Partially Supports (Some problems present)
- Does Not Support (Major accessibility barrier)
- Not Applicable (Does not apply to the product)
Step 4: Map Compliance Across Multiple Standards (If Needed)
When you need to comply with Section 508, WCAG, and EN 301 549, use the VPAT INT (Integrated) template.
Example Mapping:
Functionality | 508 Criteria | WCAG 2.1 | EN 301 549 | Conformance |
---|---|---|---|---|
Keyboard Access | 502.2.1 | 2.1.1 | 11.2.1 | Supports |
Color Contrast | 502.3.3 | 1.4.3 | 11.4.3 | Supports |
This will have one document addressing all mandated standards.
Step 5: Review & Publish the VPAT
- Legal Review: Double-check accuracy prior to release.
- Post on Your Site: Put in an Accessibility or Compliance area.
- Periodically Update: Re-evaluate when significant updates are made (e.g., new dashboard functionality).
Need Expert Help with Your VPAT?
Creating a compliant VPAT requires deep accessibility skill—something many organizations lack in-house.
At Enabled.in, we offer:
- Professional VPAT Certification Services – Get a legally sound VPAT prepared by accessibility experts.
- Comprehensive Audits – Manual + automated testing for WCAG, Section 508, and EN 301 549 compliance.
- Remediation Support – We don’t just identify issues; we help fix them.
Get Your VPAT Done Right – Request a Quote Now
Final Tips for an Effective VPAT
- Use the latest VPAT 2.5 Rev (April 24, 2025) for updated standards.
- Be transparent—clearly state limitations and remediation plans.
- Combine automated + manual testing for accurate results.
- Consider a third-party audit for higher credibility.
By following these steps—or partnering with experts—you’ll create a comprehensive VPAT. It demonstrates your web application’s accessibility compliance. It reduces legal risks and improves usability for all users.
Need help with WCAG 2.2 updates or VPAT customization?
Contact our team today for a consultation!
