Learn: the web, apps and software projects, explained /
Website accessibility in Israel: IS 5568 and WCAG
In Israel, website accessibility is grounded in the Equal Rights for Persons with Disabilities Law (1998) and the Service Accessibility Adjustments Regulations (2013). The technical benchmark is Israeli Standard IS 5568, which is based on WCAG 2.0 at level AA. Sites are also expected to publish an accessibility statement. This page is general information, not legal advice.
The legal framework in brief
The Equal Rights for Persons with Disabilities Law of 1998 is the foundation. The Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations of 2013 spell out accessibility adjustments for services provided to the public, and they cover information and services delivered through a website.
Whether and how the rules apply to a particular business is a legal question, and we do not answer it here. If you need certainty for your own organisation, ask a lawyer who specialises in this area. Everything on this page is general information, not legal advice.
IS 5568 and WCAG 2.0 level AA
IS 5568 is the Israeli Standard for web content accessibility. It is based on the Web Content Accessibility Guidelines, WCAG 2.0, at conformance level AA. WCAG organises its requirements under four principles: content must be perceivable, operable, understandable and robust.
In practice that means things you can test. Images have text alternatives. Text has enough contrast against its background. Every function works from the keyboard alone, with a visible focus indicator and no keyboard traps. Form fields have labels and clear error messages. Headings are structured, and the page language is declared in code.
The accessibility statement
Alongside an accessible site, the regulations call for an accessibility statement published on it. A useful statement is written in plain language and typically contains the conformance level the site aims for, any known limitations and parts that are not yet accessible, the contact details of an accessibility coordinator, and the date of the last review.
A statement is only worth publishing if it is true. It should describe what was actually reviewed and when, and be updated when the site changes. An inaccurate statement is worse than a modest honest one.
Why an overlay widget alone does not make a site accessible
Accessibility overlays are small toolbars added to a page that offer to change contrast, text size or highlight links. They can be a convenience for some visitors, but they sit on top of the page and do not repair the underlying code. Missing labels, broken keyboard navigation, unreadable structure for screen readers and inaccessible forms stay broken.
Automated scanners and overlays catch only part of the problems, because judging whether alt text is meaningful or a flow makes sense needs a human. Accessibility is a property of how the site is built and tested, not an add-on installed afterwards.
Building it in from the start
It is far cheaper in effort to design accessibility in than to retrofit it: semantic HTML, a considered colour palette, keyboard-first interaction and tested forms come naturally when planned at the start. Testing with a keyboard and a screen reader, alongside automated checks, finds what scanners miss.
We build multilingual, right-to-left-ready sites and treat accessibility as part of the engineering. We do not claim any particular site is certified; conformance is something you verify and document for your own site, ideally with specialist review.
FAQ
Does my website have to be accessible in Israel?
Israeli law and regulations require accessibility adjustments for services offered to the public, including online services. Whether and how that applies to your specific business is a legal question, so this is general information, not legal advice; check with a qualified lawyer.
What is IS 5568?
IS 5568 is the Israeli Standard for web content accessibility. It is based on WCAG 2.0 at level AA and is the technical benchmark used for website accessibility in Israel.
What should an accessibility statement include?
Typically the conformance level the site aims for, known limitations, the contact details of an accessibility coordinator, and the date of the last review. It should be written in plain language, be accurate, and be updated when the site changes.
Does an accessibility overlay or widget make my site compliant?
No. An overlay does not fix the underlying code, so missing labels, keyboard problems and screen-reader issues remain. Accessibility comes from building and testing the site properly.
Is this legal advice?
No. This page is general information to help you understand the topic. For advice about your own obligations, consult a lawyer who specialises in disability and accessibility law.