An accessibility statement is a public document that explains which accessibility standard a website or application targets, its current conformance status, known shortcomings and a feedback channel. In the EU it is mandatory for public sector websites, and services covered by the EAA must also provide accessibility information. A statement must be based on a real assessment.
A statement typically contains the following: scope (which site or application it covers), the target standard (for example WCAG 2.2 AA), the current conformance status (full, partial or non-conformant), known accessibility issues, the assessment method used, the dates of preparation and last update, and a feedback channel. EU rules for public sector websites make the statement mandatory, and private sector services covered by the EAA must also provide information on how they meet accessibility requirements. In practice, the statement is published on a dedicated page reachable from the site footer.
The value of a statement lies in its honesty: a statement that claims everything is conformant without a real assessment weakens both user trust and your legal position. The right approach is to base it on automated scan and manual test results, list known shortcomings openly and include a remediation plan. It is a living document and should be updated after significant site changes and each new assessment, and the feedback channel must actually work, with reported barriers answered within a reasonable time. Whether you draft the statement by hand or with a generator tool, reviewing organization-specific details before publishing remains your responsibility.
Frequently asked questions
Is an accessibility statement mandatory?
It depends on which rules apply to you. In the EU, a statement is explicitly mandatory for public sector websites and mobile applications. Private sector services covered by the EAA are obliged to provide information on how they meet accessibility requirements. In Türkiye, Circular 2025/10 sets a WCAG 2.2 Level A target; publishing a statement is good practice that documents transparency in that process.
What should an accessibility statement include?
At minimum: the site or application covered, the target standard and level (for example WCAG 2.2 AA), the current conformance status, known accessibility issues and any workarounds, the assessment method (automated scan, manual testing, third-party audit), preparation and update dates, and a contact channel where users can report barriers. Writing shortcomings openly together with a remediation plan strengthens the statement rather than weakening it.
This content is for information only and is not legal advice.