← Accessibility Insights & Resources

What Is a VPAT / ACR, and Who Needs One?

The difference between a VPAT and an ACR, the four editions, what "Partially Supports" really means, and how to tell whether you need one at all.

See our VPAT and ACR service

A VPAT is a blank form. The Voluntary Product Accessibility Template (VPAT®) is published by the Information Technology Industry Council (ITI). When you fill it in for a specific product, the finished document is called an Accessibility Conformance Report, or ACR. It lists each accessibility requirement in a standard such as WCAG and states how well your product meets it.

People use the two names loosely. When a buyer says "send us your VPAT", they mean the completed report, the ACR.

You need one when a customer asks for it. That is most often a government body, university, hospital or large company buying software or another digital product. If you run an ordinary business website and nobody is procuring it from you, you almost certainly don't need a VPAT. You may still need an accessibility audit, which is a different thing. Both are covered below.

VPAT vs. ACR: the difference

VPAT and ACR compared
QuestionVPATACR
What it isThe empty template, with instructionsThe template completed for one product
Who writes itITIThe vendor, or a tester working for the vendor
What it tells youNothing about any productHow one version of one product meets each criterion
CostFree to downloadThe cost of the testing and writing behind it

ITI describes the VPAT on its VPAT page as a tool that helps companies explain how their information and communication technology products support accessibility standards. The template is free, and you don't need to be an ITI member to use it.

An ACR is not a certification

This is the most common misunderstanding. ITI says plainly that there is no official VPAT or ACR certification, approval or pass/fail rating, and that it does not review or approve completed reports. An ACR is the vendor's own statement about its own product.

The word "voluntary" in the name means the same thing: no law makes you publish one. In practice, a buyer can make it a condition of doing business with them, and many do.

The four VPAT editions

The current version is VPAT 2.5Rev, released in April 2025. It comes in four editions. Each one measures the product against a different standard, so the edition you choose depends on who is buying.

The four editions of VPAT 2.5Rev and the standards each one includes, as listed by ITI
EditionStandards includedWho usually asks for it
WCAGWCAG 2.0, 2.1 and 2.2Most private-sector buyers, Ontario organizations, universities
508The US Revised Section 508 standards, with WCAG 2.0US federal agencies, and many US state governments and colleges
EU (EN 301 549)The European standard EN 301 549, with WCAG 2.0 and 2.1Buyers in the EU, and Canadian federal buyers
INT (International)All of the above in one reportVendors selling into several markets at once

A few things follow from this table.

  • The WCAG edition lets you choose the version. You report on WCAG 2.0, 2.1 or 2.2, and on Level A, AA or AAA, and the report must say which. Check what the buyer named. Our comparison of WCAG 2.0, 2.1 and 2.2 explains what each version adds.
  • The 508 and EU editions cover more than web pages. Section 508 has chapters for software and support documentation. EN 301 549 has clauses for web, non-web documents, software, and documentation and support services. A desktop app or a PDF user guide can be in scope.
  • EN 301 549 matters in Canada. In May 2024 Accessibility Standards Canada published CAN/ASC-EN 301 549:2024, an identical adoption of the 2021 European standard. It is a voluntary standard, but federal buyers refer to it.
  • If you aren't sure, ask. The buyer's solicitation should name the standard. If it doesn't, ask them before you commission the report.

The conformance levels and what they mean

Every row of an ACR has a criterion, a conformance level and a remark. The conformance level is one of five terms. These are ITI's own definitions, taken from the instructions in the VPAT 2.5Rev template.

ITI's conformance level terms in VPAT 2.5Rev
TermITI's definition
Supports The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially SupportsSome functionality of the product does not meet the criterion.
Does Not SupportThe majority of product functionality does not meet the criterion.
Not ApplicableThe criterion is not relevant to the product.
Not Evaluated The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

Three points are worth knowing before you write or read one.

  • "Partially Supports" is a wide band. It covers everything from one low-contrast label to a third of the product being unusable by keyboard. The term alone tells you very little. The remark beside it is what matters.
  • "Not Evaluated" is only allowed for Level AAA. A vendor can't use it to skip a Level A or AA criterion it didn't get around to testing.
  • Remarks are expected when something falls short. For "Partially Supports" and "Does Not Support", ITI's instructions say the remarks should identify the functions or features with issues and how they fall short. If a criterion doesn't apply, the remark should say why.

