VPAT & ACR SERVICES

Accessibility testing that leads to a credible ACR.

Need accessibility documentation for a customer, procurement team, or contract?

EqualAccess. evaluates your digital product against the applicable accessibility requirements, documents what we find, and helps you prepare a clear Accessibility Conformance Report using the appropriate VPAT® template.

  • Manual Testing
  • Assistive Technology
  • WCAG Evaluation
  • Clear Documentation

Websites · Web Applications · Software · Digital Products

EqualAccess.Illustrative report

Accessibility
Conformance Report

Example product · Evaluation summary

Illustrative findings, not actual client results.
CriterionFinding
Keyboard AccessSupports
Focus OrderSupports
Form ErrorsPartially Supports
Name, Role, ValueSupports
Tested. Findings documented. Report prepared.
Visual demonstration only. Human experts perform the evaluation and prepare the report. Scope and results vary by product.

THE TEMPLATE. THE EVALUATION. THE REPORT.

The VPAT® is the template.
The ACR is the report.

The terms are often used interchangeably. Understanding the difference makes it easier to know what you are asking for—and what your customer needs.

VPAT®

Voluntary Product Accessibility Template

A standardized template developed by the Information Technology Industry Council (ITI) for documenting how information and communications technology supports applicable accessibility requirements.

The structure used to organize and report the evaluation.

EVALUATE
& DOCUMENT

ACR

Accessibility Conformance Report

Once the VPAT® has been completed for a specific product using actual evaluation results, the finished document is an Accessibility Conformance Report.

The report you can share with customers, procurement teams, government buyers, and other organizations evaluating your product.

You do not simply “get a VPAT.” A useful ACR starts with an actual evaluation of the product it describes.

Read ITI’s VPAT® explanation and GSA’s guide to preparing an ACR.

MORE THAN A FORM

An ACR is only as useful as the evaluation behind it.

Completing a template without evaluating the product can produce vague or inaccurate documentation. Our approach starts with the actual product: test first, document second.

  • Product
  • Testing
  • Evidence
  • ACR
  • Test the product

    Evaluate real interfaces, components, workflows, and functionality to establish how the product behaves.

  • Use human testing

    Combine automated tools with manual keyboard, screen reader, and interaction testing where appropriate.

  • Document accurately

    Connect findings to useful explanations of how the product supports the applicable requirements.

  • Identify what needs work

    Make accessibility barriers visible so your team understands what needs remediation.

A polished document cannot replace a thorough accessibility evaluation.

WHEN AN ACR BECOMES IMPORTANT

When customers ask about accessibility, be ready with a clear answer.

Accessibility documentation can be part of procurement, vendor reviews, questionnaires, RFPs, and customer due diligence.

Need an ACR for an upcoming procurement review?

Talk to EqualAccess.

How ACRs support federal ICT procurement.

  • A customer requested a VPAT

    You need to determine what should actually be tested and reported in response to an accessibility request.

  • You are selling to government

    Your product is being evaluated for public-sector procurement, with accessibility requirements in the purchasing process.

  • Enterprise procurement is asking questions

    A prospective customer wants evidence of product accessibility before approving a purchase.

  • Your existing ACR is outdated

    The product has changed, or the report no longer accurately describes the current experience.

  • You want evidence before publishing

    Your team needs a reliable assessment before making accessibility representations to customers.

THE EVALUATION

We test the product
behind the report.

The evaluation depends on your product, the relevant VPAT® edition, and the requirements being documented. We agree the product scope, environments, workflows, and methods before testing begins.

Example product · Account settings
workspaceOverview   Settings

Account details

Manage your profile and notification preferences.

Full nameAlex Morgan
Email addressalex@example.com
Save changes
  • Programmatic field labels
  • Instructions and error relationships
  • Keyboard operation and visible focus
