Free template · No sign-up

Accessibility statement: template to copy

Here you will find a template for the accessibility statement of public sector bodies based on the EU model statement, and a template for the accessibility information required under the German BFSG. For each section we explain what to fill in and which mistakes are common.

Sources checked on 10 November 2026.

Who needs which document?

Public sector bodies and businesses have different obligations. First check which group you belong to.

Public sector bodies: accessibility statement

Directive (EU) 2016/2102 requires public sector bodies to publish an accessibility statement for their websites and mobile apps. Commission Implementing Decision (EU) 2018/1523 sets out its structure with a model statement. Each member state transposes the directive into national law, so the legal references, deadlines and enforcement bodies differ. In Germany, federal bodies are covered by § 12b BGG and § 7 BITV 2.0, while the Länder and municipalities follow their own state law. Under § 7 BITV 2.0 the statement must be reachable from the start page and from every page and published in an accessible, machine-readable format.

Businesses under the German BFSG: accessibility information

The BFSG does not require an accessibility statement in this sense. Under § 14 BFSG, service providers must prepare the information listed in Anlage 3 and make it publicly available in an accessible form, in their terms and conditions or in another clearly perceptible way. It includes a general description of the service, explanations needed to understand how it is carried out, a description of how it meets the accessibility requirements and the competent market surveillance authority. Unlike public bodies, businesses do not list and justify non-accessible content: the service has to meet the requirements.

Austria

Federal websites and mobile apps are covered by the Web-Zugänglichkeits-Gesetz (WZG). Under § 4 WZG, an accessibility statement must be published, kept up to date and be reachable from the start page. Complaints go to the body under § 5 WZG; as long as no regulation designates another body, this is the Austrian Research Promotion Agency (FFG). The Länder and municipalities follow state law, and businesses are covered by the Barrierefreiheitsgesetz (BaFG), which this template does not cover.

Switzerland

Switzerland is bound neither by the EU directive nor by the BFSG. The EU model can serve as a structure, but it is not a legal requirement there. The relevant rules are the Disability Discrimination Act (BehiG) and cantonal regulations.

Country guides:GermanyAustriaSwitzerland

Template: accessibility statement for public sector bodies

The template follows section 1 of the model statement in Implementing Decision (EU) 2018/1523. Replace everything in square brackets, choose exactly one compliance status and delete anything that does not apply before you publish.

Template text

Accessibility statement

[Name of the public sector body] is committed to making [its website / its mobile application] accessible, in accordance with [national legislation transposing Directive (EU) 2016/2102].

This accessibility statement applies to [address of the website / name and version of the mobile application].

Compliance status

[Choose one option and delete the others.]

[Option (a), only if all requirements are fully met without exception:] This website is fully compliant with [legislation or standard].

[Option (b):] This website is partially compliant with [legislation or standard] due to the non-compliances [and/or] the exemptions listed below.

[Option (c):] This website is not compliant with [legislation or standard]. The non-compliances [and/or] the exemptions are listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons:

(a) Non-compliance with [legislation or standard]

  • [Affected page or function and the specific problem, e.g. "In the contact form, error messages are not associated with the affected input field."] [Requirement concerned, e.g. WCAG success criterion 3.3.1.] [Accessible alternative, e.g. contact by e-mail at …]

(b) Disproportionate burden

  • [Affected content or function, the reasons for your assessment under Article 5 of Directive (EU) 2016/2102 and national law, accessible alternative]

(c) The content is not within the scope of the applicable legislation

  • [Affected content and the exemption you rely on]

[Delete any reasons that do not apply.]

Preparation of this accessibility statement

This statement was prepared on [date].

The statement is based on [a self-assessment carried out by [name of the public sector body] / an assessment carried out by a third party, [name], e.g. a certification]. [Short description of the method: pages and processes checked, test procedure, test period.]

The statement was last reviewed on [date of the latest review].

[Optional: link to the assessment report.]

Feedback and contact information

Have you noticed any accessibility problems with the content of [website]? Or do you have questions about accessibility? Please contact us:

[Link to an accessible contact form or e-mail address]

[Responsible unit or person, postal address, telephone]

[Response time, if national law sets one.]

Enforcement procedure

If you do not receive a satisfactory response to your feedback or request, you can contact the enforcement body: [description of and link to the enforcement procedure under national law].

[Name and contact details of the enforcement body]

Additional information

[Optional, following section 2 of the EU model: planned measures to remove barriers with a timeframe, date the website was published, date of the latest substantial update, additional telephone support. Otherwise delete.]

How to fill in each section

The statement describes the actual state of your website. Every statement should be backed by testing you can document.

