Loading…
Loading…
A public document describing a product's accessibility status, standards met, and contact information.
stellae.design
An accessibility statement is a public document that communicates an organization's accessibility commitment, conformance status, known limitations, and how users can report barriers. Under the EU Web Accessibility Directive (2016/2102), public sector bodies must publish accessibility statements in a specific format. While not legally mandated for private sector in most countries, publishing one demonstrates good faith, helps users understand what to expect, and provides a crucial feedback channel. The W3C WAI provides a generator tool and template. A good accessibility statement is honest about limitations rather than making blanket claims, includes specific contact information, and is regularly updated to reflect the current state of the product.
An accessibility statement is a public declaration of an organization's commitment to digital accessibility, outlining the standards it follows, known limitations, and how users can report barriers they encounter. Beyond legal compliance, it signals to users with disabilities that they are recognized, valued, and supported — a message that builds trust and loyalty in a demographic that represents over one billion people globally. Organizations without a published statement risk both legal exposure under regulations like the ADA and EAA, and reputational damage when users with disabilities encounter barriers with no clear path to resolution.
GOV.UK publishes a detailed accessibility statement for each service, listing the WCAG 2.1 AA conformance target, specific known issues with remediation timelines, and a direct contact path for reporting new barriers. The transparency builds public trust and demonstrates that accessibility is treated as an ongoing operational commitment rather than a one-time checkbox. The structured format has become a de facto template adopted by organizations across Europe.
Microsoft publishes an accessibility statement across its product suite that references specific standards (WCAG, EN 301 549, Section 508), provides conformance reports for individual products, and links to dedicated support channels for users with disabilities. The statement is updated with each major product release and includes voluntary product accessibility templates that enterprise buyers can review during procurement. This level of detail turns the statement into a competitive differentiator in enterprise sales.
A retail website copies a generic accessibility statement template, buries it in the footer legal section with no contact information or issue-reporting mechanism, and never updates it after the initial site launch. Users who encounter barriers have no way to request assistance or report problems, and the statement claims WCAG 2.1 AA compliance despite dozens of unresolved audit findings. The hollow claim exposes the company to legal risk and alienates the very users it claims to support.
• The most common mistake is publishing a vague, copy-pasted statement that claims full compliance without specifying which standard, which conformance level, or which pages have been evaluated — this satisfies neither legal requirements nor user needs. Teams also frequently treat the statement as a static legal document rather than a living page that must be updated whenever the product changes, leading to claims that diverge from reality over time. Failing to include an accessible feedback channel is equally damaging, because users who find barriers and see no way to report them conclude the organization does not genuinely care about accessibility.
Was this article helpful?