A vendor may use its own definitions for these terms, but ITI requires the report to list the definitions it uses and to flag any change from ITI's wording in the Notes section. If the terms in a report look unfamiliar, check there.

Who asks for a VPAT or ACR

Buyers ask, not regulators. An ACR is a procurement document: it lets a buyer compare products and understand the accessibility risk before signing. ITI's own description is that it helps buyers make a preliminary assessment.

US federal buyers

The US government's Section 508 guidance for vendors recommends that vendors generate an ACR for any technology they intend to market to the federal government.

Canadian federal buyers

The Government of Canada's guide to accessibility in ICT procurement tells departments to require suppliers to submit an ACR, and recommends the ITI template. It prefers a report prepared by a third party with professional accessibility testing expertise, or by the supplier's own experienced in-house specialists. The guide describes EN 301 549 as not yet mandatory for the Government of Canada while strongly encouraging its use, so expect to see it in federal solicitations.

Ontario's public sector

Section 5 of Ontario's Integrated Accessibility Standards Regulation requires the Government of Ontario, the Legislative Assembly and designated public sector organizations to incorporate accessibility design, criteria and features when procuring or acquiring goods, services or facilities, except where it isn't practicable. The regulation doesn't mention VPATs or ACRs by name. An ACR is simply one of the easiest ways for a municipality, hospital, college or university to show it considered accessibility, so many of them ask for one.

Enterprises and everyone else

Large private companies often have their own accessibility policies for the tools their staff and customers use, and their procurement or vendor-risk teams ask for an ACR alongside security questionnaires. Buyers in the EU typically ask for the EN 301 549 edition.

If a request has just landed on your desk as part of a tender, our guide to accessibility requirements in RFPs covers the other things buyers usually ask for at the same time. This is general information, not legal advice.

Do I need a VPAT?

Usually the answer is one of these.

  • You sell software, a SaaS product, an app or hardware to public-sector or enterprise buyers: yes, or you will soon. Having a current ACR ready saves weeks when a tender arrives.
  • A customer has asked for one: yes. Find out which edition and which WCAG version they want.
  • You run a business website and want to meet the AODA: no. The AODA website rule requires your site to meet WCAG 2.0 Level AA. It doesn't require a VPAT or an ACR. What helps you is an audit and fixes; see what a website accessibility audit is and our AODA requirements guide.
  • You want something to show visitors: that is an accessibility statement, not an ACR. See how to write an accessibility statement.

An ACR written from a real audit

We test your product by hand and with assistive technology, then write your ACR on the ITI template in the edition your buyer asked for.

See the VPAT and ACR service

Why an ACR should be based on an audit

Anyone can download the template and type "Supports" into every row. Nothing stops them, because nobody certifies the result. That is exactly why buyers look at how the report was produced.

The template has a required field called "Evaluation Methods Used". ITI's best-practice notes suggest describing the testing done with assistive technologies and with manual and automated tools, and naming any published test method. A report where that field is empty or vague gives a buyer no reason to trust the rows below it.

An audit is what fills those rows honestly. Many WCAG criteria can't be judged by a scanner: whether alt text makes sense, whether focus order is logical, whether a screen reader user can finish a task. Someone has to test them. Our article on automated vs. manual accessibility testing explains where each fits.

There is also a practical reason. Buyers sometimes test the product themselves and compare the result with your ACR. If they find a keyboard trap on a criterion you marked "Supports", every other row is now in doubt. An accurate "Partially Supports" with a clear remark is a much safer answer than an optimistic "Supports".

At CodexMotive we only write ACRs from audits we ran ourselves, and the audit and the report are sold together. Our pricing page shows what's included.

How to read an ACR

If you're the buyer, or you're checking a report someone wrote for you, read it in this order.

  1. Product name and version. Does it match what you're buying or selling today? An ACR describes one version of one product.
  2. Report date. ITI requires at least the month and year. Compare it with the product's release history.
  3. Template version. The report should say which VPAT version it is based on, such as 2.5Rev. A very old template version suggests the report hasn't been touched in years.
  4. Applicable standards. Which standards, which WCAG version and which level does the report cover? A report on WCAG 2.0 doesn't answer a WCAG 2.2 requirement.
  5. Evaluation methods. Who tested, how, and with which assistive technologies and tools?
  6. Notes. Look for what was left out: modules not tested, platforms excluded, or a second report covering another part of the product.
  7. The tables. Go straight to every row that isn't "Supports" and read the remark. Then ask whether the affected feature matters to your users.

