Product Overview Section — Setting the Context for Your VPAT

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

The VPAT product overview section identifies the product name, version number, evaluation date, vendor contact information, standards included, and evaluation methodology used for the conformance assessment.

What You'll Learn

You will learn what to include in the product overview section of a VPAT and why each field matters for procurement evaluation.

Why It Matters

The product overview is the first thing procurement officers read. Missing or incomplete information can lead to immediate rejection regardless of the conformance ratings.

Real-World Use

DodaTech's VPAT overview is concise and complete. It includes the exact version of Durga Antivirus Pro evaluated, the date of evaluation, and which standards are covered.

flowchart TD
  A[Product Overview] --> B[Essential fields]
  A --> C[Optional fields]
  B --> D[Product name and version]
  B --> E[Evaluation date]
  B --> F[Vendor name and contact]
  B --> G[Standards included]
  B --> H[Evaluation methodology]
  C --> I[Product description]
  C --> J[Supported platforms]
  C --> K[Known limitations summary]

Essential Fields

Product Name and Version

The exact product name and version number that was evaluated. Including the version is critical because different versions may have different conformance status.

Evaluation Date

When the evaluation was completed. Updated VPATs should show the current date.

Vendor Name and Contact

Your organization name and contact information for Accessibility questions.

Standards Included

Check which standards are included: WCAG 2.x, Section 508, EN 301 549. Indicate if all standards are covered or only a subset.

Evaluation Methodology

Describe how the evaluation was conducted. Automated tools used, manual testing methods, screen reader testing, and user testing.

function createProductOverview(name, version, date, standards) {
  return {
    productName: name,
    productVersion: version,
    vpatVersion: '2.4',
    evaluationDate: date,
    lastUpdated: date,
    vendor: {
      name: 'DodaTech',
      contact: 'accessibility@dodatech.com'
    },
    standardsIncluded: standards,
    evaluationMethodology: [
      'Automated testing with axe-core v4.8',
      'Manual keyboard testing',
      'Screen reader testing with NVDA 2024 and VoiceOver',
      'Color contrast verification with Stark plugin',
      'Manual review of each WCAG success criterion'
    ],
    notes: `This VPAT documents conformance for ${name} version ${version} as of ${date}.`
  };
}

const overview = createProductOverview(
  'Durga Antivirus Pro',
  '4.2.0',
  '2026-06-28',
  ['WCAG 2.2 AA', 'Section 508', 'EN 301 549']
);

console.log(overview);

Expected output:

{
  productName: 'Durga Antivirus Pro',
  productVersion: '4.2.0',
  vpatVersion: '2.4',
  evaluationDate: '2026-06-28',
  lastUpdated: '2026-06-28',
  vendor: { name: 'DodaTech', contact: 'accessibility@dodatech.com' },
  standardsIncluded: ['WCAG 2.2 AA', 'Section 508', 'EN 301 549'],
  evaluationMethodology: ['Automated testing with axe-core v4.8', 'Manual keyboard testing', 'Screen reader testing with NVDA 2024 and VoiceOver', 'Color contrast verification with Stark plugin', 'Manual review of each WCAG success criterion'],
  notes: 'This VPAT documents conformance for Durga Antivirus Pro version 4.2.0 as of 2026-06-28.'
}

Common Mistakes

1. Omitting the Product Version

A VPAT without a version number is not a valid procurement document. Always include the exact version.

2. Using a Stale Date

Using last year's date suggests the VPAT is outdated. Update the evaluation date when you review or update the VPAT.

3. Vague Methodology Description

Tested with tools is insufficient. Specify which tools, versions, and methods. This adds credibility.

4. Not Listing Which Standards Are Included

Buyers need to know which standards the VPAT covers. If you include only Section 508 but the buyer needs EN 301 549, they need to know.

5. Missing Contact Information

Buyers with questions need a contact. Include an email address or accessibility feedback form URL.

6. Too Much Marketing Language

The product overview should be factual, not promotional. Save marketing for the product page.

7. Not Updating the Overview When Standards Change

If you add support for a new standard, update the overview. Stale overviews reduce VPAT credibility.

Practice Questions

1. What are the essential fields in the product overview?

Product name and version, evaluation date, vendor contact, standards included, and evaluation methodology.

2. Why must the product version be included in the VPAT?

Different versions may have different conformance status. Buyers need to know exactly which version was evaluated.

3. What should the evaluation methodology section include?

Describe which automated tools, manual testing methods, and assistive technologies were used for the evaluation.

4. Why is the evaluation date important?

It tells buyers how current the VPAT is. Outdated VPATs may not reflect the current product.

5. Challenge: Write a product overview section for a real product you use. Fill out all essential fields.

FAQ

Mini Project

Create a product overview section for a fictional product or a real product you use. Include all essential fields. Write a clear methodology description.

What's Next

Learn about the Criteria Table and how to assign conformance ratings. Then explore Evaluation Methods for testing.