Skip to main content

Israeli Standard 5568: What It Requires From Your Website

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.

What is Israeli Standard 5568?

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.

What does level AA mean under IS 5568?

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

  • A text alternative for every image, icon or visual element that carries a message.
  • Full keyboard navigation, with no point where the user gets stuck.
  • A visible pause or stop button for anything that plays on its own, such as a slider or video.
  • No more than three flashes per second.
  • A skip link to the main content, so screen reader users don’t hear the whole menu on every page.
  • The page language set with the lang attribute.

Level AA adds

  • Text that can be enlarged to 200% without losing content.
  • No text inside images, so the message is available as live text.
  • At least two ways to reach a page, for example a menu and a search, or a menu and a site map.
  • Clear, hierarchical headings and clear instructions on forms.
  • Sufficient color contrast.

Which issues do we find most often in IS 5568 audits?

In our audits the same problems come up again and again, on large sites and small ones:

  1. Images that carry information but have no alt text.
  2. Text that is part of an image instead of live text, so a screen reader never reaches it.
  3. Headings that are not marked as headings, or that skip levels.
  4. A reading and focus order that jumps around the page.
  5. Form fields with no label, so the user doesn’t know what to type.
  6. Tables built in a way a screen reader can’t follow.
  7. Low color contrast, or a link shown only by color. If a link is red and nothing else, a color blind user may not notice it at all. Add a second signal, such as an underline.
  8. No accessibility statement, or a generic one copied from another site.

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.

How does IS 5568 relate to WCAG 2.1 and 2.2?

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).

What should international teams know about Hebrew and RTL?

This is where foreign teams usually miss things:

  • Set 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.
  • Check that arrows, carousels, icons and progress bars mirror correctly in RTL.
  • Test with Hebrew voices in NVDA, JAWS and VoiceOver, and listen to how numbers, dates and mixed English terms are read.
  • Translate alt text, form labels and error messages, not only the visible copy.

What goes into an accessibility statement in Israel?

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:

  1. A short opening about the organization and its commitment to accessibility.
  2. The accessibility adjustments made on the website.
  3. Information about any exemption, if one applies.
  4. Physical accessibility arrangements, if you serve the public at a physical location.
  5. A summary with the accessibility coordinator’s details: name, phone and email.

Write it for your actual site. A statement copied from another website, describing features you don’t have, does more harm than good.

How do you plan IS 5568 work?

  1. Audit the main templates and user journeys manually, with keyboard and Hebrew screen readers.
  2. Fix the issues in code and in content.
  3. Make documents accessible too, since PDFs and Word files on the site are part of the scope.
  4. Retest and publish the accessibility statement.
  5. Train the content team, so new pages and posts stay accessible after launch.

Our experts handle this end to end for Israeli and international clients. You can see everything we do on our accessibility services page.

FAQ

Is IS 5568 the same as WCAG?

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.

Do foreign companies need to follow IS 5568?

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.

Does IS 5568 cover PDFs and other documents?

Yes. Documents published on the site are expected to be accessible as well.

Can an accessibility plug-in make a site meet IS 5568?

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.