Wholesale Buyers Now Ask for a VPAT. Is Your Portal Ready?
Picture a wholesale deal that is two weeks from signature. The buyer's procurement team sends a vendor questionnaire, and line 14 reads: "Attach your Accessibility Conformance Report." Nobody on your side knows what that is. The deal waits while someone searches for a template and guesses at the answers.
For B2B and wholesale brands, that moment is arriving more often. This article explains what buyers are actually asking for, why the ask is growing, and what it takes to answer it with something that holds up.
What is a VPAT, and what is an ACR?
Answer in brief: A VPAT (Voluntary Product Accessibility Template) is the standard form, published by the Information Technology Industry Council, that vendors fill in to describe how well a product meets accessibility standards such as WCAG. The completed document is called an Accessibility Conformance Report (ACR). It records, criterion by criterion, whether the product supports, partially supports, or does not support each requirement. It is a disclosure, not a certification.
That last point matters. An ACR is not a pass/fail badge. It is a structured statement of where your storefront or portal stands, and the buyer's team will read it as a statement of fact.
Why wholesale buyers are asking now
Two developments make this a live issue rather than a niche one.
Proof of accessibility is becoming a purchasing requirement. Level Access, citing the State of Digital Accessibility Report in an August 4, 2026 guide, reports that 75% of professionals say their organization requires proof of accessibility at least most of the time when buying digital products, and 31% say it is required for every purchase. Those respondents are buyers of digital products broadly, not only ecommerce, so treat the figures as a direction of travel for B2B procurement, not a measurement of wholesale specifically.
Public-sector deadlines are getting closer. On April 20, 2026, the Department of Justice issued an interim final rule that moved the ADA Title II web accessibility deadlines by one year, according to law-firm summaries of the rule. Public entities serving a population of 50,000 or more now have until April 26, 2027, and smaller entities until April 26, 2028. The standard is still WCAG 2.1 Level AA, and the rule covers digital content provided directly or through contractors. School districts, universities, and municipalities that buy supplies through supplier portals are exactly the buyers who will start sending accessibility questions to vendors.
Neither development makes your portal a Title II entity. What they do is raise the odds that a buyer's compliance team asks you for evidence.
Where self-written ACRs go wrong
Because vendors complete their own ACRs, quality varies widely. WebAIM's guidance on procurement lists the failure patterns buyers are taught to look for:
- Evaluation methods listed as "general product knowledge," which signals that no real testing happened.
- A "Supports" rating with no implementation detail behind it.
- A report that does not match the version of the product being sold, or is simply old.
- A sales contact listed where a technical contact should be.
- Empty remarks on criteria, even where the rating is "Supports."
A sophisticated buyer will follow up on every one of these. The risk for the vendor is not only a stalled deal. An ACR that says "Supports" for a criterion your portal fails, such as keyboard access to the bulk-order form, becomes a documented misstatement. A candid "Partially Supports" with a remediation plan is stronger than a confident claim that testing later disproves.
What a defensible ACR needs for a B2B portal
An honest report starts with an honest scope. For a wholesale portal, that means testing the flows buyers actually use, not just the homepage.
Scope the real buying flows
Account login and password reset, catalog search and filtering, quick-order and CSV bulk upload, reorder from history, quote requests, checkout with payment terms, and downloadable invoices and statements. Dense data tables, multi-line order forms, and date pickers are where accessibility defects tend to concentrate, because they are custom-built and keyboard behavior is easy to get wrong.
Test with more than a scanner
Automated tools catch only part of what WCAG requires. A credible report combines automated scans with keyboard-only testing and screen reader passes, and it names the tools and assistive technologies used. That specificity is what separates an ACR from a marketing document.
Choose the standard deliberately
The WCAG edition of the VPAT covers WCAG 2.0, 2.1, and 2.2. Most public-sector references still point to WCAG 2.1 AA, while WCAG 2.2 adds criteria such as target size and accessible authentication that affect login and form-heavy B2B flows. Reporting against 2.2 is the safer long-term choice.
Name an owner and a refresh date
Buyers want a technical contact who can answer follow-up questions, and a report dated recently enough to match the live product. The ACR should be updated when the platform changes materially.
Fix the system, then write the report
The report is a symptom of the engineering underneath it. Overlay widgets do not change the code buyers' testers inspect, and patching pages one at a time does not survive the next release.
MnT Future treats accessibility as a design-system problem. In our own WCAG 2.x AA remediation, we took seven failing checks to zero, measured with axe-core across nine key pages, by fixing shared components: contrast tokens, form labels, a modal keyboard trap, heading structure, and focus handling. We used no overlay widgets. Automated measurement does not cover every WCAG criterion, so manual testing remains part of the process, but fixing at the component level is what keeps a clean result clean as the catalog and portal grow.
For a wholesale portal, the same principle applies: once the table, form, and modal components are accessible, every new page built from them inherits that work, and the ACR becomes something you can update in an afternoon rather than rebuild under deadline pressure. See how we approach B2B and wholesale commerce platforms.
Frequently asked questions
Is a VPAT legally required for an ecommerce site?
No. It is a voluntary template. It becomes a practical requirement when a buyer's procurement process asks for it.
Does an ACR protect us from an ADA lawsuit?
No. It documents conformance; it does not confer immunity, and an inaccurate one can create additional exposure.
Who should write it?
Ideally the team that can test and fix the product, with an independent review where the stakes are high.
Next step
If a buyer has asked for an ACR, or you expect one, start with a clear view of where your portal stands. MnT Future offers a free strategy session in which senior engineers walk through your buying flows, flag the likely accessibility gaps, and outline what it would take to make the report you hand over accurate.