Guide · Accessibility statement
How to write a website accessibility statement
An accessibility statement is a page on your site that tells visitors what you did to make the site accessible, what still isn't accessible, and who to contact when something doesn't work. Here is what the Israeli regulations require, based on their text, plus a structure that works, a sample and common mistakes.
General information, not legal advice. I wrote this guide from the text of the law and regulations as I checked it on 14 November 2026. Legislation changes. For your own business, ask a lawyer.
In short
- The duty to publish a website accessibility statement is in regulation 35E (35ה) of the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013.
- The statement must appear in a prominent place on the site, and in your app if you have one.
- It must include three things: the accessibility adjustments you made; the accessibility coordinator's details and contact methods, if you must appoint one; and contact details for reporting an accessibility problem or requesting an adjustment.
- If you received an exemption from a specific adjustment for technological reasons, the statement must mention the exemption and the alternative adjustments (regulation 35F(c)).
- A statement doesn't make a site accessible. It should describe the real situation, including what isn't fixed yet.
What the regulation says
This is my translation of regulation 35E, titled "Accessibility statement in internet services":
"In addition to regulations 34 and 91(e), an obligated party shall state in a prominent place on its website, and in any application it operates, a statement, in accordance with the guidelines in the internet accessibility standard regarding an accessibility statement, that includes information on the accessibility adjustments it made, the details of the accessibility coordinator and how to contact them, if it must appoint one under the Law, and details that allow contact for reporting a lack of accessibility adjustments or requesting an adjustment, including a demand under regulation 35A(d)(1)."
A few notes on the text:
- The "internet accessibility standard" is IS 5568, as defined in regulation 35. In parts 1 and 2 of the standard, in the September 2023 editions published on gov.il, I didn't find a section on accessibility statements. So I treat the list in the regulation itself as the baseline, and add details that help visitors.
- Accessibility coordinator: under section 19MB (19מב) of the Law, whoever is responsible for a public service and employs at least 25 employees must appoint one. If you don't have to, you still need a way for people to contact you.
- "A demand under regulation 35A(d)(1)" is a notice someone sends you about an accessibility problem. Under that regulation the problem must be fixed within a reasonable time and no later than 60 days from receiving the notice. So the contact details must reach someone who reads them.
- Regulation 34 also requires publishing the accessibility adjustments of the service and of the places where it is given, such as a shop or office, among other ways on your website. If you have a physical location, you can cover it on the same page.
A structure that works
This is the structure I recommend. Items marked "required" are the ones regulation 35E names explicitly. The rest help visitors know what to expect.
- Title and date. "Accessibility statement", and the date you last updated it.
- Scope. The site address, and the app if there is one.
- The level you aim for. The regulations require IS 5568 at level AA (regulation 35A(a)). Part 1 of the standard is identical to WCAG 2.0, with a few national changes. If the site hasn't had a full audit, say you are "working to meet" it, not that it "complies".
- What you actually did (required). For example: alt text for images, labels for form fields, heading structure, keyboard navigation, colour contrast, captions. Only list what was really done.
- How and when you checked. Automated check, manual keyboard check, screen-reader check, and who did it.
- What isn't accessible yet, and the alternative. For example old PDFs, videos without captions, or content uploaded by users (regulation 35B covers that separately). Say how people can get the information another way.
- Exemptions, if any. Regulation 35F(c) requires publishing a technological exemption and the alternative adjustments.
- Accessibility coordinator (required, if you must appoint one). Name, phone and email.
- How to report a problem or request an adjustment (required). I recommend more than one way, such as phone and email, and a line saying how soon you reply.
Sample statement
A short draft to start from. Replace the square brackets with your details, and delete any sentence that isn't true for your site.
Accessibility statement
Last updated: [date]
[Business name] is committed to giving everyone, including people with disabilities, equal access to its services. This statement covers [site address].
Accessibility level
[Business name] is working to meet Israeli Standard 5568 at level AA. Accessibility is ongoing work, and some parts of the site may not be fully accessible yet.
What has been done
- [Example: images that convey information have alt text.]
- [Example: the site and its forms can be used with a keyboard alone.]
- [Example: videos on the site have captions.]
How it was checked
On [date] the site was checked [with an automated test / manually with a keyboard and a screen reader] by [name].
Known limitations
- [Example: PDFs uploaded before [year] are not accessible yet. You can ask for them in an accessible format by phone or email below.]
Accessibility contact
- Accessibility coordinator: [name, if any]
- Phone: [number]
- Email: [address]
[Business name] replies to accessibility requests within [number] working days.
Common mistakes
- Copying another site's statement. The structure can be similar, but the content must describe your site. A copied statement usually lists adjustments you never made, or someone else's contact details.
- Saying the site is "fully accessible" with no audit to back it. It doesn't help visitors, and if it's untrue it can work against you.
- Describing only the accessibility widget. "An accessibility menu is installed" says nothing about adjustments to the content itself. I wrote a separate guide on accessibility widgets.
- Contact details nobody checks. After a notice about a problem, the fix is due within 60 days at most (regulation 35A(d)(1)). An unread inbox wastes that time.
- A link that's hard to find. The regulation requires "a prominent place". The usual practice is an "Accessibility statement" link in the footer of every page, sometimes also in the menu.
- A statement that never changes. When you add pages, forms or videos, update the statement and its date too.
The risk of not having one
Not publishing an accessibility statement (regulation 35E) is on the list of breaches for which the Commission may impose an administrative fine (section 26G of the Law and the Eighth Schedule, part A, item 12). Under the updated text of the Law, the 2026 amounts are ₪1,310 where annual turnover is up to ₪2 million, ₪3,830 for ₪2–20 million, and ₪13,680 above that and for public authorities. Until 10 August 2027, a business with turnover up to ₪20 million that isn't a public authority gets an administrative warning instead of a fine for a first breach (section 26R(a)(3) of the Law). It is a power of the Commission's officer, not an automatic fine, and you can submit arguments before a decision.
The other risks, including lawsuits with compensation without proof of damage, are in my guide to who must comply and the exemptions.
How my checker can help
I built a free accessibility checker that checks one page of your site. Among other things it shows whether it found a link to an accessibility statement on that page.
The full report includes a statement generator: after the check you fill in the business name, contact person, phone and email, and get a draft in Hebrew and English. The "found in order" list is built only from checks that passed, and "known limitations" from the issues found. It is a draft: review it and add what an automated check can't know.
Free check, and a full report if you need it
- Free check: a score, the most serious issues on the page, and whether a statement link and an overlay widget were found.
- Full report, US$29 per site, one-time: every issue found, how to fix it with example code, and an accessibility statement draft in Hebrew and English.
Automated checks find only part of accessibility issues. This is not a compliance certificate and not legal advice.
Common questions
Does every website need an accessibility statement?
Anyone obligated to make internet services accessible must publish a statement under regulation 35E. A VAT-exempt dealer, or anyone whose average annual turnover is up to ₪100,000, is exempt "from making accessibility adjustments under this part" (regulation 35F(g)). I found no explicit wording on whether that exemption also covers the statement, so in that case ask a lawyer. A short, honest statement with a contact method does no harm even where it isn't required.
Is there an official template?
The regulations don't set a mandatory wording. Regulation 35E lists what the statement must include, not the words. That's why it should describe the real state of your own site.
Where should the link go?
The regulation requires "a prominent place" on the site, and in the app if there is one. The usual practice is a link in the footer of every page with plain text: "Accessibility statement".
Can an accessibility widget replace the statement?
No. The statement is a separate requirement under regulation 35E, and a widget doesn't replace adjustments to the content either. See my guide on accessibility widgets.
Sources
- תקנות שוויון זכויות לאנשים עם מוגבלות (התאמות נגישות לשירות), התשע״ג–2013 (Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013), consolidated text, PDF on the National Insurance Institute site
- The same regulations, updated text with Reshumot references (Hebrew Wikisource)
- חוק שוויון זכויות לאנשים עם מוגבלות, התשנ״ח–1998 (Equal Rights for Persons with Disabilities Law, 1998), updated text, Hebrew Wikisource
- ת״י 5568 חלק 1 (IS 5568 part 1, September 2023: website accessibility), PDF on gov.il
- ת״י 5568 חלק 2 (IS 5568 part 2, September 2023: digital documents), PDF on gov.il
- כל זכות: הנגשת אתרי אינטרנט ואפליקציות (Kol Zchut, website and app accessibility; secondary source)
