The WCAG edition of the VPAT covers conformance to the Web Content Accessibility Guidelines only. The EU edition covers EN 301 549, the European standard that incorporates WCAG and adds requirements for hardware, software, documentation, and support services. The WCAG edition fits products evaluated against the guidelines alone. The EU edition fits products sold into European markets where EN 301 549 applies, including procurement under the EU Web Accessibility Directive and obligations under the European Accessibility Act.
Choosing the right edition depends on where your product is sold, who is buying, and which standard the buyer references in their procurement requirements.
| Attribute | WCAG Edition | EU Edition |
|---|---|---|
| Standard covered | WCAG 2.1 AA or WCAG 2.2 AA | EN 301 549 (includes WCAG plus added clauses) |
| Primary market | Global, default for SaaS | European Union |
| Scope | Web content, software, mobile apps against WCAG | ICT including hardware, software, documentation, support |
| Common buyers | U.S. enterprise, private sector procurement | EU public sector, EAA-regulated companies |
| Length | Shorter, focused tables | Longer, additional EN clauses included |
What the WCAG Edition Covers
The WCAG edition of the VPAT documents conformance to the Web Content Accessibility Guidelines at a stated level, typically 2.1 AA or 2.2 AA. The tables map each success criterion against the product and record a conformance level: Supports, Partially Supports, Does Not Support, or Not Applicable. Each finding includes remarks that explain the result.
This edition is the default for most SaaS companies. When a U.S. enterprise buyer requests an ACR, they almost always want the WCAG edition. The document gives procurement teams a clean read on how the product performs against the guidelines without extra clauses they will not evaluate.
What the EU Edition Covers
The EU edition documents conformance to EN 301 549, the European harmonized standard for ICT accessibility. EN 301 549 incorporates WCAG by reference, so the WCAG criteria appear in the EU edition as well. The added value is everything that surrounds the web content portion.
EN 301 549 covers hardware features, two-way voice communication, video capabilities, documentation, support services, and other ICT considerations beyond web content alone. Even when most clauses do not apply to a SaaS product, the EU edition records that determination clearly, which is what European buyers expect.
Which Edition Should You Choose?
The choice maps to the buyer and the market. If your customers are in the United States and your product is web-based or SaaS, the WCAG edition almost always fits. If your customers are EU public sector entities, or if your company falls under the European Accessibility Act, the EU edition is the right pick.
Some companies issue both editions when they sell into multiple regions. The underlying evaluation is the same, since EN 301 549 references WCAG, but the documents serve different procurement audiences. Producing both editions from a single audit is simple when the audit was scoped to capture the relevant data.
How the Audit Connects to the ACR
An ACR is only as credible as the audit behind it. A fully manual evaluation against WCAG 2.1 AA or 2.2 AA identifies the issues that populate every conformance entry in the report. Without that audit data, the document is guesswork.
Accessible.org conducts manual audits and produces the resulting ACR using the appropriate edition for the client’s market. For a SaaS company entering EU procurement for the first time, this often means starting with a WCAG 2.1 AA audit and then mapping the results into the EU edition to cover the EN 301 549 clauses that apply.
Common Mistakes When Picking an Edition
The most frequent error is defaulting to the INT edition because it covers everything. The INT edition combines WCAG, Section 508, and EN 301 549 into one document. It looks thorough on the surface, but most buyers do not want a document padded with clauses they will not read.
A second error is selecting the EU edition for U.S. buyers who only want WCAG conformance documented. The extra clauses create noise. A focused document reads better and gives procurement what they actually need.
Frequently Asked Questions
Do I need both the WCAG and EU editions for my product?
Only if you sell into both U.S. and EU markets and your buyers in each region request the matching edition. Many companies start with the WCAG edition and add the EU edition when European procurement opportunities come up.
Is the EU edition required for EAA compliance?
The European Accessibility Act does not mandate a specific document, but the EU edition is the natural fit because it documents conformance to EN 301 549, the harmonized standard used to demonstrate EAA compliance for in-scope products.
Does the EU edition cost more than the WCAG edition?
The audit work driving the document is similar when the product is web-based, since EN 301 549 references WCAG. The EU edition can take a bit more time to fill in due to the added clauses, but the cost difference is typically modest.
Can the same audit support both editions?
Yes. A manual WCAG audit produces the conformance data needed for both editions. The EU edition adds clauses that often resolve to Not Applicable for SaaS products, which the auditor records during the evaluation.
The right edition is the one your buyer expects to receive. Match the document to the market, anchor it to a manual audit, and the ACR will do its job.
Contact Accessible.org to discuss which VPAT edition fits your product: Contact Accessible.org.
