Section 508 & WCAG 2.1 AA Readiness

VPAT 2.4 Compliance Checklist & Interactive ACR Generator

Evaluate your software platform against WCAG 2.1 Level A & AA standards, track conformance levels, and export a standardized Accessibility Conformance Report for enterprise and government procurement.

Legal & Compliance Disclaimer: This interactive checklist and template tool provides general technical guidance for preparing a self-issued Accessibility Conformance Report (ACR). It does not constitute formal legal counsel or accredited accessibility certification. For formal submission to federal agencies or enterprise RFPs, third-party audit verification is recommended.

Interactive VPAT 2.4 Self-Assessment Tool

Select conformance levels for each WCAG criterion, record technical remarks, and export your completed report in standard Markdown table format.

VPAT 2.4 Assessment Tool

Generate standardized Accessibility Conformance Reports (ACR) directly from your browser. All progress is automatically saved securely on your device.

No saved sessions detected.

Understanding VPAT Conformance Levels

The Information Technology Industry Council (ITI) defines four official terms for reporting conformance in an Accessibility Conformance Report:

Supports

Supports

The functionality of the product has been verified to meet the success criterion without exceptions. Source code structures, ARIA attributes, and keyboard flows fully satisfy WCAG requirements.

Supports with Exceptions

Supports with Exceptions

Some functionality of the product does not fully meet the success criterion, but workarounds exist or only specific secondary modules are affected. Technical remarks must detail the exact exception.

Does Not Support

Does Not Support

The majority of product functionality fails the success criterion, or key user flows are blocked for assistive technology users. Remarks should detail remediation plans.

Not Applicable

Not Applicable

The success criterion does not apply to the product. For example, audio caption criteria on a web application that contains zero audio or video media.

Raw VPAT® 2.4 ACR Markdown Template

Copy this pre-formatted GFM markdown table directly into your GitHub repository documentation or software release notes:

# Accessibility Conformance Report (VPAT® 2.4 Edition)

**Product Name:** [Your Product Name]
**Product Version:** [1.0.0]
**Report Date:** [YYYY-MM-DD]
**Contact Email:** [[email protected]]
**Evaluation Standard:** WCAG 2.1 Level A & Level AA

## Table 1: WCAG 2.1 Level A & AA Success Criteria

| Criteria | Conformance Level | Remarks and Explanations |
| :--- | :--- | :--- |
| **1.1.1 Non-text Content** (Level A) | Supports | All non-text UI elements have text equivalents or aria-labels. |
| **1.3.1 Info and Relationships** (Level A) | Supports | Page landmarks, form labels, and heading hierarchy are semantic. |
| **1.4.3 Contrast (Minimum)** (Level AA) | Supports | Body text maintains minimum 4.5:1 contrast ratio against background. |
| **2.1.1 Keyboard** (Level A) | Supports | All interactive components are navigable via keyboard interface. |
| **2.4.7 Focus Visible** (Level AA) | Supports | Visible outline focus rings are enforced across all controls. |
| **3.3.1 Error Identification** (Level A) | Supports | Form validation errors are described in text to screen readers. |
| **4.1.2 Name, Role, Value** (Level A) | Supports | Custom ARIA widgets expose correct roles, states, and properties. |

Why Enterprise Buyers Reject Unverified VPATs

Procurement officers for federal agencies (GSA, DoD, VA), state universities, and Fortune 500 enterprises review dozens of ACRs monthly. A common mistake SaaS founders make is submitting a self-authored VPAT that marks every single criterion as "Supports" without detailed technical remarks.

Procurement evaluators recognize blanket self-assessments as red flags. If a product claims full support without explaining how keyboard focus or screen reader parsing is handled, procurement teams routinely pause procurement or demand a certified third-party audit report.

Detailed Remarks are Mandatory: Every "Supports" or "Supports with Exceptions" entry requires specific code-level explanations.
Honest Exceptions Win Deals: Procurement teams accept software with documented exceptions if a clear remediation timeline is provided.
Third-Party Validation: Certified audits from independent digital accessibility specialists remove liability for enterprise buyers.

Request Third-Party VPAT Audit

We conduct manual and automated WCAG 2.1 AA audits and author certified, legally defensible VPAT 2.4 ACR reports for your procurement deals.

Frequently Asked Questions

Clear answers to technical and procedural questions about VPAT 2.4 compliance and ACR authoring.

What is the difference between a VPAT and an ACR?

VPAT (Voluntary Product Accessibility Template) is the blank template document created by the Information Technology Industry Council (ITI). An ACR (Accessibility Conformance Report) is the completed report produced after auditing a specific software product against VPAT criteria.

Which VPAT 2.4 edition do I need?

There are four VPAT 2.4 editions: WCAG Edition (WCAG 2.1 Level A & AA for commercial/global SaaS), 508 Edition (US Federal agencies under Section 508), EU Edition (European Union under EN 301 549), and International Edition (combines all three standards).

Is a VPAT legally mandatory for software sales?

For US Federal government procurement under Section 508 and state government / public higher-education institutions, a completed ACR is mandatory. Commercial enterprise procurement teams also require an ACR to verify vendor risk under ADA Title III.

What happens if I mark 'Supports with Exceptions' on my ACR?

Marking 'Supports with Exceptions' is normal and expected for real-world software. Procurement teams prefer honest exception reporting with clear remediation timelines over unverified claims of 100% compliance.

Can a software team author a VPAT internally?

Yes, software teams can complete a self-issued ACR internally. However, for high-value government contracts or strict enterprise procurement, buyers frequently require an independent third-party audit to verify claims.

How often does a VPAT ACR need to be updated?

An ACR should be updated whenever a major software version is released, key UI components are redesigned, or new feature modules are added to the platform.

Need a Certified Third-Party VPAT Audit?

Our team conducts comprehensive WCAG 2.1 AA audits, fixes code-level violations, and authors official ACR documentation for your buyers.

Request Your Audit Package