"We already comply with WCAG" and "our site complies with Standard 5568" sound like the same statement โ€” but theyโ€™re not exactly identical, and the difference matters when it comes to compliance with Israeli law. In this article, weโ€™ll explain how the two standards connect, whatโ€™s legally mandatory, and what goes beyond the requirement but is still highly recommended.

In short โ€” what this guide covers

  1. How 5568 and WCAG connect
  2. Whatโ€™s mandatory: level AA
  3. Whatโ€™s recommended: beyond the legal requirement
  4. How this applies to documents too

How 5568 and WCAG connect

WCAG (Web Content Accessibility Guidelines) is an international standard published by the W3C that defines technical criteria for digital content accessibility. SI 5568 is the Israeli standard, which adopts WCAGโ€™s principles and guidelines and adapts them to the local regulatory framework โ€” itโ€™s the standard that Israeli regulations actually point to in order to define what "accessibility" means legally.

WCAG is built around four principles sometimes called POUR: Perceivable โ€” content that can be sensed in some way, Operable โ€” an interface that can be operated even without a mouse, Understandable โ€” content and interface that are predictable and clear, and Robust โ€” compatibility with assistive technologies like screen readers.

Whatโ€™s mandatory: level AA

Of the three compliance levels WCAG defines (A, AA, and AAA), level AA is the mandatory threshold under Israeli regulation for most bodies โ€” public and private alike. Itโ€™s the level actually tested when checking compliance with the standard, and itโ€™s the level our tool checks against by default.

Thereโ€™s relief available for very small businesses: businesses with an especially low revenue turnover can request a partial exemption that lowers the requirement to level A only. The exact threshold for this exemption is updated from time to time, so we wonโ€™t cite a fixed figure here โ€” itโ€™s worth checking the current amount with the Commission for Equal Rights of Persons with Disabilities before relying on it.

WCAG itself has been updated since the Israeli standard first adopted it: WCAG 2.1 (2018) added criteria relevant mainly to mobile and cognitive disabilities, and WCAG 2.2 (2023) added further requirements around interactive interfaces. Not all of these newer criteria have formally become mandatory under the current version of the Israeli standard โ€” but they represent the direction regulation is heading, and building to them today saves expensive rework later.

Level AAA โ€” the highest level in WCAG โ€” is also not mandatory, but itโ€™s worth adopting specific criteria from it (like higher contrast or simpler language) for critical content, such as forms or legal documents.

How this applies to documents too

The exact same logic applies to digital documents โ€” not just web pages. SI 5568 Part 2 applies WCAGโ€™s principles to PDF, Word, and other document files: structure tags, hierarchical headings, alt text for images, and a logical reading order โ€” exactly what screen readers need to "understand" a document. Thatโ€™s why our tool checks the exact same criteria for documents too, not just for the website itself.

๐Ÿ’ก Practical tip

Want to check basic compliance yourself? Start with the simple question: can you navigate the entire site (and every document) using only the keyboard, with no mouse at all? If not โ€” thatโ€™s already a strong indication of a gap from level AA.

โš–๏ธ Legal disclaimer

The information in this article is provided for general informational purposes only and does not constitute legal advice. Itโ€™s recommended to consult an attorney who specializes in accessibility and to check the current version of SI 5568 on the Standards Institution of Israel website.

Want to check exactly where your documents stand?

Our tool automatically checks every document against AA criteria, and shows you exactly where the gaps are.

Get a Free Check โ†