Website accessibility under Israeli law: what's required, what gets checked and how to comply

Website accessibility in Israel isn't a recommendation, it's a legal requirement. The service accessibility regulations issued under the Equal Rights for Persons with Disabilities Law apply Israeli Standard SI 5568, which adopts the international accessibility guidelines WCAG 2.0 at level AA, to websites that serve the public. What this means in practice: a business website that isn't accessible is exposed to lawsuits, and it loses both customers and points with Google. In this guide we'll go over what the law requires, what actually gets checked, why an accessibility button alone isn't enough, and how to build a site that meets the requirements from the ground up. It's also the standard we work to when we build business websites: accessibility is built into the code itself, not stuck on at the end.

What the law actually requires

The legal framework is built in three tiers. At the top: the Equal Rights for Persons with Disabilities Law, which sets the principle of the right to equal service. Below it: the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013, which extend the obligation to services provided online as well. And at the bottom, on the technical level: Israeli Standard SI 5568, which refers to the WCAG 2.0 guidelines at level AA and defines what an "accessible website" actually is. In addition to meeting the standard, you're required to publish an accessibility statement on the site that details the accessibility arrangements and how to contact the accessibility coordinator.

It's important to be honest here: the regulations include distinctions and partial exemptions, for example by the size of the business and its turnover, and the details vary from case to case. This article isn't legal advice, and if you want certainty about your exact obligations, consult a qualified professional. What doesn't vary from case to case: an accessible website is in your business's interest, plain and simple, even without the shadow of a lawsuit.

What gets checked on an accessible website: the practical list

• Keyboard navigation: every action on the site (menus, forms, buttons) must be possible without a mouse, with a visible focus indicator.
• Alt text for images: every image that carries information needs a description (alt) that a screen reader can read aloud.
• Color contrast: a sufficient contrast ratio between text and background, so people with low vision can read comfortably too.
• Correct heading structure: a logical hierarchy of headings that lets a screen reader jump between parts of the page.
• Labeled forms: every input field is tied to a clear label, and error messages are explained in words, not just in color.
• Video and audio: captions for videos and full control over media playback.
• Screen reader compatibility: correct use of semantic elements and ARIA attributes where needed.
• Accessibility statement: a dedicated page, available from anywhere on the site, detailing the arrangements and contact details. Here's our statement, if you want a live example.

Why an accessibility button alone doesn't solve the problem

The temptation is understandable: you paste in an accessibility plugin's script, get a floating button with a wheelchair icon, and move on. But a plugin sitting on top of an inaccessible site is like a ramp that ends in a step: it enlarges text and changes contrast, but it can't invent alt text for images, doesn't fix a form without labels, and doesn't turn a menu that breaks with the keyboard into a menu that works. Real accessibility lives in the code itself: in the semantic structure, the heading hierarchy, the contrast chosen in the design. A plugin is a legitimate addition on top of a sound foundation, not a substitute for it. This is another fundamental advantage of a custom-coded site over a plugin-heavy template, as we explain in detail in our comparison of custom code and WordPress.

The bonus nobody tells you about: good accessibility boosts your rankings on Google

Here's a trade secret: the list Google loves and the list the standard requires overlap remarkably well. A correct heading structure helps a screen reader and also helps the search engine understand the page. Alt text for images serves blind users and also image search. Clean semantic code loads faster and gets parsed better. A site built to be truly accessible gets, for free, a large part of the work laid out in our checklist for building an SEO-friendly website. And in an era when search engines and AI engines read websites like sophisticated screen readers, this investment grows stronger year after year, as we explain in more depth in our guide to SEO for AI engines.

How to meet the requirements without a headache

If the site doesn't exist yet, the cheapest way is to build it accessible from day one: choose a team for whom accessibility is part of the development process and not a line item at the end. If you have an existing site, the right order is a methodical check against the standard's list, fixing the core in the code (headings, forms, contrast, keyboard), adding an accessibility widget as an extra, and publishing an accessibility statement. Just as important: every new piece of content added to the site, including landing pages for campaigns, has to meet the same standard, a point worth remembering when you read our guide to landing pages vs full websites.

Frequently asked questions

Does every website in Israel have to be accessible?

The accessibility regulations apply to websites that serve the public, and most business websites fall under that definition. There are relief provisions and partial exemptions that depend, among other things, on the size of the business and its turnover, so get the exact answer for your case from a qualified advisor. What's certain: relying on "we're small, nobody will come after us" is a gamble, not a strategy.

What is Israeli Standard SI 5568?

Israeli Standard SI 5568 is the standard that defines the accessibility of web content in Israel. It adopts the international WCAG 2.0 guidelines and sets level AA as the required bar. In practice, it translates into a list of technical requirements: keyboard navigation, alt text, contrast, heading structure, labeled forms and screen reader compatibility.

Is an accessibility plugin enough to comply with the law?

In most cases, no. A plugin changes the display but doesn't fix structural flaws in the code: images without alt text, forms without labels and menus that don't work with the keyboard stay as they are. Compliance with the standard is measured on the site itself, so the foundation must be accessible in the code, and the plugin can serve as an extra layer of convenience on top.

What should an accessibility statement include?

The statement details the accessibility level of the site and the service, the existing arrangements, known limitations if there are any, and the contact details of the person who handles accessibility inquiries in the business. It should be easy to reach from every page of the site, and be updated when the site changes.

Does accessibility affect SEO?

Yes, indirectly but consistently. The main accessibility requirements (a correct heading structure, alt text, semantic code and clear forms) are exactly the signals that help search engines understand and rank pages. An accessible site is almost always also a site that's easier for the search engine to read, so the investment serves both goals at once.

The bottom line

Website accessibility in Israel is a legal obligation that's also an opportunity: a site built to SI 5568 serves more customers, gets along better with Google and lets you sleep better at night. At VeloLinx we build every site with accessibility in the code itself, from the first heading to the last form, including a proper accessibility statement. Want to know where your site stands, or build a new one that meets the requirements from the ground up? Take a look at our website development service or talk to us, and we'll be happy to look into it together.