How to Write an Accessibility Statement (with a Template)
An accessibility statement is a short public page that states your commitment, the standard you target, known limitations, and how users can report barriers. It's expected under several laws and is genuinely useful.
An accessibility statement is a public document declaring your commitment to digital inclusion and describing the current accessibility status of your site or app. It's required or strongly expected under laws like the EAA and public-sector rules, and it's a practical good-faith signal everywhere else.
What to include
- Commitment and scope — your dedication to accessibility and which sites/apps are covered.
- Conformance status — the standard you target (e.g., WCAG 2.2 Level AA) and your current level (fully, partially, or working toward).
- Known limitations — specific barriers you're aware of, where they are, and their impact.
- Remediation plan — timelines for fixing known issues and any interim workarounds.
- Feedback mechanism — a dedicated email or phone number for reporting problems and requesting help.
- Dates — when the statement was last reviewed or updated.
Where to put it
Link it from your footer so it's reachable from every page, and keep the language plain and jargon-free. Many regulators expect the statement to be easy to find — the footer is the conventional home.
A reusable template
[Company] is committed to making [website] accessible to everyone. We aim to conform to WCAG 2.2 Level AA. We are currently [fully / partially] conformant; known limitations include [list]. We plan to resolve these by [date]. If you encounter a barrier, contact us at [email] or [phone] and we will respond within [timeframe]. This statement was last reviewed on [date].
Keep it honest and current
Don't claim full conformance you can't back up — an inflated statement is worse than an honest one. List real limitations, give a real contact, and review it on a schedule as you remediate.
accessibilitywebsite.com can generate an accessibility statement based on your latest scan results, so the conformance claims and known limitations reflect your site's actual status — and stay current as you fix issues.
Frequently asked questions
- What should an accessibility statement include?
- Your commitment and scope, the standard you target (such as WCAG 2.2 AA) and conformance level, known limitations, a remediation plan, a feedback contact, and the date it was last reviewed.
- Where should the accessibility statement go on my website?
- Link it from the footer so it is reachable from every page, which is where regulators and users expect to find it.
- Is an accessibility statement legally required?
- It is required or strongly expected under several laws, including the European Accessibility Act and public-sector accessibility rules, and is considered good practice everywhere else.
See where your site stands — free
Run an instant WCAG 2.2 AA scan and get a severity-ranked report with AI fix suggestions in seconds. No overlay, no false promises.