WCAG Audit, EN 301 549 Test, or VPAT: Which Accessibility Request Belongs to Which Service?
Route an incomplete accessibility request by its required output: web-content findings, European ICT test evidence, or an Accessibility Conformance Report created with a VPAT.
Signals to watch
- The request names an asset, procurement route or standard instead of asking for accessibility in general
- The buyer can identify whether it needs findings, conformity evidence or a procurement-facing report
- A tender, renewal, release or customer review gives the output an owner and date
“Need a VPAT before renewal” does not yet identify the service. Work backward from who will receive the document and the procurement clause they must answer, then freeze the product version and inspect available evidence. That sequence reveals whether the supplier must test web content against WCAG, evaluate applicable EN 301 549 requirements, produce an Accessibility Conformance Report using a VPAT, or combine those tasks.
This is the decision facing an accessibility-services channel director reviewing authorized procurement, SaaS-partner and public-sector supplier Telegram groups. A day of delay can miss a tender clarification or renewal review. A generic same-day quote can be worse: it may promise a report for the wrong product version or treat last year’s website scan as evidence for a changed admin console.
The messages below are illustrative composites, not customer messages, a real tender or a commercial result.
09:10 — the request names a document, not its evidence
“Need VPAT for our portal before renewal. Anyone available?”
The post provides a familiar acronym, a product label and a deadline event. It does not identify the buyer, jurisdiction, procurement clause, portal version, user surfaces, target criteria, existing tests, remediation expectation or person who will sign off.
VPAT stands for Voluntary Product Accessibility Template. It is a reporting template, not a test standard or certification. Section508.gov describes how a vendor can use a VPAT to create an Accessibility Conformance Report (ACR), a document explaining how an information and communication technology product conforms to accessibility requirements. The completed ACR is what a procurement reviewer evaluates; the blank template does not create supporting evidence.
The channel director therefore replies with two questions before discussing price: “Who requested the report?” and “Which requirement or VPAT edition did they specify?”
09:35 — the recipient exposes why the document exists
The sender answers:
“US customer sent the form. Their vendor review closes Friday. I think it says WCAG 2.2, but we only tested the public site last year.”
Now the likely output is procurement-facing, but the asset and evidence still do not align. A contracting official or enterprise buyer may need an ACR. A product owner preparing remediation usually needs traceable findings. A European public-sector procurement team may instead request evidence against applicable EN 301 549 clauses. The recipient does not determine scope by itself, but it reveals the decision the output must support.
The European Accessibility Act supplier-demand article explains why a general law mention is not yet a defined deliverable. Here, the named form and Friday review make the request more concrete, while the exact clause and edition remain unknown.
10:20 — freeze the product before counting evidence
The team learns that “portal” includes a public website, an authenticated admin console and PDF support documents. The admin console changed two months ago. The previous review covered only the public site.
That version boundary matters because WCAG 2.2 is a W3C Recommendation organised around principles, guidelines and testable success criteria at levels A, AA and AAA. A WCAG evaluation can produce web-content findings for a defined website or web-app release. Depending on scope, it may combine automated checks, manual expert review and testing with assistive technologies or disabled users. An automated score alone is not a conformance determination.
The old report may still support unchanged public pages. It cannot automatically support a changed admin console or new documents. Before reusing any finding, record the current build, included journeys, target level, test method and evidence date.
This is also where a seemingly simple ACR-writing job can turn into testing work: the report cannot honestly describe surfaces that nobody evaluated.
11:40 — one procurement clause changes the test boundary
Suppose the form names a U.S. procurement requirement and the relevant VPAT edition. The supplier can map valid WCAG evidence, test uncovered web surfaces and document each conformance statement in the ACR. “Supports,” “partially supports,” “does not support” and “not applicable” entries need accurate remarks and evidence; missing evidence stays visible until it is produced.
If the buyer instead sends a European public-sector tender naming EN 301 549, the route changes. The European Commission’s web-accessibility page states that EU public-sector website and app requirements are underpinned by harmonised standard EN 301 549 v3.2.1. It includes web requirements and other information and communication technology dimensions beyond a webpage.
A SaaS interface may reuse relevant WCAG test evidence while documentation, support or other applicable ICT requirements still need review. Hardware and communications products can extend further beyond web content. The exact legal or procurement basis, standard edition and applicable clauses must be confirmed rather than inferred from “EU customer.”
14:00 — write the scope as a chain, not an acronym
By the afternoon, the routing note should connect five records:
- the recipient and decision date;
- the procurement clause, jurisdiction and requested report;
- the exact product, version and included surfaces;
- reusable test evidence and its date; and
- uncovered criteria, new testing, remediation or documentation work.
For the composite request, a defensible scope might be: preserve valid public-site findings, test the changed admin console and new support documents against the applicable criteria, then use the selected VPAT edition to prepare an ACR for Friday’s vendor review. If the buyer names EN 301 549, replace that assumption with a clause-level scope before estimating effort. If the buyer only wants checkout-flow failures against WCAG 2.2 AA, do not sell a procurement report they did not request.
TOP Prospect can connect incomplete fragments from authorized groups, retain source and time, remove clear duplicates and rank the candidate for human review. It cannot determine the applicable standard, test a private product, author unsupported conformance claims or contact the writer.
When the original requirement has been forwarded without its form or clause, use the official-source recovery method. If the post has only an acronym and no recipient, asset or date, separate topical relevance from buying intent before treating it as a service request.
The route is ready when the note can say: “This buyer needs this output for this decision; it covers this product version; these findings already support it; these gaps still require testing or documentation.” That sentence scopes the work without pretending WCAG, EN 301 549 and VPAT are three names for the same service.
Frequently asked questions
Is WCAG the same as EN 301 549?
No. WCAG is a W3C recommendation containing testable success criteria for web content. EN 301 549 is a European ICT accessibility standard with requirements that include web content and other ICT dimensions.
Is a VPAT a test standard?
No. A Voluntary Product Accessibility Template is a reporting template. When completed to describe how a product meets applicable accessibility requirements, the resulting document is commonly called an Accessibility Conformance Report.
Can an existing WCAG audit be copied into a VPAT?
Not automatically. The report must address the applicable criteria, product scope and procurement requirement, and each conformance statement needs adequate evidence. Gaps may require additional testing.
What should sales verify before quoting an accessibility request?
Verify the asset and version, buyer jurisdiction and procurement clause, requested output, applicable standard or edition, testing depth, existing evidence, remediation scope, document owner and decision date.
