The short answer
An accessibility statement is a public page that says which standard you aim for (usually WCAG 2.2 AA), how accessible the site is today, known problems and workarounds, how you test, and how people can contact you if they hit a barrier. Keep it honest and specific, date it, and update it after each review.
Key takeaways
- Be honest: list known issues instead of claiming full compliance.
- Give a real contact: email, phone and a promised response time.
- Say what standard you aim for and how you test.
- Date it and update it at least once a year.
- Link it from your footer on every page.
A good accessibility statement builds trust. It shows you take the topic seriously, sets honest expectations, and gives people a way to get help instead of leaving. Laws in some places, such as the public sector in the European Union, require one. Everywhere else it is simply good practice.
What to include, step by step
-
State your commitment
One or two sentences on why accessibility matters to your organization and who the statement covers (which site or app).
-
Name your target standard
For example: “We aim to meet WCAG 2.2 level AA.” Say whether you currently partially or fully meet it.
-
List known issues
Be specific: “Some older PDF menus are not tagged. Email us and we will send the menu as text.” Include workarounds and planned fix dates where you can.
-
Explain how you test
Mention automated weekly scans, manual keyboard checks, and any expert review, with the date of the last review.
-
Give contact options
Email, phone and a mailing address if relevant, with a response time such as “within 2 business days”.
-
Publish and link it
Put it at a simple address like /accessibility/ and link it in the footer of every page.
A simple template
Accessibility statement for [Your Company]
[Your Company] wants everyone to be able to use [website address]. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.
Current status: This website partially meets WCAG 2.2 AA. Known issues: [list issues and workarounds].
How we test: We scan our site automatically every [week] and test key pages by hand with a keyboard and screen reader. Last review: [date].
Visitor tools: Our site includes an accessibility menu where you can change text size, contrast, spacing and more. These tools are a convenience and do not replace our work to fix issues in the site itself.
Contact us: If you have trouble using any part of this site, email [email] or call [phone]. We reply within [2 business days].
This statement was last updated on [date].
What not to write
Avoid “This site is 100% accessible” or “fully ADA compliant” unless an expert audit backs it up, and even then, content changes daily. Avoid legal-sounding language that hides the contact details. And do not claim that a widget or overlay makes your site compliant. See are accessibility overlays enough? for why.
Let the tool draft it for you
Accessible Nord creates an accessibility statement for each site, in English and French, using your latest scan results, your contact details and the date of your last review. You edit it, publish it on a hosted page or copy it into your own site, and it stays up to date as you fix issues.
Sources
Last reviewed .
Frequently asked questions
Is an accessibility statement required by law?
For EU public sector bodies, yes. In Canada and the US it is usually not required for private businesses, but it is recommended and can show good faith. This is general information, not legal advice.
Should I list known problems publicly?
Yes. Being honest about known issues, with workarounds, is more helpful and more credible than a perfect claim that visitors can disprove in seconds.
Should the statement be in French too?
If you serve customers in Quebec or other French-speaking markets, offering it in French as well is a good idea, and Quebec language rules may require French for content aimed at Quebec consumers.
This guide is general information, not legal advice. For your specific obligations, check with a lawyer or your regulator.
