The short answer: Israeli Standard 5568 (IS 5568) is Israel’s web accessibility standard. It is based on the W3C’s WCAG guidelines with a few national adjustments, and Israel’s accessibility regulations require most websites to meet it at level AA. In practice that means meeting every level A and level AA success criterion, and publishing an accessibility statement that matches the site.
I have been auditing and fixing websites against IS 5568 for 9+ years, for Israeli organizations and for international companies that start serving customers in Israel. Below is what the standard actually asks for, and the issues we keep finding when we test real sites.
IS 5568 was published on 26.10.2017. It gives website owners a clear guideline: what to check and what to do so people with disabilities can use the site. It is based on WCAG, with national adjustments, mainly around time-based media such as video and audio.
When we explain it to clients, we put it simply: the standard is not a design trend or a plug-in setting. It describes how the site has to work for someone using a screen reader, a keyboard only, screen magnification or captions.
WCAG has three levels: A, AA and AAA. The Israeli standard asks you to meet level AA, which means meeting all of level A and all of level AA. Level A is the base layer, AA builds on top of it.
Some examples of what each level covers:
Level A
lang attribute.Level AA adds
In our audits the same problems come up again and again, on large sites and small ones:
Most of these are not hard to fix once you know where they are. The hard part is finding them, and that takes a manual check with real assistive technology, not only an automated scan.
IS 5568 is based on WCAG, and newer WCAG versions (2.1 and 2.2) add criteria for mobile use, low vision and cognitive needs. My advice to international teams is to build and test to WCAG 2.2 AA. One round of work then covers the Israeli standard and most international requirements, including the EU’s EN 301 549. For the background on the three levels, see our WCAG guidelines overview, or the official W3C WCAG 2 overview (opens in a new tab).
This is where foreign teams usually miss things:
lang="he" and dir="rtl" on Hebrew pages. An English word in the middle of a Hebrew sentence is fine, but it should be marked with its own language so the screen reader pronounces it correctly.Israel’s regulations require an accessibility statement (regulations 34 and 35). As I tell every client: no one is exempt from publishing one. If your organization has a specific exemption, you state it inside the statement.
A good statement usually follows this order:
Write it for your actual site. A statement copied from another website, describing features you don’t have, does more harm than good.
Our experts handle this end to end for Israeli and international clients. You can see everything we do on our accessibility services page.
It is based on WCAG at level AA, with national adjustments, mainly for time-based media. A site that meets WCAG 2.1 or 2.2 AA covers it in practice.
If you offer a service to the public in Israel through a website, it is likely to be relevant. Check your specific situation with a legal adviser; our part is the technical work and the documentation.
Yes. Documents published on the site are expected to be accessible as well.
No. A plug-in changes how the page looks, but problems in the code, such as missing labels or a broken focus order, still have to be fixed in the site itself.
This website uses essential cookies to operate and, with your consent, statistics cookies (Google Analytics). For more details, see our Privacy Policy.