VPAT History — From Section 508 to Modern Conformance Reporting

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

The VPAT originated with Section 508 of the Rehabilitation Act in 1998, evolving from US federal procurement documentation to an international standard covering WCAG, EN 301 549, and multiple regional Accessibility standards.

What You'll Learn

You will learn the history of the VPAT, how it evolved alongside accessibility standards, and why understanding its history matters for creating credible reports today.

Why It Matters

Understanding the VPAT's origins helps you understand its purpose and structure. A VPAT is not just a form to fill out. It is a tool for procurement transparency that has evolved over 25 years.

Real-World Use

DodaTech's accessibility team studied VPAT history to understand why certain sections exist. This understanding helped them create more thorough, credible reports.

flowchart LR
  A[1998: Section 508] --> B[2000: Original VPAT]
  B --> C[2015: VPAT 2.0]
  C --> D[2018: VPAT 2.3]
  D --> E[2020: VPAT 2.4]
  E --> F[Current: VPAT 2.4]
  A --> G[Rehabilitation Act amendment]
  C --> H[Added WCAG support]
  D --> I[Section 508 refresh]
  E --> J[EN 301 549 support]

Origins: Section 508 (1998)

Section 508 was amended in 1998 to require federal agencies to procure accessible technology. The VPAT was created to provide a standardized format for vendors to document conformance.

VPAT 2.0 (2015)

The first major update. Added support for WCAG 2.0 criteria. Made the template more comprehensive.

VPAT 2.3 (2018)

Updated to reflect the Section 508 refresh that incorporated WCAG 2.0 AA. Added support for EN 301 549.

VPAT 2.4 (2020)

The current version. Supports WCAG 2.x, Section 508, and EN 301 549 in a single template. Includes improved structure for remarks and explanations.

The Future of VPAT

As WCAG evolves and new accessibility laws emerge, the VPAT will continue to evolve. Future versions may support additional regional standards and newer WCAG versions.

function getVPATVersionInfo(year) {
  const history = {
    2000: { version: 'Original', focus: 'Section 508', notable: 'First VPAT template created' },
    2015: { version: '2.0', focus: 'WCAG 2.0 + Section 508', notable: 'Major update with WCAG support' },
    2018: { version: '2.3', focus: 'WCAG 2.0 + EN 301 549', notable: 'Section 508 refresh alignment' },
    2020: { version: '2.4', focus: 'WCAG 2.x + 508 + EN 301 549', notable: 'Current version, multi-standard' }
  };

  return history[year] || { message: 'Version information not available for that year' };
}

console.log(getVPATVersionInfo(2018));

Expected output:

{ version: '2.3', focus: 'WCAG 2.0 + EN 301 549', notable: 'Section 508 refresh alignment' }

Why History Matters

The VPAT's evolution shows the trend toward harmonization of accessibility standards. Understanding this trend helps you create VPATs that will remain relevant as standards evolve.

Common Mistakes

1. Using the Wrong VPAT Version

VPAT 2.4 is current. Using 2.3 or older risks rejection by buyers who know the latest version.

2. Not Understanding Why Sections Exist

Each section of the VPAT exists because of a specific legal or procurement requirement. Understanding the history helps you fill each section correctly.

3. Ignoring EN 301 549

VPAT 2.4 added EN 301 549 support specifically for EU procurement. Ignoring it misses the purpose of the update.

4. Treating VPAT as Static

The VPAT has evolved significantly. Future versions will add more standards. Plan for updates.

5. Not Mentioning Which Standards Apply

The VPAT covers multiple standards. Clearly indicate which standards are included in your evaluation.

6. Assuming All Buyers Know VPAT History

New buyers may not understand VPAT versions. Explain which version you are using and what it covers.

7. Not Planning for WCAG Version Updates

As WCAG 2.2 becomes more widely adopted, VPAT may be updated. Plan to update your VPAT when new versions are released.

Practice Questions

1. What legislation led to the creation of the VPAT?

Section 508 of the Rehabilitation Act of 1973, amended in 1998.

2. What is the current VPAT version?

VPAT 2.4, published in 2020.

3. What major addition was made in VPAT 2.4?

Support for EN 301 549 (European accessibility standard) alongside WCAG and Section 508.

4. Why was VPAT 2.3 created in 2018?

To align with the Section 508 refresh that incorporated WCAG 2.0 AA.

5. Challenge: Research what changes might be needed for a future VPAT 2.5. What new standards or WCAG versions should it support?

FAQ

Mini Project

Create a timeline of VPAT history. Include each major version, the year it was published, and what new standards it added.

What's Next

Learn about the ACR Template Structure in detail. Then explore the Product Overview section.