Illustrative interface with inspection markers. This visual does not collect information.
  • Automated accessibility testing

    Tools identify detectable issues and provide technical signals for deeper evaluation.

  • Keyboard testing

    Can important functionality be reached, operated, and understood without a mouse?

  • Screen reader testing

    Relevant interfaces and workflows are evaluated with assistive technology.

  • Forms & validation

    Labels, instructions, required fields, errors, status messages, and interaction behavior.

  • Navigation & focus

    Focus order, visible focus, menus, dialogs, navigation patterns, and other controls.

  • Structure & semantics

    Headings, landmarks, names, roles, states, relationships, tables, and programmatic information.

  • Visual accessibility

    Color contrast, text presentation, reflow, zoom, non-text content, and related requirements.

  • Core user journeys

    Authentication, account management, search, purchasing, applications, and other important tasks.

A scanner alone cannot establish accessibility conformance. W3C describes testing as a combination of automated checks and human evaluation. Read W3C’s conformance guidance.

HOW IT WORKS

From product evaluation
to clear documentation.

Our five-step accessibility process connects the product, its test evidence, any agreed fixes, and the resulting ACR.

01 · Assess

Define the product
and requirements.

Identify the product and version, important functionality, environments, and standards the report needs to address. Initial analysis helps establish the technical scope and evaluation plan.

OUTPUTEvaluation scope
EVALUATION BRIEF
Product
Example web application · v3.1
Journeys
Sign in, account settings, forms
Reporting target
Agreed VPAT® edition and criteria

02 · Manual Testing

Evaluate real interactions.

Experts combine the automated findings with keyboard, screen reader, and product-specific testing. We map observed behavior to the relevant criteria and prioritize barriers that need attention.

OUTPUTTechnical findings and evidence
TESTING NOTES
  • Primary navigation
  • Form interactions
  • Date picker Barrier found

Keyboard behavior is recorded alongside the affected component and criterion.

03 · Code-Level Remediation

Address the underlying barrier.

When remediation is included, we correct agreed accessibility issues directly or work with your developers before the report is finalized.

Reporting can also document a product with known limitations. Remediation is agreed separately within the engagement.

OUTPUTAgreed technical corrections
COMPONENT UPDATE
<button type="button"
  aria-label="Choose date"
  aria-expanded="false">
  Choose date
</button>

Illustrative markup excerpt. Keyboard behavior, focus, and state changes also need implementation and testing.

04 · Retest & Verify

Check the changes
in the product.

Retest remediated functionality with the agreed methods. Confirm the observed behavior and document any remaining limitations so the report reflects the evaluated product state.

OUTPUTVerified findings
DATE PICKER · RETEST
  • Keyboard operation
  • Focus management
  • Assistive-technology behavior
Illustrative verified result

05 · Documentation

Prepare the ACR.

Translate the evaluation evidence into criterion-level conformance findings and useful remarks. Prepare the Accessibility Conformance Report using the appropriate VPAT® edition, including the tested product version, methods, scope, and limitations.

OUTPUTAccessibility Conformance Report
REPORT CONTENTS
  • Product and version
  • Evaluation methods
  • Conformance findings
  • Remarks and limitations

Illustrative workflow. Human experts carry out the evaluation and reporting. Testing, remediation, verification, and deliverables are defined in your engagement scope.

CHOOSING THE RIGHT REPORT

Which VPAT® edition
do you need?

The appropriate edition depends on the requirements your customer, procurement process, or market needs documented. ITI currently provides four VPAT® 2.5Rev editions.

VPAT® WCAGWCAG Edition

COVERSApplicable Web Content Accessibility Guidelines criteria. The current edition can address WCAG 2.0, 2.1, and 2.2.

COMMON FITCustomers requesting WCAG-based accessibility documentation.

VPAT® 508Revised Section 508

COVERSThe Revised Section 508 standards for U.S. federal information and communications technology.

COMMON FITVendors and products involved in U.S. federal procurement.

VPAT® EUEU Edition

COVERSEN 301 549 accessibility requirements for information and communications technology.

COMMON FITProducts needing documentation aligned with applicable European ICT requirements.

VPAT® INTInternational Edition

COVERSThe standards represented by the WCAG, Revised Section 508, and EU editions in a broader report.

COMMON FITProducts serving multiple markets or procurement environments.

ITI editions checked October 4, 2026. View the current templates. For U.S. federal procurement, GSA directs vendors to the Revised Section 508 or International edition. Review the actual solicitation requirements.

