Israeli Accessibility Compliance
Trusted88/100Implement Israeli web accessibility compliance per IS 5568 standard, anchored to WCAG 2.0 AA (IS 5568 adds some 2.1-aligned criteria; sources differ), for Hebrew RTL applications. Use when user asks about Israeli accessibility law, "negishot" (accessibility), IS 5568, "teken negishot" (accessibility standard), "nachim" (disabilities), who is exempt from website accessibility, enforcement and penalties, the accessibility coordinator role, Hebrew screen reader support, RTL ARIA patterns, or accessibility audit for Israeli websites. Covers mandatory legal requirements under the Equal Rights for Persons with Disabilities Act, revenue-based exemption tiers, the two enforcement tracks (civil damages and the Commission administrative penalty) and the 60-day cure period, the accessibility coordinator role, Hebrew screen reader compatibility, and RTL-specific ARIA patterns. Do NOT use for general WCAG guidance without Israeli context (use standard a11y resources instead).
Trust score 88/100 (Trusted) · 2,484+ installs · 2 GitHub contributors · MIT license
The Israeli accessibility standard IS 5568 is anchored to WCAG 2.0 AA (some sources describe the current edition as 2.1 AA, so sources differ) and adds unique requirements for Hebrew and RTL that are not covered by international guides. Israeli businesses are legally required to comply, and non-compliance exposes them to lawsuits and Commission administrative penalties. In practice, most developers are unaware of the differences and rely on tools that do not check the Israeli-specific requirements.
skills-ilHow to use this skill
Not sure how? Read the guide- 1. Click "Download ZIP" to download the skill files.
- 2. Open Claude Desktop and go to Customize > Skills.
- 3. Click "+" and select "Upload a skill", then upload the ZIP file.
- 4. Start a new conversation. The skill will activate automatically when relevant.
Developers? Install via command line (CLI)
npx skills-il add skills-il/localization@v1.3.0-israeli-accessibility-compliance --skill israeli-accessibility-compliance -a claude-codeWhen to Apply
- When building a website in Israel that must comply with IS 5568 (anchored to WCAG 2.0 AA; sources differ on whether the current edition reaches 2.1)
- When checking whether a business is exempt: website-accessibility exemptions are revenue-based (full exemption for osek patur, temporary tiers below 100,000 NIS and 100,000-1,000,000 NIS, no automatic exemption above 1,000,000 NIS)
- When handling a complaint or legal demand to fix accessibility issues, including the 60-day cure period
- When performing an audit with screen readers (NVDA, JAWS) and keyboard navigation
- When upgrading compliance per the Commission for Equal Rights of Persons with Disabilities
- When building an accessibility preferences widget for a Next.js or React site that must satisfy Regulation 35 and IS 5568
Try These Prompts
What are the main requirements of the IS 5568 accessibility standard for websites in Israel? How does it differ from WCAG 2.1?
How do I verify that a Hebrew app complies with IS 5568? What tools, manual checks, and documents are required?
How do I configure ARIA attributes for a Hebrew RTL interface? Including aria-label, aria-describedby, and support for Hebrew screen readers.
Build me an accessibility preferences widget for my Next.js site compliant with Israeli Regulation 35 and WCAG 2.0 AA. User-preference toggles only (contrast, text size, line spacing, cursor, motion), not an auto-alt-text overlay. Use a pub-sub store, localStorage, and a FOUC bootstrap script.
Add an Alt+A keyboard shortcut to my accessibility widget that works on macOS as well as Windows/Linux. Use e.code === 'KeyA', not e.key === 'a', because macOS produces the dead-key 'å'.
Frequently Asked Questions
Changelog
Clarified the contested small-business exemption threshold, added the certified-expert (morshe negishut) role, IS 5568 Part 2 (document accessibility), a user complaint path, and corrected the deadline history.
Jun 21, 2026
Replaced the incorrect compliance trigger (25 employees / 300k NIS) with revenue-based exemption tiers, added the enforcement tracks and the 60-day cure period, and pinned the WCAG framing to 2.0 AA.
May 14, 2026
Fact refresh: clarified that the current IS 5568:2020 aligns with WCAG 2.1 AA (with Part 1 updated again in 2023), noted WCAG 2.2 is not yet legally required, fixed the Commission for Equal Rights URL, and corrected the statutory damages cap to 50,000 NIS in the reference file.
Apr 24, 2026
Related Skills
Author: skills-ilGenerate professional Hebrew documents (PDF, DOCX/Word, and PPTX) with correct right-to-left layout, mixed Hebrew-and-English bidi handling, and proper Hebrew typography. Use whenever the output is a Hebrew or mixed Hebrew/English Word document, Hebrew PDF, or Hebrew PowerPoint, including phrasings like "Hebrew Word document", "Word document in Hebrew", "מסמך Word בעברית", "create a .docx in Hebrew", "lehafik heshbonit", and "litstor hozeh", or Israeli templates such as Heshbonit Mas (tax invoice), Hozeh (contract), Hatza'at Mechir (proposal), or Protokol (meeting minutes). ALSO use this for the symptom where a Hebrew document looks correct on screen or in Claude but comes out scrambled, reversed, or broken after export to Word, with English words, numbers, or punctuation landing on the wrong side, phrased as "Hebrew text reversed in Word", "my Hebrew Word file is broken", "fix Hebrew formatting in Word", or "the docx came out messed up"; the fix is regenerating the .docx with paragraph-level RTL/bidi, NOT a web/CSS RTL change. Prefer this over the generic docx or pdf skills ONLY when the document is Hebrew or right-to-left, because those do not set RTL/bidi and produce scrambled Hebrew with English words and punctuation in the wrong place; for English-only documents use the generic skill. Covers reportlab, WeasyPrint, python-docx, and pptxgenjs. Do NOT use for OCR or reading existing documents (use hebrew-ocr-forms instead).
Author: skills-ilWrite and edit professional content in Hebrew including marketing copy, UX text, articles, emails, and social media posts. Use when user asks to write in Hebrew, "ktov b'ivrit", create Hebrew marketing content, edit Hebrew text, write Hebrew UX copy, or optimize Hebrew content for SEO. Covers grammar rules, register from formal to dugri, mixed Hebrew/English, gendered language, nikud and numerals, and Hebrew SEO best practices. Do NOT use for Hebrew NLP/ML tasks (use hebrew-nlp-toolkit) or translation (use a translation skill).
Author: skills-ilImplement right-to-left (RTL) layouts for Hebrew web applications. Use when user asks about RTL layout, Hebrew text direction, bidirectional (bidi) text, Hebrew CSS, "right to left", or needs to build a Hebrew web UI. Covers CSS logical properties, the :dir() pseudo-class, Tailwind RTL, React/Next.js RTL setup, icon mirroring, Hebrew typography, and font selection. Do NOT use for Arabic RTL (similar but different typography) unless user explicitly asks for shared RTL patterns, or for native mobile RTL (React Native I18nManager, SwiftUI, Android) which is out of scope.
Use at your own risk. Terms of Use · Security
Want to build your own skill? Try the Skill Creator · Submit a Skill