The accessibility statement: complete, honest and easy to find

Two sets of rules

National laws implement both directives and may add details. Check which rules apply to you.

Businesses: the information under Annex V

Article 13(2) of the European Accessibility Act requires service providers to prepare information in line with Annex V, explain how their services meet the accessibility requirements and make it public in written and oral format, including in an accessible way. Annex V says the information belongs in the general terms and conditions or an equivalent document and covers, as far as relevant:

1. a general description of the service in accessible formats,
2. descriptions and explanations needed to understand how the service operates,
3. a description of how the service meets the relevant requirements of Annex I.

Providers may use the harmonised standards to do so. Some countries add items; Germany, for example, also requires naming the market surveillance authority. Microenterprises providing services are exempt, see the EAA for small businesses.

Public sector: the EU model statement

Public sector bodies publish a statement for each website and app under Article 7 of Directive (EU) 2016/2102. Implementing Decision (EU) 2018/1523 sets a model with mandatory items:

• compliance status: fully, partially or not compliant,
• content that is not accessible and why,
• when the statement was prepared and how (self-assessment or third party),
• a feedback mechanism and contact details,
• the enforcement procedure people can turn to.

Optional items include measures beyond the minimum and plans to remove barriers. National laws set details such as where to publish and how often to update; in Germany, for example, the statement must be reachable from every page and updated every year.

Be honest about compliance status

Only say “fully compliant” when every criterion has been tested and met. An automated scan cannot show that, because many criteria cannot be measured. “Partially compliant” with a clear list of known issues and a date for fixing them is more honest and more useful.

Be specific: not “some images lack text alternatives” but “product images in the accessories section have no text alternatives yet; we will add them by the end of March”. That is how we handle our own statement.

Link it where people look

A link in the footer that has the same name and position on every page is the most reliable way to make the statement reachable (3.2.3 Consistent Navigation, 3.2.4 Consistent Identification). The link text should name its target (2.4.4 Link Purpose (In Context)).

<footer>
  <span onclick="openInfo()">More</span>
</footer>

<footer>
  <nav aria-label="Legal">
    <ul>
      <li><a href="/legal-notice/">Legal notice</a></li>
      <li><a href="/accessibility/">
        Accessibility statement</a></li>
    </ul>
  </nav>
</footer>

A plain link with a clear name works with keyboard, screen readers and without JavaScript.

How to write yours

1. Define the scope: which website, which app, which areas.
2. Test: run an automated pre-check, then have people assess every criterion (our method).
3. List known barriers with reasons and a timeline.
4. Set up a contact channel and decide who answers reports.
5. Draft the text, for example with our statement generator.
6. Add the date and a reminder for the next update.

Checklist

Related WCAG criteria

• 2.4.4 Link Purpose (In Context)
• 3.2.3 Consistent Navigation
• 3.2.4 Consistent Identification
• 3.2.6 Consistent Help

Tools and patterns for this

• Statement generatorPrepare your accessibility statement
• Our accessibility statementHow we handle it on this website
• EAA & national lawsDuties, deadlines, enforcement
• MethodAll 55 criteria, openly described

Frequently asked questions

Sources

• Directive (EU) 2019/882, Article 13 and Annex V (EUR-Lex)
• Directive (EU) 2016/2102, Web Accessibility Directive (EUR-Lex)
• Implementing Decision (EU) 2018/1523, model accessibility statement (EUR-Lex)