Accessibility law · Middle East & Africa
Israel IS 5568 → WCAG 2.0 AA
In Israel, the standard to meet is IS 5568 → WCAG 2.0 AA. It binds public bodies and most businesses that serve the public online, except the smallest. This page was reviewed against primary sources on 30 September 2026.
- Standard
- IS 5568 → WCAG 2.0 AA
- Private sector
- Covered
- Accessibility statement
- Required
- Latest
- Oct 2017
- Reviewed
- 30 September 2026
Scope
Who it applies to
Any public body or business that offers a public service, or information about one, online must make its websites, documents and apps meet Israeli Standard 5568 (based on WCAG 2.0) at level AA and display an accessibility statement. Businesses with average yearly turnover up to NIS 100,000 are exempt. Courts can award up to NIS 50,000 per tort without proof of harm (index-linked), and since August 2023 the Commission can also impose administrative fines.
Public sector
Every public body that serves the public. The law's 'public authorities' include listed public bodies, state health service providers, official educational institutions and public institutions more than 30% funded by the state. Public authorities must also caption prerecorded video, whatever their size.
Private sector
CoveredVery broad. The duty covers anyone providing a 'public service', which includes the sectors in the law's Second Schedule: health, entertainment, education and leisure, welfare, sport, tourism, transport, culture, hospitality, commerce, religion, energy, telecommunications, and banking, credit, insurance, pensions and other financial services. Businesses that are VAT-exempt dealers or have average annual turnover up to NIS 100,000 are exempt, and captions are required only above NIS 5 million average turnover.
Coverage
What it covers
Websites are only part of it. Each tile says whether these rules reach that kind of product, with the detail.
Websites
CoveredMust meet IS 5568 at level AA.
Mobile apps
CoveredIsraeli app standard if one exists, otherwise the web standard's criteria on at least two common operating systems; exempt if the same service is on an accessible mobile site.
Documents
CoveredDocuments such as PDFs prepared from 26 October 2017 must be accessible; online forms regardless of date.
Software
Not coveredDesktop software is not addressed by the internet rules.
Kiosks and terminals
CoveredRegulation 25 covers vending, payment, information and banking machines: IS 1918 Part 4, plain-language and audio instructions, at least a third of identical machines.
Public procurement
UnclearNo procurement rule found in the sources checked.
Timeline
Deadlines
Every date here is already in force.
Dates move, so check the linked source before you plan around one.
7 Oct 2005 In force
The accessibility chapter of the law (Amendment 2) takes effect, including damages without proof of harm.
25 Oct 2013 In force
The Service Accessibility Regulations take effect, six months after publication on 25 April 2013.
13 Oct 2016 In force
An amendment moves the deadline for existing websites from 25 October 2016 to 26 October 2017.
26 Oct 2017 In force
Deadline for existing sites; new regulations 35A to 35F take effect (standard, documents, apps, captions, statement, exemptions).
26 Oct 2020 In force
The temporary exemption for businesses with turnover up to NIS 300,000 ends.
1 Jan 2022 In force
Personal documents behind a login prepared from this date must be accessible.
10 Aug 2023 In force
Administrative fines and warnings under Amendment 23 become available to the Commission.
Instruments
The law in Israel
4 laws, rules and rulings, oldest first. Each links to its primary source.
Every fact points at a primary source. Dates move, and several moved in 2025 and 2026, so check the source before you rely on one.
1998
Equal Rights for Persons with Disabilities Law, 5758-1998
Chapter E1 (accessibility) added by Amendment 2, 2005; administrative enforcement added by Amendment 23, 2022
Gives disabled people a right of access to public services offered by public bodies and listed private sectors, and makes breaches of the accessibility rules a civil tort with damages of up to NIS 50,000 without proof of harm. Since 2023 the Commission can also impose administrative fines.
2013
Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013
K.T. 7240, 25 April 2013; made under s. 19L (19יב) of the law
Detailed accessibility duties for public services. The original regulation 35 required internet services to follow the Israeli standard, or else W3C WCAG, at level AA; regulation 25 covers self-service machines.
Oct 2017 Latest
Regulations 35A to 35F (35א–35ו), internet services
K.T. 7876, 26 October 2017, replacing regulation 35
The current web rules: websites and documents must meet the internet accessibility standard, IS 5568, at level AA; apps follow the app standard or the web criteria on two common platforms; accessibility statement; captions for public bodies and entities above NIS 5 million turnover; turnover and technology exemptions; 60-day notice-and-fix rule.
May 2021
IS 5568 Part 1 (2021): Guidelines for accessibility of internet content
Standards Institution of Israel; regulations refer to it as amended from time to time
The May 2021 edition of Part 1 adopts WCAG 2.0 (11 December 2008) with some Israeli changes, including to the time-based media criteria. Level AA is what the regulations require.
Enforcement
Enforcement and penalties
Who enforces
The Commission for Equal Rights of Persons with Disabilities, headed by the Commissioner.
How
The Commissioner can issue accessibility orders. Since 10 August 2023 a senior Commission official can impose administrative fines or give administrative warnings, and the Commission can also sue. Disabled people can bring civil claims, including class actions.
Penalties
Courts can award up to NIS 50,000 per tort without proof of damage; the amount is index-linked to the consumer price index from February 2005, and senior officers can be personally liable unless they show they did not know and took reasonable steps. Administrative fines for website and app failures (Eighth Schedule, Part C) are NIS 3,940 for micro, NIS 14,220 for small and NIS 41,030 for other entities; for a missing accessibility statement (Part A) they are NIS 1,310, NIS 3,830 and NIS 13,680. Fines are indexed every 1 January.
Individuals
Yes. Breaching the accessibility rules is a civil tort, and a disabled person can sue without proving damage; class actions are possible. Under regulation 35A(d), a deviation from the web rules is not a breach unless the entity was notified and failed to fix it within a reasonable time of no more than 60 days.
Accessibility statement
A statement is required
Every covered website and app must display, in a prominent place, an accessibility statement that follows IS 5568. It must describe the adjustments made, give the contact details of the accessibility coordinator where the law requires one, and explain how to report missing accessibility or request an adjustment. Any exemption and the alternative arrangements must also be published there. No update deadline is set.
Exemptions
What is exempt
Exemptions are narrow and usually have to be claimed and explained, not assumed.
- VAT-exempt dealers and entities with average annual turnover up to NIS 100,000.
- Average turnover up to NIS 300,000: temporary exemption, ended 26 October 2020.
- Average turnover of NIS 1,000,000 or less: exempt for a site or app it began operating before the rules took effect, if its contact details for getting the service are published accessibly; valid three years and renewable.
- Technological limits certified by a service accessibility auditor on expert opinion: up to three years, renewable once, with alternative access and disclosure in the statement.
- Features a social network platform does not allow.
- Services open only to pre-registered users with at most 500 simultaneous participants, unless a disabled person asks.
- Documents prepared before 26 October 2017, except online forms and documents explaining them prepared after 26 October 2015.
- Third-party content the entity does not edit or produce, provided it offers accessible tools such as an image-description field.
- Captions are required only from public bodies and entities with average turnover above NIS 5 million; recorded conferences and lectures may use a transcript.
- Advertising, if an accessible alternative for the service information exists.
- Undue burden and other exemptions under the law, with alternative adjustments where reasonable.
The standard
What WCAG 2.0 Level AA asks for
38 success criteria: 25 at Level A and 13 at Level AA. 4.1.1 Parsing counts in this version, but WCAG 2.2 removed it as obsolete, so it has no page here.
1. Perceivable
- 1.1.1Non-text ContentA
- 1.2.1Audio-only and Video-only (Prerecorded)A
- 1.2.2Captions (Prerecorded)A
- 1.2.3Audio Description or Media Alternative (Prerecorded)A
- 1.2.4Captions (Live)AA
- 1.2.5Audio Description (Prerecorded)AA
- 1.3.1Info and RelationshipsA
- 1.3.2Meaningful SequenceA
- 1.3.3Sensory CharacteristicsA
- 1.4.1Use of ColorA
- 1.4.2Audio ControlA
- 1.4.3Contrast (Minimum)AA
- 1.4.4Resize TextAA
- 1.4.5Images of TextAA
2. Operable
- 2.1.1KeyboardA
- 2.1.2No Keyboard TrapA
- 2.2.1Timing AdjustableA
- 2.2.2Pause, Stop, HideA
- 2.3.1Three Flashes or Below ThresholdA
- 2.4.1Bypass BlocksA
- 2.4.2Page TitledA
- 2.4.3Focus OrderA
- 2.4.4Link Purpose (In Context)A
- 2.4.5Multiple WaysAA
- 2.4.6Headings and LabelsAA
- 2.4.7Focus VisibleAA
3. Understandable
- 3.1.1Language of PageA
- 3.1.2Language of PartsAA
- 3.2.1On FocusA
- 3.2.2On InputA
- 3.2.3Consistent NavigationAA
- 3.2.4Consistent IdentificationAA
- 3.3.1Error IdentificationA
- 3.3.2Labels or InstructionsA
- 3.3.3Error SuggestionAA
- 3.3.4Error Prevention (Legal, Financial, Data)AA
4. Robust
Beyond the law
18 Level A and AA criteria in WCAG 2.2 that these rules do not require yet. Meeting them now costs little and is where the rules are heading.
- 1.3.4OrientationAANew in 2.1
- 1.3.5Identify Input PurposeAANew in 2.1
- 1.4.10ReflowAANew in 2.1
- 1.4.11Non-text ContrastAANew in 2.1
- 1.4.12Text SpacingAANew in 2.1
- 1.4.13Content on Hover or FocusAANew in 2.1
- 2.1.4Character Key ShortcutsANew in 2.1
- 2.4.11Focus Not Obscured (Minimum)AANew in 2.2
- 2.5.1Pointer GesturesANew in 2.1
- 2.5.2Pointer CancellationANew in 2.1
- 2.5.3Label in NameANew in 2.1
- 2.5.4Motion ActuationANew in 2.1
- 2.5.7Dragging MovementsAANew in 2.2
- 2.5.8Target Size (Minimum)AANew in 2.2
- 3.2.6Consistent HelpANew in 2.2
- 3.3.7Redundant EntryANew in 2.2
- 3.3.8Accessible Authentication (Minimum)AANew in 2.2
- 4.1.3Status MessagesAANew in 2.1
Meeting it
Where to start
The standard named here is WCAG 2.0 Level AA.
- Audit your pages against WCAG 2.0 Level AA: 38 success criteria at Level A and AA.
- Check text and control contrast in the Contrast Checker.
- Run the URL Analyzer for the problems a machine can find, then test with a keyboard and a screen reader.
- Publish an accessibility statement that says what does not meet the standard yet, and how to report a problem.
- Work through the Accessibility Checklist and keep a record of what you tested.
This is a summary to orient you, not legal advice. For a decision that matters, read the primary sources and ask a lawyer who practices there.
Questions
Common questions
Does it apply to private companies?
Yes, unusually broadly. Any business that provides a public service in the listed sectors, such as commerce, banking, insurance, telecoms, health, tourism or entertainment, and offers it or information about it online must comply, unless its average annual turnover is NIS 100,000 or less or it is a VAT-exempt dealer.
Which WCAG version applies?
The regulations require IS 5568 at level AA, 'as amended from time to time'. The 2021 edition of IS 5568 Part 1 is based on WCAG 2.0 with Israeli changes. The regulations do not name a newer WCAG version.
Can we be sued over a single accessibility bug?
Under regulation 35A(d), a deviation from the web rules is not a breach unless you were notified and did not fix it within a reasonable time, no later than 60 days, and you must offer an alternative in the meantime. Once it is a breach, a court can award damages without proof of harm, up to NIS 50,000 per tort, index-linked.
Do apps have to be accessible?
Yes. Apps must meet an Israeli app standard if one exists; until then they must meet the web standard's success criteria as far as relevant, on at least two common operating systems. An app is exempt if the identical service is available on an accessible mobile website and the app links to it.
Do we need an accessibility statement?
Yes. It must be prominent on the site and in any app, describe the adjustments made, give the accessibility coordinator's details where one is required, explain how to report problems or request adjustments, and disclose any exemption.
Sources
Sources
Every fact on this page comes from one of these; the few secondary sources are marked. Reviewed 30 September 2026.
- Equal Rights for Persons with Disabilities Law, 5758-1998, consolidated Hebrew text (Nevo) nevo.co.il
- Same, Internet Archive copy read (July 2026) web.archive.org
- Service Accessibility Adjustments Regulations, 5773-2013, consolidated Hebrew text (Nevo) nevo.co.il
- Same, Internet Archive copy read (January 2026) web.archive.org
- Unofficial English translation of the 2013 regulations as published (UN DESA) un.org
- Unofficial English translation of the 1998 law as enacted (UN DESA) un.org
- IS 5568 Part 1 (2021), copy hosted by the Israel Internet Association (Internet Archive copy read) web.archive.org
- Knesset committee background document on the 2017 amendment fs.knesset.gov.il
- Bar Law: Revision of the regulations requiring websites and applications to be accessible (secondary) barlaw.co.il
Elsewhere
Other jurisdictions
- USUnited StatesWCAG 2.1 AA (ADA Title II, HHS Section 504) — Section 508 still WCAG 2.0 AA
- CACanadaCAN/ASC-EN 301 549:2024 → WCAG 2.1 AA (federal, from Dec 2027) — Ontario AODA: WCAG 2.0 AA
- BRBrazilLBI art. 63 → "international guidelines"; eMAG 3.1 for government; ABNT NBR 17225:2025 (WCAG 2.2) voluntary
- EUEuropean UnionEN 301 549 V3.2.1 → WCAG 2.1 AA
- UKUnited KingdomWCAG 2.2 AA
- FRFranceRGAA 4.1.2 → WCAG 2.1 AA
- DEGermanyBITV 2.0 → EN 301 549 → WCAG 2.1 AA
- ITItalyAgID guidelines → EN 301 549 → WCAG 2.1 AA
- ESSpainEN 301 549 V3.2.1 → WCAG 2.1 AA
- NLNetherlandsEN 301 549 → WCAG 2.1 AA
- IEIrelandEN 301 549 V3.2.1 → WCAG 2.1 AA
- NONorwayEN 301 549 V3.2.1 → WCAG 2.1 AA (public); WCAG 2.0 AA less 3 criteria (private)
- CHSwitzerlandeCH-0059 v3.0 → WCAG 2.1 AA
- INIndiaGIGW 3.0 → WCAG 2.1 AA · IS 17802
- JPJapanJIS X 8341-3:2016 → WCAG 2.0 AA
- KRSouth KoreaKWCAG 2.2 (KS X OT0003:2022)
- CNChinaGB/T 37668-2019 (recommended; draws on WCAG 2.0 and 2.1)
- AUAustraliaWCAG 2.2 AA for government — the DDA names no standard
- NZNew ZealandWeb Accessibility Standard 1.2 → WCAG 2.2 AA