# Accessibility Statement: What to Include

Source: https://allyway.ai/glossary/accessibility-statement

An accessibility statement is a public page that explains how accessible a website or app is, which standard it aims for, what is not accessible yet and how people can report barriers or get content in another form.

An accessibility statement is a page on your website that tells visitors how accessible it is, which standard you follow and what to do if something doesn't work for them. For public bodies in the EU it is a legal duty, and businesses covered by the [European Accessibility Act](https://allyway.ai/glossary/european-accessibility-act) must publish comparable information about their services. A good statement, sometimes called an accessibility declaration, is honest about known gaps and gives people a direct way to reach you.

## What it means

The W3C recommends a minimum of three things in every statement: a commitment to accessibility for people with disabilities, the standard you apply (such as [WCAG](https://allyway.ai/glossary/wcag) 2.2), and contact information in case people run into problems. It also suggests listing known limitations, the measures you take and the technologies you tested with – see [Developing an Accessibility Statement](https://www.w3.org/WAI/planning/statements/) by W3C WAI.

Who has to publish one depends on the law:

| Who | Law | What is required |
|---|---|---|
| Public sector bodies in the EU | Web Accessibility Directive (EU) 2016/2102, Article 7 | A detailed, comprehensive and clear statement, updated regularly, with the parts that are not accessible and why, a feedback mechanism and a link to the enforcement procedure |
| Federal public bodies in Germany | BGG and [BITV 2.0](https://allyway.ai/glossary/bitv) | A statement following the EU model |
| Public bodies in Austria | [Web Accessibility Act (WZG)](https://allyway.ai/glossary/web-zugaenglichkeits-gesetz) | A statement following the EU model |
| Businesses with covered consumer services in Germany | [BFSG](https://allyway.ai/glossary/bfsg), § 14 and Annex 3 | Information on how the service meets the requirements, in the terms and conditions or another clearly perceptible way, naming the market surveillance authority |
| Businesses with covered consumer services in Austria | [BaFG](https://allyway.ai/glossary/barrierefreiheitsgesetz-austria), Annex 3 | Information on how the service meets the requirements, in the terms and conditions or a similar document |

The EU publishes a model statement for public bodies in [Implementing Decision (EU) 2018/1523](https://eur-lex.europa.eu/eli/dec_impl/2018/1523/oj). It asks for a compliance status – fully, partially or not compliant – the non-accessible content with its reasons, how and when the statement was prepared, feedback and contact details, and the enforcement procedure.

> **Warning:** > **A statement is not a certificate**
> A statement describes your website; it doesn't make it accessible. Never claim more than you have tested – automated checks cannot find every barrier.

## Examples

Link the statement from the same place on every page, usually the footer, with a consistent link name. Inside the statement, use real headings and a contact that works:

```html title="Example"
<footer>
  <a href="/accessibility">Accessibility statement</a>
</footer>

<!-- /accessibility -->
<h1>Accessibility statement</h1>
<p>We aim to meet WCAG 2.2 Level AA. Last reviewed: 3 November 2026.</p>
<h2>Known limitations</h2>
<ul><li>Some older product videos have no captions yet.</li></ul>
<h2>Feedback</h2>
<p>Found a barrier? Email <a href="mailto:access@example.com">access@example.com</a>.</p>
```

The known limitation above names a real gap in plain words, as the W3C advises, instead of citing a criterion number such as [captions](https://allyway.ai/glossary/captions) 1.2.2.

**Do:** Do

Name the standard, list known gaps in plain language, give a contact that someone reads, add the review date and update the statement after every larger change.

**Don't:** Don't

Claim the website is "fully compliant" without a test, hide the statement deep in the site, or leave an outdated date and broken contact links.

## How to write an accessibility statement



## Questions

Q: Is an accessibility statement mandatory?
A: For public sector bodies in the EU, yes – under the Web Accessibility Directive and national laws such as the BGG with BITV 2.0 in Germany and the WZG in Austria. Businesses covered by the BFSG or BaFG must publish information on how their service meets the accessibility requirements.

Q: What should an accessibility statement include?
A: At least your commitment, the standard you follow (for example WCAG 2.2 AA), known limitations and a contact for feedback. Public bodies also add the compliance status, the reasons for non-accessible content and the enforcement procedure.

Q: Where should I put the accessibility statement?
A: On its own page, linked from the footer or another place that appears on every page. Use the same link name everywhere so people recognise it.

Q: How often should I update my accessibility statement?
A: Whenever the website changes significantly, and at regular intervals. Public bodies must update it regularly under the Web Accessibility Directive; include the date of the last review.

Q: How do I find out what to write under known limitations?
A: Test your site: an automated check finds many common issues, and manual testing with keyboard and screen reader finds the rest. The [free WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) checks a page against WCAG 2.2 AA in seconds.