Not sure which edition you need?

Share the accessibility request, RFP language, procurement requirement, or customer questionnaire. We can help identify the technical reporting scope. Your procurement or legal team handles contractual and legal interpretation.

Get a Free Review

DELIVERABLES

Clear documentation.
Actual testing behind it.

A report your team can understand and your customers can evaluate, with the scope and evidence that give its findings context.

Accessibility
Conformance Report

Product, version, and evaluation date

  • Evaluation scope
  • Methods and environments
  • Criterion-level findings
  • Remarks and explanations
  • Known limitations
Illustrative report structure
The completed ACR describes the product and requirements included in the evaluation.
  • Accessibility evaluation

    Structured evaluation of the product and functionality in the agreed scope.

  • Testing documentation

    Findings from the applicable automated, manual, keyboard, screen reader, and interaction testing.

  • Criterion-level findings

    Accessibility requirements connected to observed product behavior.

  • Accessibility Conformance Report

    A completed report using the appropriate VPAT® edition and describing the evaluated product.

  • Remediation guidance

    Technical recommendations for accessibility barriers identified during evaluation.

  • Verification

    When remediation is part of the engagement, relevant fixes can be retested before final reporting.

Need help fixing the issues too?
We provide code-level remediation alongside testing and documentation.

Explore Code-Level Remediation

CLEAR CONFORMANCE REPORTING

A useful ACR explains
more than “pass” or “fail.”

The VPAT® reporting structure uses defined terms to describe how the evaluated product supports individual requirements, with space for remarks and explanations.

  • Supports

    A method meets the criterion without known defects, or equivalent facilitation is provided.

  • Partially Supports

    Some functionality supports the criterion, while some does not.

  • Does Not Support

    The majority of the evaluated functionality does not meet the criterion.

  • Not Applicable

    The criterion does not apply to the evaluated product or functionality.

SAMPLE ACR CRITERION2.1.1 Keyboard

Example only

CONFORMANCE LEVEL

Supports

REMARKS & EXPLANATIONS

The evaluated navigation, forms, dialogs, and date-selection workflow can be operated using a keyboard. Testing found no keyboard-only operation barriers in the functionality covered by this criterion.

Illustrative remarks for a hypothetical product. The full evaluation and applicable reporting instructions determine the actual finding.

CONFORMANCE LEVEL

Partially Supports

REMARKS & EXPLANATIONS

Most primary navigation and form controls are keyboard operable. One custom date-picker component does not currently expose all functionality through keyboard interaction.

The remarks identify the specific limitation, instead of leaving the reader to guess what is affected.

CONFORMANCE LEVEL

Does Not Support

REMARKS & EXPLANATIONS

The majority of functionality in the evaluated workspace relies on pointer interaction. Keyboard users cannot operate the primary navigation, open key dialogs, or complete the core scheduling workflow.

The explanation describes affected functionality and the practical impact on the user.

The explanation matters.

Useful remarks show what was tested, where limitations exist, and how the product behaves. These simplified examples demonstrate reporting quality; they are not EqualAccess. client findings.

Use the full definitions and instructions in the applicable ITI VPAT® template.

MORE THAN DOCUMENTATION

Found accessibility issues?
We can help fix them.

An evaluation may uncover barriers your team wants to address before publishing or updating an ACR.

We can remediate agreed issues in the underlying website or application, verify the changes, and update the documentation to reflect the tested product state.

Explore Code-Level Remediation

ONE FINDING, FOLLOWED THROUGH

  • Issue found

    Keyboard interaction fails in a component.

  • Code remediated

    The component’s keyboard behavior is corrected.

  • Fix verified

    Keyboard and assistive-technology behavior are retested.

  • Finding documented

    The ACR reflects the verified product behavior.

Illustrative issue history within the agreed testing and remediation scope.

AN IMPORTANT DISTINCTION

A VPAT® is not an
accessibility certification.

There is no official “VPAT certification.” ITI provides the template; it does not approve or certify individual VPATs or ACRs.

Our role is to help you evaluate accurately, document clearly, and remediate barriers where appropriate. The result is useful accessibility information about the product evaluated.