Introduction and scope
Name the body, the applicable legislation and exactly which websites or apps the statement covers. For German federal bodies this is § 12a BGG and BITV 2.0; for the Länder and municipalities, the relevant state law.
Compliance status
Choose exactly one option. According to the notes in the EU model, "fully compliant" only fits if all requirements are met without exception. "Partially compliant" fits if most requirements are met, "not compliant" if most are not met.
Non-accessible content
Describe every known barrier so that non-experts understand it: the affected page or function, the problem and the requirement concerned. Where possible, name an accessible alternative. The body assesses a disproportionate burden itself under Article 5 of the directive and explains it in the statement. It is not a catch-all for content nobody has checked.
Preparation of the statement
State the preparation date, the method and the date of the latest review. The implementing decision names two methods: a self-assessment by the public sector body or an assessment by a third party, such as a certification. Under § 7 BITV 2.0 an actual assessment must have taken place. You can link to an assessment report.
Feedback and contact information
The contact option must work and be accessible itself. In Germany, § 12b BGG requires a directly accessible electronic contact option, and federal bodies must reply within one month at the latest.
Enforcement procedure
Name the procedure and body that national law provides. Examples: for German federal bodies, the Schlichtungsstelle under § 16 BGG (Mauerstraße 53, 10117 Berlin, info@schlichtungsstelle-bgg.de; free of charge); for Austrian federal bodies, the body under § 5 WZG; for the Spanish public sector, the complaint procedure under Real Decreto 1112/2018.

Common mistakes

These mistakes make a statement unreliable or incomplete:

  • Claiming "fully compliant" based only on an automated scan. Automated tests only detect some of the requirements. Keyboard operation, screen reader output and understandable content need manual testing.
  • Known barriers are missing or only described vaguely, such as "Some PDFs are not accessible", without naming the document, the problem and an alternative.
  • The contact is missing, does not work, or the contact form itself cannot be used accessibly.
  • The date is outdated: the statement describes a state that is no longer accurate after a relaunch or major changes.
  • Placeholders, instructions in square brackets or options that were not chosen are still in the published text.
  • The public sector statement is copied unchecked for a service that falls under the BFSG.

How often should you review the statement?

Directive (EU) 2016/2102 requires the statement to be updated regularly. Implementing Decision (EU) 2018/1523 recommends reviewing it for accuracy regularly, at least once a year. National law may be stricter: in Germany, § 7 BITV 2.0 requires federal bodies to update the statement annually and whenever the website or app changes significantly.

There is no fixed cycle for BFSG information. Under § 14 BFSG the requirements must be met at all times while the service is offered, and changes to the service must be taken into account appropriately. Update the information after every relevant change and keep it for as long as you offer the service.

Template: accessibility information under the German BFSG

This shorter template is for businesses whose service falls under the German BFSG, such as an online shop selling to consumers in Germany. It follows the minimum content of Anlage 3 no. 1 BFSG. It is not an accessibility statement in the sense of the EU directive for public bodies. Businesses in other EU countries follow their own national transposition of the European Accessibility Act (Directive (EU) 2019/882).

Template text

Accessibility information for [name of the service, e.g. online shop example.de]

[Legal basis: § 14 BFSG in conjunction with Anlage 3 no. 1. Delete this note before publishing. If your customers in Germany expect German, publish the information in German.]

General description of the service

[What do you offer, to whom and through which channels? For example: Through the website [address] and the app [name], consumers can select, order and pay for [products or services].]

How the service is carried out

[Describe the steps needed to understand the service, e.g. search, product selection, customer account, basket, payment, order confirmation and customer service.]

How the service meets the accessibility requirements

[Describe how the requirements of the regulation under the BFSG (BFSGV) are met, for example:]

  • [Standards or technical specifications applied, e.g. "The website was tested against WCAG 2.1 level AA." Only state this if it is true.]
  • [Keyboard operation, screen reader support, text alternatives for images, sufficient contrast, understandable forms and error messages]
  • [Accessible communication channels, e.g. customer service by e-mail, phone or chat]
  • [How and when accessibility was last tested]

Competent market surveillance authority

Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF AöR)

Carl-Miller-Straße 6, 39112 Magdeburg, Germany

E-mail: kontakt@mlbf-barrierefrei.de

Website: www.mlbf-barrierefrei.de

Contact

[Optional: how customers can report accessibility issues, e.g. e-mail address and phone number.]

Last updated: [date]

What to keep in mind for BFSG information

  • Where to publish: Anlage 3 mentions the terms and conditions or another clearly perceptible way. The Bundesfachstelle Barrierefreiheit, Germany’s federal accessibility agency, recommends an "Accessibility" link in the header or footer of the website.
  • No list of non-accessible content: according to the Bundesfachstelle, services under the BFSG generally have to be fully accessible. If your service does not meet the requirements, § 14(4) BFSG requires you to take corrective action and inform the market surveillance authority.
  • The Schlichtungsstelle under § 16 BGG also handles conciliation under the BFSG. According to the Bundesfachstelle, you do not need to name it in the information.
  • Services provided by micro-enterprises are exempt under § 3(3) BFSG.

Create and maintain the statement in your account

Instead of maintaining the template by hand, you can use the Accessonaut generator to create an editable draft from your details and a dated scan record. Versions are saved in your account, and an e-mail reminds you before the annual review.

Go to the statement generatorGuide: documenting an accessibility statement honestly

A template, not legal advice

This template is not legal advice. Which obligations apply to you depends on whether you are a public sector body or a business and which national or state law applies. The statement must match your actual testing: do not copy any claim you cannot back up.

Original sources

Sources checked on 10 November 2026.

Practical knowledge for your next steps

All articles in the knowledge base