What is an accessi­bility statement?

Accessi­bility statement: definition and obligation

The accessibility statement originates in the law for public bodies (BGG and BITV 2.0, based on EU Directive 2016/2102): authorities must publish a statement in line with a European template on their websites and apps. It makes transparent how accessible an offering is and where defects remain.

For private companies, the BFSG does not prescribe a statement in exactly this form, but it does impose information duties: service providers must inform consumers how their offering meets the accessibility requirements, for example in their terms and conditions or at another clearly recognizable place. In practice, a dedicated “Accessibility” page that follows the structure of the statement has become the norm.

Content: what belongs in the statement

A good statement is specific rather than general. It states what was tested, what the status is and how visitors can report barriers. What counts is the actual test status, not the aspiration. The template for public bodies offers good guidance here.

• Scope: which website, apps or services are meant
• Conformity status: fully, partially or not compliant with the requirements
• Specific inaccessible content with reasons and, where possible, alternatives
• Date of creation or last review and the test method
• Contact for feedback on barriers
• For public bodies in addition: reference to the enforcement and conciliation procedure

Real-world example: an operator of several fitness studios

An operator of several fitness studios sells memberships and class places online. A review shows that the class schedule is poorly structured for screen readers, videos have no captions and the house rules exist only as an inaccessible PDF. The operator fixes the class schedule first, because that is where booking takes place and where visitors without accessibility would be excluded fastest.

The “Accessibility” page states the status “partially accessible,” lists the open points with a timeline, gives the review date and offers an email address for feedback. Incoming feedback is answered within a few working days. This makes clear where the offering stands and what is being worked on.

Common mistakes and limits

Frequent mistakes are a statement without a prior test, the blanket claim “fully accessible,” missing dates, a contact address that is never answered, and a page that is not linked in the footer. False statements can be challenged as misleading and damage visitors’ trust.

The statement does not replace implementation. It documents the status but removes no barriers and is not a liability waiver. If the website changes, for example through a relaunch or new features, the statement must be adjusted too, so that it reflects the actual state.

What companies should look out for

First check whether your offering falls under the BFSG. Then have a test done with keyboard, screen reader and testing tools and record the result. Link the page in the footer, update it after every major relaunch and answer feedback promptly. Nano Concepts supports the testing, implementation and technical integration of the page. This article does not replace legal advice.