Accessibility compliance guides · More Global Markets

Israel IS 5568 website accessibility

Israel’s web accessibility duty sits in the Equal Rights for Persons with Disabilities Law and the service-accessibility regulations. The technical standard is Israeli Standard IS 5568, which adopts WCAG 2.0 Level AA with national modifications.

Standard: IS 5568, based on WCAG 2.0 Level AA
Legal home: Equal Rights for Persons with Disabilities Law and service accessibility regulations
Practical target: WCAG 2.1/2.2 AA, which includes the IS 5568 web criteria

What it is

The Equal Rights for Persons with Disabilities Law requires accessibility of services. The service accessibility regulations apply that duty to websites of public bodies and of organizations that provide a service to the public. IS 5568 is the standard those websites are measured against. It is based on WCAG 2.0 Level AA and adds Israeli requirements, including expectations for an accessibility statement and for Hebrew and Arabic where the service uses those languages.

Enforcement sits with the Commission for Equal Rights of Persons with Disabilities. Non-compliance can lead to orders and sanctions. An accessibility statement that claims conformance the site does not have is a problem of its own.

Because IS 5568’s web core is WCAG 2.0 AA, a site we audit to WCAG 2.2 AA meets the international criteria inside the Israeli standard and is in better shape for customers in the U.S., EU, and Canada. We still check the national items — statement, language, and document accessibility — that a generic WCAG export would skip.

Who needs to comply

Public bodies and service providers. A site that is only an internal tool is a different question from a site that is the service.

Public bodies. Government and public services whose websites are how people obtain the service.
Organizations that provide a service to the public. The regulations reach businesses and other service providers, not only ministries. The threshold details depend on the regulation that applies to your type of service.
Accessibility coordinators. Certain organizations must appoint one. We work with that person so the statement, the audit, and the fixes stay in one place.

Timeline

The regulations have been in force for years. The useful date is your last redesign.

Service accessibility regulations. Websites of covered service providers are brought under IS 5568. If your site has never been tested against it, the gap is current.
Each material change. A new template, a new checkout, or a new portal needs a new look at the standard. An old statement does not cover a new build.
When you sell abroad. WCAG 2.2 AA on the same site also serves ADA, EAA, and Canadian buyers. We map one audit to IS 5568 and to those regimes.

What the rule requires

Meet the WCAG 2.0 AA core, then the Israeli additions.

WCAG 2.0 AA as the legal core. We test WCAG 2.2 AA so the 2.0 criteria are included and the newer ones are not left for a second pass.
An accessibility statement. IS 5568 and the regulations expect a statement that describes the site’s status. We write it from the audit.
Hebrew, Arabic, and documents. Labels, errors, and PDFs have to work in the languages you publish. We include those files in the sample.
A coordinator and a contact path. Where the law requires an accessibility coordinator, the site needs a way for the public to reach them and get an alternative.

How we help

We audit to IS 5568’s WCAG core and the national items around it, then remediate in the codebase.

An audit reported against IS 5568, with WCAG 2.1/2.2 findings called out separately so you can see the legal floor and the current best practice.
An accessibility statement in the form Israeli users and the Commission expect, matched to the pages we actually tested.
Manual testing with NVDA, JAWS, and VoiceOver, plus keyboard-only use and browser zoom. The failures these rules care about are often invisible to an automated scan.
Remediation in your production code by our developers, so the fix lives in the product and not only in a report.
An accessibility statement and, where a buyer or regulator expects one, a VPAT-based Accessibility Conformance Report grounded in the audit.
Training for the people who publish pages, documents, and campaigns after the audit.
A retest after major releases, so a later deploy does not quietly undo the work.

Web accessibility audit and remediation

Our process

Confirm what applies to you. We confirm you provide a public service in Israel, which sites and languages are in scope, and whether an accessibility coordinator is already appointed.
Audit the live experience. We review the pages, flows, documents, and apps people actually use, with assistive technologies as well as automated checks, and map each finding to the standard this rule points to.
Fix the barriers that block access. Our developers remediate structure, keyboard access, forms, contrast, names, and media in your codebase, starting with the journeys that gate a service.
Document what was tested. You receive the findings, what we fixed, and the statement or conformance report your team, counsel, or procurement office needs on file.
Keep it from slipping. We train publishers and retest after significant releases so new content does not reopen the same gaps.

Frequently asked questions

Is IS 5568 identical to WCAG 2.0 AA?

The web guidelines are based on WCAG 2.0 AA, with Israeli national modifications. A plain English-language WCAG report is not a complete IS 5568 report. We include the statement, language, and document checks the standard adds.

Should we stop at WCAG 2.0 because that is what the standard cites?

2.0 AA meets the cited international core. 2.1 and 2.2 add criteria that matter on mobile and for low vision, and they are what other countries now require. We test the newer level and mark the 2.0 line clearly.

Do you work in Hebrew?

We test the interface in the languages the site publishes, including Hebrew and Arabic labels, names, and errors. Copywriting in those languages stays with your team; the accessibility of that copy is part of our audit.

Can you guarantee Commission approval?

No. We provide the audit, the fixes, and a statement that matches them. The Commission’s view of a specific complaint is not something a vendor can pre-approve.

Related guides

This page is general information from Peradeo Technologies Inc., not legal advice.

Talk with us about this requirement · hello@peradeo.com · +1 (306) 216-9934