It is a dedicated page on your website or app that explains what was made accessible, which standard was followed, what is still limited, and how to contact the person responsible for accessibility.
The short answer: An accessibility statement is a dedicated page on your website or app that tells users what was made accessible, which standard you followed, what is still limited, and who to contact when something does not work. A good accessibility statement template has five parts: a short intro about your organization, the accessibility adjustments made on the site, any known limitations or exemptions, accessibility arrangements at your physical locations, and the accessibility contact details with the date of the last update.
I get asked about accessibility statements almost every week. Usually the question is “can you send me a template I can paste in?” My answer is always the same: you can have the structure, but the content has to come from your own site. Below is the structure we use with clients, section by section, and the mistakes I keep seeing in statements that were copied from somewhere else.
An accessibility statement is a public page that explains three things to a visitor: what was done to make the site accessible, how to get help if something is not working, and how committed the organization is to keeping it that way. It covers the website itself and, if you receive the public, your offices, stores or branches too.
It is not a legal disclaimer and it is not marketing copy. Think of it as an honest status report written for a person who may be using a screen reader or a keyboard right now.
If your site serves users in Israel, the expectation is simple: every site publishes one, including organizations that have an exemption for part of the work. We cover the Israeli context in our guide to Israeli Standard 5568. Outside Israel, many public bodies and companies publish a statement as part of their WCAG work, and the W3C recommends it as good practice.
Yes. Each app, on iOS and on Android, should have its own statement that matches that platform: what was tested, which adjustments were made, on which devices it was checked, and who the contact is. A website statement does not automatically cover your app.
Five sections, from top to bottom. Here is what goes into each one.
Six to ten lines. Who you are, what you offer, who your users are, and a clear sentence about your commitment to accessibility. Keep it human. This is the part where your organization speaks in its own voice.
This is the heart of the statement. Describe what was actually done, not what you hope was done:
If the site has an accessibility widget, explain what it does and how to use it. To be clear, I don’t recommend relying on one. It does not replace accessible code.
If some content is not accessible yet, say which content and what users can do instead (for example, request the document by email). If you have an exemption for part of the site, state what it covers and why. I like to list both what was done and what is exempt, each in its own paragraph. It is not required, but it looks far more professional to users and to clients.
If you have an office, a store or any place that receives the public, describe what is accessible there: parking, entrance, the route inside, an accessible elevator. Be precise. Anyone can walk in and check, so only write what is true today. If you are not sure, check with the accessibility consultant who worked on your premises before you publish this part.
A full name, a direct phone number, an email address, and a way to send a written message. Real details of a real person who answers. A general company inbox, or the email of someone who comes in once a week, does not work.
In Israel, an organization with more than 25 employees is required to appoint an accessibility coordinator, and this is the person whose details belong here.
Close the statement with the date it was last updated.
Use this as a skeleton. Every bracket must be replaced with facts about your own site.
About us: [Organization name] provides [what you offer] to [who you serve]. We are committed to making our website and services usable by everyone, including people with disabilities.
Accessibility adjustments: This site was made accessible according to [standard and level, e.g. WCAG 2.2 AA]. The work was done [manually in the code / by our team with accessibility experts]. We tested [keyboard navigation, screen reader support, color contrast, forms, headings, alt text] using [browsers, screen readers and devices].
Known limitations: [Content or features that are not fully accessible yet, and the alternative users can request.] [Exemption details, if any, and what they cover.]
Physical accessibility: [Address.] [Parking, entrance, route, elevator, accessible restroom, service counter.]
Accessibility contact: [Full name], [role]. Phone: [direct number]. Email: [address]. Written messages: [SMS / messaging app / form].
Last updated: [date]
If you want a second reference point, the W3C has a guide and a generator for developing an accessibility statement. It is a good starting structure. The facts still have to come from your own audit.
Because it describes someone else’s site. In our audits we often see statements that say the site was tested with a screen reader, when nobody on the client’s side ever opened one. Here are the three problems that come with copying:
The same goes for asking an AI tool to write it. AI does not know your business, your premises or the work your site went through. What comes out is a generic text that sounds right and describes nothing. Use AI for slides and blog drafts, not for this page.
Read your current statement and answer four questions:
If most of your answers are “not sure”, rewrite it after an audit rather than copying a new one.
Every time something real changes: a site redesign, a new app version, a move to a new office, a new branch, a new contact person. Then update the date. I see plenty of statements last updated four or five years ago that no longer match the site or the building. Open the page, fix it, and you can stop worrying about it.
Start with the facts, not the wording. Get a manual audit of your main templates, fix what it finds, and write the statement from the results. That way every sentence on the page is true.
At WEB-A we write the statement as the last step of the work: a manual audit, fixes in the code, a retest, and then a statement that matches what was done. You can see the full process on our accessibility services page.
It is a dedicated page on your website or app that explains what was made accessible, which standard was followed, what is still limited, and how to contact the person responsible for accessibility.
Yes, as a structure. The five sections are the same for most sites, but the content has to describe your own site, your own testing and your own contact person. A copied statement describes someone else’s site.
For sites serving users in Israel, yes, including organizations with a partial exemption, which should state the exemption inside the statement. Elsewhere it is widely recommended as part of WCAG work, and the W3C encourages publishing one.
Whenever the site, the app, your physical locations or the contact person change, and at least when you review the site’s accessibility. Always update the date at the bottom.
This website uses essential cookies to operate and, with your consent, statistics cookies (Google Analytics). For more details, see our Privacy Policy.