Accessibility Statement
A public statement declaring your website's or app's current level of accessibility conformance, known issues, and contact information for accessibility-related feedback.
What is a Accessibility Statement?
A public statement declaring your website's or app's current level of accessibility conformance, known issues, and contact information for accessibility-related feedback.
Regulators across EU, UK, US treat a Accessibility Statement as a baseline legal requirement. Without one, your business is immediately exposed to enforcement action — regardless of size or industry.
Who Needs a Accessibility Statement?
Public sector bodies (legally required in UK/EU) and private companies subject to the EU European Accessibility Act or ADA.
- Any organisation that public sector bodies (legally required in uk/eu) and private companies subject to the eu european accessibility act or ada
- Businesses operating in EU and UK
- Anyone using third-party services that process data on your behalf
Legal Framework
EU Web Accessibility Directive 2016/2102, UK PSBAR 2018, ADA Title III (US), European Accessibility Act.
EU
EU GDPR — up to €20M or 4% turnover
UK
UK GDPR — ICO enforcement
US
Applicable national and regional regulations
What Your Accessibility Statement Must Include
- 1
Conformance Status (WCAG level)
Conformance Status (WCAG level) — Clearly define conformance status (wcag level) so users and regulators understand its scope and why it matters for your compliance obligations.
- 2
Non-Accessible Content
Non-Accessible Content — Clearly define non-accessible content so users and regulators understand its scope and why it matters for your compliance obligations.
- 3
Known Issues
Known Issues — Clearly define known issues so users and regulators understand its scope and why it matters for your compliance obligations.
- 4
Feedback Mechanism
Feedback Mechanism — Clearly define feedback mechanism so users and regulators understand its scope and why it matters for your compliance obligations.
- 5
Enforcement Contact
Enforcement Contact — Clearly define enforcement contact so users and regulators understand its scope and why it matters for your compliance obligations.
- 6
Preparation Date
Preparation Date — Clearly define preparation date so users and regulators understand its scope and why it matters for your compliance obligations.
- 7
Technical Compatibility
Technical Compatibility — Clearly define technical compatibility so users and regulators understand its scope and why it matters for your compliance obligations.
- 8
Assessment Approach
Assessment Approach — Clearly define assessment approach so users and regulators understand its scope and why it matters for your compliance obligations.
How to Write a Accessibility Statement
Building a compliant Accessibility Statement from scratch takes legal expertise and hours of research. Here is a framework covering the core steps:
- 1Step 1: Conformance Status (WCAG level) — Document this section completely and accurately. Vague or incomplete disclosures can be treated as violations even if the underlying practice is compliant.
- 2Step 2: Non-Accessible Content — Document this section completely and accurately. Vague or incomplete disclosures can be treated as violations even if the underlying practice is compliant.
- 3Step 3: Known Issues — Document this section completely and accurately. Vague or incomplete disclosures can be treated as violations even if the underlying practice is compliant.
- 4Step 4: Feedback Mechanism — Document this section completely and accurately. Vague or incomplete disclosures can be treated as violations even if the underlying practice is compliant.
- 5Step 5: Enforcement Contact — Document this section completely and accurately. Vague or incomplete disclosures can be treated as violations even if the underlying practice is compliant.
- 6Step 6: Preparation Date — Document this section completely and accurately. Vague or incomplete disclosures can be treated as violations even if the underlying practice is compliant.
- 7Final step: Legal review — Review with qualified legal counsel before publishing, especially if operating in high-risk jurisdictions.
Common Mistakes to Avoid
Copying another website's Accessibility Statement verbatim — Every business has different data flows. A generic copy may fail to disclose what you actually do, creating false statements that are worse than no policy at all.
Using vague or ambiguous language — Regulators and courts expect plain, specific language. Phrases like "we may share your data with partners" are too vague and regularly cited in enforcement actions.
Forgetting to update after product changes — Your Accessibility Statement must reflect current practice. Outdated policies are a compliance liability — some regulators treat an outdated policy as a violation in itself.
Not making your Accessibility Statement easy to find — Buried in a footer or behind multiple clicks, your policy may not meet the "easily accessible" standard required by most regulations.
Missing jurisdiction-specific requirements — A policy compliant in one jurisdiction may still fail in another. If you operate across EU and UK, you need to address each framework's specific requirements.
How Often Should You Update Your Accessibility Statement?
At minimum, review your Accessibility Statement once a year — and immediately whenever you: change the data you collect, add new third-party tools, enter new jurisdictions, or experience a data incident.
Consequences of Non-Compliance
Beyond financial penalties, non-compliance with Accessibility Statement requirements can result in: reputational damage and loss of customer trust, app store removal (for mobile apps), inability to process payments (for ecommerce), and difficulty attracting enterprise customers who require compliance evidence.
Frequently Asked Questions
Is a Accessibility Statement legally required?
Yes. A Accessibility Statement is a legal requirement under EU Web Accessibility Directive 2016/2102, UK PSBAR 2018, ADA Title III (US), European Accessibility Act.. Operating without one puts your business at risk of regulatory enforcement action.
How long should a Accessibility Statement be?
A typical Accessibility Statement runs 2 pages. Length matters less than completeness — every required disclosure must be present, written in plain language that users can understand.
How often should I update my Accessibility Statement?
At minimum, review your Accessibility Statement once a year — and immediately after any business change.
What are the penalties for not having a Accessibility Statement?
Regulatory enforcement for public sector bodies. ADA lawsuits in the US.
Can I use a free Accessibility Statement template?
Free templates are a starting point, not a solution. A template that was not drafted for your specific business, jurisdiction, and data practices may create false statements — which is legally worse than having no policy at all. Always customise any template and have it reviewed by qualified counsel.
Related Policies
GDPR Compliance Policy
A comprehensive internal and external framework documenting how your organisatio…
Read guide 💬Community Guidelines
The behavioral standards for users in social or collaborative spaces, focusing o…
Read guide 📣Forum Rules
Highly specific technical and behavioral rules for message boards and bulletin b…
Read guide 🔗Affiliate Disclosure
A legally required statement disclosing that you may earn a commission when read…
Read guidePolicifyAI is a technology provider, not a law firm. The information on this page is for orientation only and is not legal advice. Generated templates are intended as a structured starting point for review by qualified counsel before publication.