Quick Answer
An accessibility statement is a public document that explains what an organization is doing to support digital accessibility, which standard applies, what accessibility limitations remain, and how someone can get help or report a problem. It helps users know what to expect before they run into trouble, not just after. It does not, on its own, prove legal compliance or full accessibility.
Introduction
An accessibility statement can be treated as a compliance requirement or formal document, but its value depends on whether the information remains accurate and useful to users.
A good accessibility statement does something more useful. It should give users clear and current information about accessibility, including known limitations, available alternatives, and how to report barriers. Done well, it functions closer to a practical resource than a formality.
Whether an organization is required to have one at all depends on where it operates and who it serves. Some organizations are legally obligated to publish one with specific content. For others, requirements vary by jurisdiction, sector, and other applicable obligations.
This guide covers what an accessibility statement actually is, who is required to have one, what it should include, how to write one without overstating anything, and the mistakes that undermine an otherwise useful document.
What Is an Accessibility Statement?
What it's actually for
An accessibility statement communicates current, specific information: which accessibility standard or requirements apply and what conformance status has been established, what measures have actually been taken, what barriers are still known to exist, and how to report a new one. For people with disabilities using different assistive technologies or interaction methods, such as screen readers, switch controls, or keyboard-only navigation, a clear statement can save real time, confirming quickly whether a known issue is already on record.
What it is not
An accessibility statement is not proof that a product is accessible, and it is not the same thing as a formal conformance report. A company can publish a well-written, honest statement and still have real accessibility problems; the statement's role is to disclose that honestly, not to resolve it. It's also worth being precise about two related but different documents. An Accessibility Conformance Report, or ACR, provides more detailed information about how a product conforms to a specific accessibility standard.
A VPAT is a template used to prepare an ACR, not the underlying technical evidence itself. Supporting evidence can include test results, evaluation reports, and manual or automated testing findings. An accessibility statement is the public-facing document; an ACR is the more detailed technical report, and a VPAT is the template commonly used to prepare one.
Who Is Required to Have an Accessibility Statement?
EU public sector bodies
For public sector bodies in the EU, this isn't optional. Directive (EU) 2016/2102, the Web Accessibility Directive, states in Article 7 that member states must ensure public sector bodies "provide and regularly update a detailed, comprehensive and clear accessibility statement" covering their websites and mobile apps. The Directive requires the statement to explain which content is not accessible and why, identify accessible alternatives where appropriate, provide a working feedback mechanism, and include information about the applicable enforcement procedure. A related European Commission decision encourages public sector bodies to review and update their statements regularly, and at least annually, and recommends making the statement reachable from every page of the site.
U.S. federal agencies
In the United States, OMB Memorandum M-24-08, issued in December 2023, requires federal agencies to maintain a digital accessibility statement on their websites, covering the accessibility standard applied, known limitations, information about compatibility with assistive technology, and a public feedback mechanism.
What about other organizations
Outside EU public sector bodies and U.S. federal agencies specifically, requirements vary by jurisdiction, sector, and other applicable obligations. Some organizations have obligations under other laws or sector-specific rules. Some publish a statement because a procurement process or a client asks for one directly.
What Should an Accessibility Statement Include?
W3C's guidance on developing an accessibility statement, along with its free generator tool, lays out a structure worth following even if an organization doesn't use the generator itself.
- Basic information and scope. The organization's name, and exactly which website, app, or service the statement covers. A statement covering only the main website shouldn't be read as also covering a separate mobile app.
- Accessibility standard and conformance status. The applicable accessibility standard, such as a specific WCAG version and conformance level, and an honest conformance status, such as fully conformant, partially conformant, non-conformant, or not assessed. W3C's own generator makes this distinction explicit rather than treating conformance as a single yes-or-no answer.
- Accessibility measures and evaluation approach. What the organization has actually done, built into procurement practices, staff training, an appointed accessibility lead, and how the current state was actually checked, an internal review, external testing, or both.
- Known limitations and alternatives. This is an important part of an honest accessibility statement. For each known issue, it helps to say what the barrier is, where it shows up, why it exists if that's known, and what a user can do in the meantime. A vague line like "some parts of our site may not be fully accessible" tells a user little.
Something like "our PDF reports are not yet fully accessible to people using screen readers; contact support for an accessible version while a fix is in progress" gives someone a real path forward. Writing the statement in plain language, rather than relying on WCAG success criterion terminology, helps users understand what it actually means for their own experience. - Feedback and contact information. A real way to report a problem, and an indication of how quickly someone can expect a response, without implying a universal response time unless a specific policy sets one.
- Publication and review information. When the statement was published, and when it was last reviewed, so a reader isn't relying on outdated information.
- Supporting evidence, where appropriate. A link to a recent evaluation report or audit, if one exists and is appropriate to share.
How Do You Write an Accessibility Statement?
Start by defining the scope precisely: which site, app, or product the statement actually covers. From there, identify the applicable accessibility standard and conformance level being targeted.
Before writing a single claim, assess the current state through internal review, external testing, or both, since the point of this step is to know the real answer before describing it publicly. Document the specific limitations that testing turns up, not a vague admission that issues may exist. Set up an actual feedback channel, an email address or form that is actively monitored, not one that goes unanswered.
From there, W3C's generator tool is a genuinely useful starting structure, not a finished answer. It collects the right categories of information but doesn't know an organization's specific situation or any additional policies and legal requirements that may apply. Customize the wording so it reflects what was actually found, publish it somewhere consistent and easy to find with a clear, recognizable link label, and set a real review date rather than leaving it untouched indefinitely.
Throughout, the discipline that matters most is deciding what can actually be substantiated before writing a conformance claim, not writing the claim first and hoping the evidence lines up afterward.
Can You Write an Accessibility Statement Without Testing?
An organization can publish a basic statement about its commitment and feedback process before completing a formal accessibility evaluation, but it should not make unsupported conformance claims. What shouldn't happen is a specific, detailed claim, "fully conforms to WCAG 2.2 AA," published without evidence to support it.
A commitment is honest even when the work is still in progress. A precise technical conformance claim should be supported by an appropriate evaluation, whether that's self-evaluation, external evaluation, or another recognized approach. W3C itself is clear that an accessibility statement is not a technical assessment or a declaration of conformity on its own.
What Should You Avoid Saying in an Accessibility Statement?
Avoid broad claims such as "fully accessible" or "100% accessible" unless the organization can substantiate precisely what the claim covers.
Avoid a specific conformance claim with no testing behind it. Avoid vague commitments that say nothing concrete, a statement of care with no standard, no status, and no contact method attached. Avoid denying known limitations that the organization is already aware of internally.
Avoid publishing a statement with no working feedback mechanism. Avoid letting the statement go stale for years after the product has changed significantly. Avoid copying a generic template without verifying that its claims match reality.
And avoid treating a single automated scan as proof of accessibility: automated tools can identify many rule-based accessibility issues, but they do not by themselves establish that people with disabilities can successfully complete real tasks.
If your organization needs help evaluating its current accessibility, understanding barriers, or building a stronger accessibility process, you can get in touch with BarrierBreak for accessibility support.
Frequently Asked Questions
Is an accessibility statement legally required in the US?
There is no single requirement that applies to every organization. Federal agencies are required to maintain a digital accessibility statement under OMB Memorandum M-24-08. Requirements for private businesses and other organizations can differ depending on the applicable law, sector, contract, or other obligation.
Does an accessibility statement guarantee legal compliance?
No. It's a communication document, not a conformance guarantee. A company can publish an accurate, well-written statement and still have real accessibility issues; the statement does not by itself establish compliance with WCAG or a particular law.
How often should an accessibility statement be updated?
For EU public sector bodies, the European Commission's guidance encourages regular review and updating, at least annually. Organizations more broadly should also review their statement whenever significant changes affect the accessibility of the website or app, not only on a fixed schedule.
Can I use W3C's accessibility statement generator?
Yes. It's a free, official tool that walks through the right categories of information, organization details, standard and conformance status, known limitations, and feedback options, and produces a usable starting draft. It's a helpful structure to build from, not a substitute for knowing your product's real accessibility status first.
Does an accessibility statement need to disclose accessibility problems?
Yes. If known accessibility limitations exist, the statement should describe them accurately and, where appropriate, explain available alternatives or support.
Where should an accessibility statement be published?
Somewhere consistent and easy to find. The European Commission's guidance for EU public sector bodies recommends making the statement reachable from every page, and U.S. federal agencies are required under OMB M-24-08 to provide accessible links to this information on their websites. For other organizations, a clearly labeled and consistently placed link is a practical way to help users find the statement.