A clear accessibility statement demonstrates your organisation’s commitment to digital inclusion. It signals that you recognise legal obligations and invites users to report issues. Without one, visitors may assume you haven’t considered accessibility at all.
What is an accessibility statement?
An accessibility statement is a short document explaining how your website or application conforms (or strives to conform) to recognised accessibility standards such as WCAG. It typically includes what standard and level you aim for, any known limitations, and ways for users to get in touch. Governments, universities and enterprises often require one for procurement and compliance.
Why publish an accessibility statement?
- Compliance – Many laws and regulations require public websites to provide an accessibility statement, including the EU Web Accessibility Directive and Section 508 in the United States.
- Transparency – Explaining your current level of compliance and any limitations builds trust with users and regulators.
- Feedback channel – Users can report barriers they encounter, helping you prioritise fixes and improve.
- Procurement – Buyers often ask for a VPAT or an accessibility statement before procuring software.
What to include
An effective statement should cover:
- Commitment – A brief commitment to providing an accessible experience.
- Standard and level – State whether you follow WCAG 2.1/2.2 at Level A/AA/AAA.
- Scope – Describe the parts of your site or app the statement applies to (web, mobile, specific subdomains).
- Limitations – List any known accessibility issues you’re working on and provide timelines for fixes if possible.
- Contact information – Provide an accessible method (email, form, phone) for users to request information or report barriers.
- Enforcement procedure – If relevant, explain how complaints can be escalated (for example, to an ombudsman).
Accessibility statement template (example)
You can adapt the following text for your organisation:
Commitment
[Organisation name] is committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability. We aim to conform to [WCAG version] at [Level A/AA/AAA].Measures to support accessibility
We take the following measures to ensure accessibility: [integrate accessibility into our development process, employ formal quality assurance methods, use automated and manual testing, etc.].Limitations and alternatives
We know some parts of this website are not fully accessible: [briefly list issues]. We plan to address these by [timeframe].Feedback and contact information
If you experience difficulty accessing any content on this site, please [contact us] at [email address or form]. We will respond within [X] business days.Formal complaints
If you are not satisfied with our response, you can [escalate the complaint] to [relevant body].
Remember to replace the placeholders with your details and keep the statement updated as you improve accessibility.
Best practices
- Use plain language – Avoid legal jargon; make it easy to understand.
- Keep it up to date – Review and update the statement as issues are fixed or standards change.
- Ensure accessibility of the statement itself – Use proper headings, lists and link text.
- Link to related documentation – If you have a VPAT/ACR, link to it.
Where to publish
Place your accessibility statement in a prominent location such as the footer or About section and link to it from your help or contact pages. If you offer multiple products, publish a separate statement for each.
Conclusion
An accessibility statement is more than a compliance checkbox—it’s an opportunity to communicate your commitment to inclusivity and engage with users. To determine how your site stacks up against the latest standards, consider an accessibility audit and use the findings to inform your statement.