Skip to main content
document-accessibility

Digital Document Accessibility: Israeli Standard 5568 Part 2

By טוביה שיינפלד May 26, 2026 3 views

What does Israeli Standard 5568 Part 2 require for digital document accessibility?

Israeli Standard 5568 Part 2 requires digital documents to be accessible according to the standards of the software that created them—Word by Microsoft standards, PDF by Adobe standards, and so on. Public bodies are fully obligated; private organizations must comply when documents relate to public services. Use built-in tools like Word's Accessibility Checker or Adobe Acrobat's Accessibility Check to verify compliance.

Did you know:

Israeli Standard 5568 Part 2 requires digital documents to be accessible according to the standards of the software that created them—Word follows Microsoft guidelines, PDFs follow Adobe standards, and so on. Public bodies are fully obligated; private organizations must comply when documents relate to public services.

In the digital age, digital documents are an integral part of business and public communication. But did you know that these documents also have legal accessibility requirements? This article clarifies the legal obligations surrounding digital document accessibility.<\/p>\r\n

Israeli Standard 5568 Part 2 - Documents<\/h2>\r\n

According to Israeli Standard 5568 Part 2, digital documents must be accessible. However, the requirement is unique and tailored to the technological nature of the documents.<\/p>\r\n

The Guiding Principle: Accessibility by Software Standards<\/h3>\r\n
    \r\n
  • Word document<\/strong> – according to Microsoft Word guidelines<\/li>\r\n
  • PowerPoint presentation<\/strong> – according to PowerPoint guidelines<\/li>\r\n
  • Excel file<\/strong> – according to Excel guidelines<\/li>\r\n<\/ul>\r\n

    Why Does This Approach Make Sense?<\/h2>\r\n
      \r\n
    • Technology alignment:<\/strong> Each software includes specialized rules<\/li>\r\n
    • Technological currency:<\/strong> The standard stays updated with software releases<\/li>\r\n
    • Practicality:<\/strong> No need to learn new guidelines repeatedly<\/li>\r\n<\/ul>\r\n

      Practical Examples of Document Accessibility<\/h2>\r\n

      Accessible Word Documents<\/h3>\r\n
        \r\n
      • Using Styles for headings<\/li>\r\n
      • Alt Text for images<\/li>\r\n
      • Descriptive hyperlinks<\/li>\r\n
      • Avoiding reliance on color alone<\/li>\r\n<\/ul>\r\n

        Accessible PDF Files<\/h3>\r\n
          \r\n
        • Using PDF tags<\/li>\r\n
        • Setting reading order<\/li>\r\n
        • Tagging form fields<\/li>\r\n
        • Ensuring adequate contrast<\/li>\r\n<\/ul>\r\n

          Accessible PowerPoint Presentations<\/h3>\r\n
            \r\n
          • Using pre-built slide layouts<\/li>\r\n
          • Using readable fonts<\/li>\r\n
          • Avoiding flashing animations<\/li>\r\n
          • Adding table of contents and clear structure<\/li>\r\n<\/ul>\r\n

            Who Must Ensure Document Accessibility?<\/h2>\r\n
              \r\n
            • Public bodies:<\/strong> Full obligation<\/li>\r\n
            • Private entities:<\/strong> Obligation if documents are related to public service<\/li>\r\n<\/ul>\r\n

              Relevant cases:<\/h3>\r\n
                \r\n
              • Contracts, forms, and manuals<\/li>\r\n
              • Public reports<\/li>\r\n
              • Procurement documents<\/li>\r\n<\/ul>\r\n

                Tools for Accessibility Testing<\/h2>\r\n

                Built-in tools:<\/h3>\r\n
                  \r\n
                • Word / PowerPoint / Excel: Accessibility Checker<\/li>\r\n
                • Adobe Acrobat: Accessibility Check<\/li>\r\n<\/ul>\r\n

                  Manual testing:<\/h3>\r\n
                    \r\n
                  • Testing with a screen reader<\/li>\r\n
                  • Keyboard-only navigation testing<\/li>\r\n
                  • Color contrast testing<\/li>\r\n<\/ul>\r\n

                    Common Challenges<\/h2>\r\n
                      \r\n
                    • Difficulty converting legacy documents<\/li>\r\n
                    • Need for employee training<\/li>\r\n
                    • Ongoing maintenance of new documents<\/li>\r\n<\/ul>\r\n

                      Practical Recommendations<\/h2>\r\n

                      For management:<\/h3>\r\n
                        \r\n
                      • Train your employees<\/li>\r\n
                      • Establish procedures<\/li>\r\n
                      • Conduct regular testing<\/li>\r\n<\/ul>\r\n

                        For employees:<\/h3>\r\n
                          \r\n
                        • Learn to use built-in tools<\/li>\r\n
                        • Plan for document accessibility from the start<\/li>\r\n
                        • Test before publishing or sending<\/li>\r\n<\/ul>\r\n

                          Summary<\/h2>\r\n

                          Israeli Standard 5568 Part 2 requires that digital documents be accessible in accordance with the standards of the software that created them. This is a practical approach tailored to different technologies.<\/p>\r\n

                          Investing in document accessibility is not just a legal duty—it elevates service quality and transparency for all members of the public.<\/p>\r\n

                          Remember: An accessible document is one that everyone can use—and that benefits everyone.<\/p>

Frequently asked questions

Updated:

Ready to make your site accessible?

Run a free WCAG 2.1 AA / ADA scan or talk with our team

Ready to make your site accessible?

Leave your details and we'll get back to you with a custom offer — no commitment