Signs of a weak report

  • Every row says "Supports" and there are no remarks.
  • "Partially Supports" with a remark like "some minor issues may exist".
  • "Not Applicable" on criteria that clearly apply, such as captions for a product with video.
  • "Not Evaluated" on Level A or AA criteria.
  • No evaluation methods, no product version, or no date.
  • The remarks credit an overlay or widget for conformance.

One detail that looks odd but isn't: in the WCAG tables, a report may say "Supports" where you might expect "Not Applicable". ITI's instructions allow this, because under WCAG a criterion is satisfied when the product has no content it applies to. A good report explains this in the remark, for example "The product contains no audio or video content."

An ACR is a summary. It says which criteria have problems, not where each problem is or how to fix it. That detail lives in the audit report behind it; our guide on how to read an accessibility audit report covers that document.

How often to update an ACR

An ACR has no expiry date. ITI's guidance is to review or update it when the product changes in ways that could affect accessibility, and when the relevant standards or requirements change.

In practice, plan an update when:

  • you ship a major release, a redesign or a new module;
  • you fix issues the current report lists, so the report can show the improvement;
  • a buyer asks for a newer WCAG version or a different edition;
  • ITI releases a new template version and buyers start asking for "the latest VPAT";
  • a contract sets a schedule. Some buyers write an update interval into the agreement.

If nothing has triggered an update, we suggest reviewing the report once a year anyway. Products change in small ways that add up, and a report dated two or three years ago invites questions.

When you revise a report, ITI's best practice is to change the report date and explain the revision in the Notes section, or to publish a new report that says it replaces the old one.

Common VPAT mistakes

  • Filling it in without testing. The most common mistake, and the one buyers find fastest.
  • Using the wrong edition. Sending a WCAG edition to a buyer who asked for Section 508 or EN 301 549 means doing the work twice.
  • Reporting on the wrong WCAG version. The buyer asked for 2.2 and the report stops at 2.1.
  • Calling it a certification. Phrases like "VPAT certified" or "VPAT compliant" on a sales page are a warning sign to anyone who knows what the document is.
  • Hiding failures. Marking things "Not Applicable" or writing vague remarks to avoid admitting a gap.
  • Leaving the instructions in. The template opens with about ten pages of instructions for authors. ITI tells you to remove them before publishing.
  • Publishing an inaccessible report. ITI requires the final conformance report itself to be accessible. A scanned PDF of an accessibility report makes a poor first impression.
  • Covering only part of the product. The web app is tested but the mobile app, the admin area or the documentation isn't, and the report doesn't say so.
  • No plan for the gaps. Buyers accept gaps more readily when they come with dates. A short remediation plan beside the ACR answers the obvious next question.

Frequently asked questions

What does VPAT stand for?

Voluntary Product Accessibility Template. It is a template published by the Information Technology Industry Council (ITI). The completed version for a specific product is called an Accessibility Conformance Report (ACR).

Is a VPAT legally required?

No law requires a business to publish one, and the AODA doesn't mention it. A buyer can require it as a condition of a contract or tender, which is why most vendors end up needing one.

Can we fill in the VPAT ourselves?

Yes. ITI doesn't require a third party, and says the company that knows the product best is generally best placed to complete it. But a buyer may ask for an independent review, and any report is only as good as the testing behind it. If your team hasn't tested with a keyboard and screen readers, the report will be guesswork.

Which VPAT edition do I need?

The one that matches the standard your buyer named: WCAG for most private-sector and Ontario buyers, 508 for US federal buyers, EU for EN 301 549, or INT if you need all three. If the request doesn't say, ask the buyer.

Does "Partially Supports" mean we fail?

No. An ACR has no pass or fail. "Partially Supports" means some functionality doesn't meet the criterion. Most real products have some of these rows. What the buyer judges is the remark: what fails, how serious it is, and whether there is a plan to fix it.

Does my website need a VPAT to comply with the AODA?

No. The AODA requires covered organizations to make their websites meet WCAG 2.0 Level AA. It doesn't ask for a VPAT or ACR. Those are for products being sold to buyers who request them.