Israeli Accessibility Compliance
Verified95/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 95/100 (Verified) · 1,618+ 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.
npx skills-il add skills-il/localization@v1.2.0-israeli-accessibility-compliance --skill israeli-accessibility-compliance -a claude-codeInstall on Claude.ai, Claude Desktop, ChatGPT, Manus, or other platforms
- 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.
When 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
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
Added implementation guidance for a Regulation 35 / IS 5568 accessibility preferences widget: pub-sub architecture, FOUC bootstrap, layout-independent Alt+A shortcut, framer-motion wiring, and scope fences around overlay anti-patterns (citing the April 2025 FTC action against accessiBe). Complete copy-pasteable code in references/widget-implementation.md.
Apr 21, 2026
Related Skills
Plan domestic travel in Israel with local transportation, accommodations, national parks, and cultural considerations. Use when user asks about traveling in Israel, Israeli hotel chains, bus routes, Israel Railways, Rav-Kav card, national parks, tiyul b'aretz, Dead Sea, Eilat, or trip planning within Israel. Covers Egged/Dan/Kavim buses, train schedules, Rashut HaTeva sites, Shabbat travel restrictions, and seasonal advice.
Generate professional Hebrew documents including PDF, DOCX, and PPTX with full RTL support and proper Hebrew typography. Use when user asks to create Hebrew PDF, generate Israeli business documents, "lehafik heshbonit", "litstor hozeh", build Hebrew Word document, create Hebrew PowerPoint, or produce Israeli templates such as Heshbonit Mas (tax invoice), Hozeh (contract), Hatza'at Mechir (proposal), or Protokol (meeting minutes). Covers reportlab, WeasyPrint, python-docx, and pptxgenjs with bidi paragraph support. Do NOT use for OCR or reading existing documents (use hebrew-ocr-forms instead).
Write 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).
Use at your own risk. Terms of Use · Security
Want to build your own skill? Try the Skill Creator · Submit a Skill