WCAG 1.1.1Level APerceivable
Non-text Content
All non-text content (images, icons, SVGs, charts) has a text alternative that serves the equivalent purpose.
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.
Section 508U.S. Federal Standards
WCAG 2.1 AA28 Success Criteria
ITI VPAT® 2.4Official ACR Template
EN 301 549EU Procurement Aligned
Interactive VPAT 2.4 Self-Assessment Workbench
Evaluate your product against 28 WCAG criteria, toggle conformance statuses, document code-level remarks, and export an audit-ready Markdown report instantly.
28Supports
0Exceptions
0Fails
0Not Applicable
Evaluation Readiness
100%
WCAG 1.2.1Level APerceivable
Audio-only and Video-only (Prerecorded)
Text transcripts are provided for prerecorded audio-only and audio descriptions for video-only media.
WCAG 1.2.2Level APerceivable
Captions (Prerecorded)
Synchronized captions are provided for all prerecorded audio content in video media.
WCAG 1.3.1Level APerceivable
Info and Relationships
Information, structure, headings, form labels, and relationships conveyed visually can be programmatically determined.
WCAG 1.3.2Level APerceivable
Meaningful Sequence
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
WCAG 1.4.1Level APerceivable
Use of Color
Color is not used as the sole visual means of conveying information, indicating an action, prompting a response, or distinguishing an element.
WCAG 1.4.3Level AAPerceivable
Contrast (Minimum)
Visual presentation of text and images of text has a contrast ratio of at least 4.5:1 (3:1 for large text).
WCAG 1.4.4Level AAPerceivable
Resize Text
Text can be resized without assistive technology up to 200 percent without loss of content or functionality.
WCAG 1.4.10Level AAPerceivable
Reflow
Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions at 320px width.
WCAG 1.4.11Level AAPerceivable
Non-text Contrast
The visual presentation of user interface components and graphical objects has a contrast ratio of at least 3:1 against adjacent colors.
WCAG 2.1.1Level AOperable
Keyboard Operability
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
WCAG 2.1.2Level AOperable
No Keyboard Trap
If keyboard focus can be moved to a component on the page using a keyboard interface, focus can be moved away from that component.
WCAG 2.4.1Level AOperable
Bypass Blocks
A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
WCAG 2.4.3Level AOperable
Focus Order
If a Web page can be navigated sequentially, focusable components receive focus in an order that preserves meaning and operability.
WCAG 2.4.4Level AOperable
Link Purpose (In Context)
The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined context.
WCAG 2.4.6Level AAOperable
Headings and Labels
Headings and labels describe topic or purpose accurately and clearly.
WCAG 2.4.7Level AAOperable
Focus Visible
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
WCAG 2.5.3Level AAOperable
Label in Name
For user interface components with labels that include text or images of text, the name contains the text presented visually.
WCAG 3.1.1Level AUnderstandable
Language of Page
The default human language of each Web page can be programmatically determined.
WCAG 3.2.1Level AUnderstandable
On Focus
When any user interface component receives focus, it does not initiate a change of context unexpectedly.
WCAG 3.2.2Level AUnderstandable
On Input
Changing the setting of any user interface component does not automatically cause a change of context unless warned.
WCAG 3.3.1Level AUnderstandable
Error Identification
If an input error is automatically detected, the item that is in error is identified and the error is described in text.
WCAG 3.3.2Level AUnderstandable
Labels or Instructions
Labels or instructions are provided when content requires user input.
WCAG 3.3.3Level AAUnderstandable
Error Suggestion
If an input error is detected and suggestions for correction are known, the suggestion is provided to the user.
WCAG 3.3.4Level AAUnderstandable
Error Prevention (Legal, Financial, Data)
For Web pages that cause legal commitments or financial transactions, data submissions are reversible, checked, or confirmed.
WCAG 4.1.1Level ARobust
Parsing
In content implemented using markup languages, elements have complete start and end tags, elements are nested according to specifications.
WCAG 4.1.2Level ARobust
Name, Role, Value
For all user interface components, the name and role can be programmatically determined; states, properties, and values can be set.
WCAG 4.1.3Level AARobust
Status Messages
In content implemented using markup languages, status messages can be programmatically determined through role or properties.
28 Supports • 0 Exceptions • 0 Fails
Compliance Note: This interactive self-assessment workbench provides technical guidance for authoring a self-issued Accessibility Conformance Report (ACR). For high-stakes federal procurements, enterprise RFPs, or strict compliance audits requiring independent third-party certification, request our certified audit services below.
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