Skip to content

ACR Template Structure — The VPAT 2.4 Format

DodaTech Updated 2026-06-28 4 min read

In this tutorial, you will learn about ACR Template Structure. We cover key concepts, practical examples, and best practices to help you master this topic.

The VPAT 2.4 ACR template contains four main tables: WCAG criteria (all levels A through AAA), Section 508 paragraphs, EN 301 549 criteria for European procurement, and an optional hardware section, plus a product overview.

What You'll Learn

You will learn the structure of the VPAT 2.4 ACR template, what each section contains, and how to navigate the template efficiently.

Why It Matters

Understanding the template structure helps you fill it out correctly and find the right sections for different audiences.

Real-World Use

DodaTech's Accessibility team uses the VPAT 2.4 template as their primary conformance documentation. They fill out only the relevant tables for each product.

flowchart TD
  A[VPAT 2.4 Template] --> B[Product Overview]
  A --> C[Table 1: WCAG]
  A --> D[Table 2: Section 508]
  A --> E[Table 3: Hardware]
  A --> F[Table 4: EN 301 549]
  B --> G[Product name, version, date]
  C --> H[All WCAG 2.x criteria]
  D --> I[Section 508 paragraphs]
  E --> J[If applicable]
  F --> K[European standard criteria]

Product Overview Section

Contains the product name, version number, evaluation date, vendor contact information, and which standards are covered.

Table 1: WCAG Criteria

This is the core of the VPAT. It lists every WCAG success criterion with columns for conformance level (A, AA, AAA), conformance rating (Supports, Partially Supports, Does Not Support, Not Applicable), and remarks and explanations.

Table 2: Section 508 Paragraphs

Covers Section 508 requirements that are not already covered by WCAG, including software keyboard access, focus indicators, and documentation.

Table 3: Hardware

Only applicable for hardware products. Includes requirements for accessible controls, mechanical operation, and connectivity.

Table 4: EN 301 549

European procurement requirements including WCAG-based criteria plus additional European-specific requirements like closed functionality and real-time text.

<!-- VPAT excerpt structure -->
<table>
  <caption>WCAG 2.2 Level AA Criteria</caption>
  <thead>
    <tr>
      <th scope="col">Criteria</th>
      <th scope="col">Conformance Level</th>
      <th scope="col">Remarks and Explanations</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>1.1.1 Non-text Content (Level A)</td>
      <td>Supports</td>
      <td>All images have descriptive alt text. Decorative images use empty alt.</td>
    </tr>
    <tr>
      <td>1.4.3 Contrast (Minimum) (Level AA)</td>
      <td>Partially Supports</td>
      <td>Most text meets 4.5:1 ratio. Some disabled button text at 3.0:1 is documented in Appendix A.</td>
    </tr>
    <tr>
      <td>2.1.1 Keyboard (Level A)</td>
      <td>Supports</td>
      <td>All functionality is operable by keyboard. Tested with Tab, Enter, and Space keys.</td>
    </tr>
  </tbody>
</table>

Common Mistakes

1. Filling Out All Tables Even When Not Applicable

Only fill out the tables that apply to your product. Hardware table is only for hardware products.

2. Inconsistent Criteria Order

Criteria should be listed in WCAG order (1.1.1, 1.1.2, etc.). Random order makes the VPAT hard to review.

3. Missing the Product Overview

The product overview is essential. Without it, buyers do not know what product the VPAT covers.

4. Copying Remarks Across Criteria

Each criterion should have unique remarks. Copying the same remark for all criteria suggests you did not test.

5. Forgetting to Select Standards

The VPAT covers multiple standards. Indicate which standards are included. Leaving this ambiguous confuses buyers.

6. Not Including a Date

Every VPAT must have an evaluation date. Without a date, the VPAT is not a valid document.

7. Using Complex Formatting

VPATs are often reviewed by procurement officers who need to scan quickly. Keep formatting simple and consistent.

Practice Questions

1. What are the four tables in the VPAT 2.4 template?

WCAG criteria, Section 508 paragraphs, hardware (optional), and EN 301 549 criteria.

2. What information goes in the product overview section?

Product name, version number, evaluation date, vendor contact, and standards covered.

3. Which table is the core of the VPAT?

Table 1: WCAG criteria. It contains all success criteria with conformance ratings and remarks.

4. When should the hardware table be filled out?

Only when the product includes physical hardware components.

5. Challenge: Download the VPAT 2.4 template. Review its structure. Identify which tables you would need to fill out for a web application product.

FAQ

Can I add my own criteria to the VPAT?

The standard template should not be modified. You can add appendices with additional information.

Do I need to fill out all rows in every table?

Only rows applicable to your product. Mark non-applicable rows as Not Applicable with a brief explanation.

Can I combine multiple products in one VPAT?

No. Each product needs its own VPAT. Variations of the same product may share a VPAT with version notes.

What format should I use for the VPAT?

ITIC recommends HTML for web publishing and PDF for procurement responses. Include the VPAT on your website.

Should I include the VPAT template instructions in my report?

No. Remove the instructions before publishing. Only include your actual conformance information.

Mini Project

Create a skeleton VPAT 2.4 for a fictional product. Fill out the product overview section. Create the WCAG table header and add 5 example rows with sample data.

What's Next

Learn about the Product Overview section in detail. Then explore the Criteria Table and conformance ratings.

Built by the developers of DodaTech

Doda Browser, DodaZIP & Durga Antivirus Pro