Read ITI’s explanation of VPAT® reporting.

ACCESSIBILITY CHANGES WITH THE PRODUCT

Your product changes.
Your ACR should keep up.

An ACR describes an evaluated version or state of a product. Significant changes can make older documentation less representative of the current experience.

Bring accessibility into the release and maintenance process so the report stays connected to what customers use.

  • New components
  • Major releases
  • New workflows
  • Design-system changes
  • Third-party integrations
  • Accessibility remediation
Explore Ongoing Monitoring & Support
  1. v3.1

    Evaluate

    Test the product and document the findings.

  2. v3.2

    Review changes

    Identify affected components and report sections.

  3. v4.0

    Retest & update

    Align documentation with the current release.

Illustrative release history. There is no universal update interval; the product changes and reporting needs determine the scope.

STANDARDS & PROCUREMENT

How WCAG and Section 508 fit into the picture.

WCAG

W3C’s Web Content Accessibility Guidelines define testable success criteria at Levels A, AA, and AAA. WCAG is a technical standard; laws or contracts may reference it.

WCAG Compliance & Conformance

Section 508

Section 508 addresses accessibility of ICT developed, procured, maintained, or used by U.S. federal agencies. Vendors commonly use an ACR to document support for the applicable requirements.

Section 508 Compliance

VPAT®

The standardized reporting structure brings applicable requirements and product evaluation results together in an Accessibility Conformance Report.

  1. Accessibility requirements
  2. Product evaluation
  3. VPAT® reporting structure
  4. Accessibility Conformance Report

Official references: W3C WCAG · GSA’s ACR and VPAT FAQ · ITI VPAT®.

VPAT & ACR FAQ

Common questions about accessibility reports.

What the report means, what goes into it, and how to get started.

Talk to EqualAccess.

The VPAT® is the template used to document accessibility conformance. Once it has been completed for a specific product using evaluation results, the resulting document is an Accessibility Conformance Report, or ACR.

Read ITI’s explanation.

Yes. We can evaluate the product, document accessibility findings, and prepare the resulting ACR using the appropriate VPAT® edition.

We start by determining the product, version, functionality, and accessibility requirements to be evaluated.

Yes. The report should reflect the product being documented. Depending on scope, evaluation can include automated testing, manual testing, keyboard testing, screen reader testing, and review of important user journeys.

No. ITI states that there is no VPAT certification and that it does not review or approve individual reports. A completed VPAT® is an ACR documenting the accessibility of the evaluated product.

See ITI’s VPAT® FAQ.

Not necessarily. An ACR documents support for applicable criteria. It may report Supports, Partially Supports, Does Not Support, or Not Applicable, with remarks explaining the evaluated behavior and limitations.

It depends on the requirements you need to document. ITI provides WCAG, Revised Section 508, EU, and International editions. The standards named in your RFP, procurement request, or customer requirement help determine the appropriate edition.

Compare the four editions.

Accessibility documentation is commonly part of federal ICT procurement. GSA’s Section508.gov guidance directs vendors to use the Revised Section 508 or International edition when preparing an ACR using the VPAT® template for federal sales.

Always review the specific solicitation requirements. Read GSA’s guidance.

Yes. We can combine evaluation with code-level remediation and verification. Agreed barriers can be addressed and relevant functionality retested before final documentation.

Explore Code-Level Remediation.

Yes. An ACR documents the actual level of support for the applicable requirements. A product does not need to meet every applicable technical requirement simply for an ACR to exist; the report needs to describe the product accurately.

Read GSA’s ACR FAQ.

Significant changes can affect accessibility and make previous findings less representative of the current product. Retesting and updating the report helps keep documentation aligned with the version customers are using.

Explore Ongoing Monitoring & Support.

NEED A VPAT OR ACR?

Start with the product,
not the paperwork.

Tell us what you are being asked to provide and what product needs evaluation. We will help define the technical scope, test the product, document findings, and prepare clear accessibility information.

Have an RFP, procurement requirement, or existing ACR? Share it with our team when you get in touch so we can understand what you are working with.

VPAT® is a registered service mark of the Information Technology Industry Council.

Opens in a new tab.