Same Complaint, Two Very Different Conversations
Two companies receive the exact same accessibility complaint in the same month — a customer who couldn't complete checkout using a screen reader. One company has a published accessibility statement in its footer, describing an active remediation roadmap and a clear channel for reporting exactly this kind of issue. The other has nothing — no statement, no visible commitment, no obvious way the complaint was even going to reach the right person before this email arrived.
The underlying technical failure might be identical in both cases. But how each conversation unfolds from that first email is not remotely the same. One company can point to a documented, ongoing process. The other is starting the conversation from zero, with nothing on record showing they'd thought about accessibility at all before the complaint landed.
That difference is what an accessibility statement is actually for. It's worth being precise about what it is, what it isn't, and how it differs from the other document this space produces constantly: the VPAT.
What an Accessibility Statement Actually Is
An accessibility statement is a public-facing page — commonly linked from a site's footer, alongside the privacy policy and terms of service — that describes an organization's commitment to accessibility, the specific standard it targets, any known limitations, and a clear way for a visitor to report a barrier they encounter.
A genuine, useful accessibility statement includes several specific elements:
- A specific conformance target. "WCAG 2.1 Level AA," not a vague "we care about accessibility for all users." Specificity is what makes the statement meaningful rather than decorative.
- An honest note on known limitations. Every real site has some gap — a legacy PDF library that hasn't been remediated yet, a third-party embedded widget outside your direct control. Naming these specifically is not a liability; a vague, sweeping claim of full compliance with no caveats is the actual legal exposure if it turns out not to be true.
- The date it was last reviewed or updated. A statement dated three years ago, describing a product that's changed substantially since, reads as abandoned rather than active.
- A working contact method. An email address, phone number, or accessible contact form that lets someone report a specific barrier and reasonably expect a response.
What a VPAT Is — and Why It's a Different Document Entirely
A VPAT (Voluntary Product Accessibility Template) is a more technical, more structured document: a criterion-by-criterion report of how a specific product conforms to Section 508, WCAG, or EN 301 549, typically used in B2B and government procurement contexts. (Our Section 508 article covers this in more depth.) Once a VPAT is actually completed with real findings, it's often referred to as an ACR — an Accessibility Conformance Report.
The two documents differ in audience and purpose, not just in level of detail. An accessibility statement is written for any visitor to the site — a consumer-facing trust and transparency signal. A VPAT/ACR is written for a specific enterprise or government buyer, typically requested directly during a sales process or RFP response, and it walks through individual success criteria in a level of technical detail a general site visitor has no use for and would likely never read.
Publishing a public accessibility statement doesn't substitute for having a VPAT ready if your buyers are enterprise or government procurement teams — and completing a VPAT for procurement doesn't substitute for having a public accessibility statement if your buyers are individual consumers. Most organizations that sell into both markets eventually need both documents, serving two different readers.
Is a Statement Legally Required?
For private U.S. businesses, publishing an accessibility statement is not itself a legal requirement under ADA Title III — there's no specific statute mandating the statement document itself, distinct from the underlying accessibility obligation. But it functions as something valuable regardless: concrete, dated evidence of an active, good-faith remediation effort. That's directly relevant context if a demand letter or lawsuit ever arrives, and it's directly relevant in any settlement negotiation that follows — a documented, ongoing process reads very differently to opposing counsel than an organization that visibly did nothing until a complaint forced the issue.
The picture is different for EU-facing organizations in certain sectors. Public-sector bodies operating under the EU Web Accessibility Directive — a related but separate instrument from the European Accessibility Act — have an explicit legal requirement to publish an accessibility statement in a specific, prescribed format, including a feedback mechanism and a link to the relevant enforcement procedure. If your organization falls under that directive's scope, the statement isn't optional best practice; it's a compliance requirement with its own format rules.
The One Rule That Matters More Than Any Template
Don't publish a statement claiming full conformance unless a real, recent audit actually supports that claim. This is worth stating plainly because the instinct under time pressure is often to write the most reassuring version of the statement rather than the most accurate one. An inaccurate accessibility statement is arguably worse than having no statement at all, because it functions as a specific, disprovable representation — a plaintiff's attorney or a regulator doesn't need to prove your site is inaccessible in the abstract; they only need to show your published claim of "full WCAG 2.1 AA conformance" doesn't match reality, which is a much narrower and easier case to make.
The safer, more durable approach is to describe the real current state honestly: the standard you're actually targeting, the specific limitations you're aware of, and the real ongoing process for closing the remaining gaps. Update the statement's date whenever a meaningful remediation milestone is actually reached, not on an arbitrary schedule disconnected from real progress.
Who Should Own Each Document
In practice, these two documents tend to have different owners inside an organization, which is part of why they're easy to conflate or let fall out of sync with each other. The accessibility statement is usually a marketing, content, or legal-adjacent deliverable — written in plain language, reviewed for tone as much as accuracy, and published to the public site. The VPAT is usually owned by a product, engineering, or sales-engineering function, since completing it accurately requires someone who actually understands the product's technical implementation well enough to state, criterion by criterion, what does and doesn't work.
Keeping both documents current requires someone on the team to actually own that responsibility, rather than treating either one as a "publish once and forget" deliverable. A product that's changed meaningfully since its VPAT was last completed — new features, a redesigned checkout flow, a new third-party widget — should have that VPAT revisited before it's handed to the next procurement team, not recycled unchanged from the last sales cycle. The same logic applies to the public statement: if the site's actual conformance level has changed since the statement was last reviewed, the statement should reflect that, not sit untouched for years while the product underneath it evolves.
Get the Underlying Work Right First
Both documents — the statement and the VPAT — are only as trustworthy as the audit work behind them. A statement built on an assumption of compliance, rather than actual testing, is a liability with a publish date attached. A VPAT filled out from a template rather than real criterion-by-criterion testing creates the same risk in a procurement context, just with a different audience finding out later.
If you're about to publish an accessibility statement or complete a VPAT and aren't confident the underlying claim is actually true yet, get a real audit first — a statement that accurately describes where you stand today is worth more than one that describes where you hope to be.