israeli-accessibility-compliance

Implements Israeli IS 5568 accessibility compliance for Hebrew RTL websites and applications.

Updated Sep 15, 2026
One-click install
npx skills add https://github.com/Nadav011/nadavai-claude --skill israeli-accessibility-compliance-nadav011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: israeli-accessibility-compliance
Source: https://github.com/Nadav011/nadavai-claude/tree/main/plugins/nadavai/skills/israeli-accessibility-compliance
Command: npx skills add https://github.com/Nadav011/nadavai-claude --skill israeli-accessibility-compliance-nadav011

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, beautifulsoup4, selenium, axe-core, and includes scripts (resource) and references (resource) components.

What problem does it solve? Israeli websites and apps face mandatory accessibility duties under the Equal Rights for Persons with Disabilities Act and IS 5568, with statutory damages up to 50,000 NIS per violation, yet most developers only know generic WCAG guidance and miss the Israeli-specific legal and RTL requirements. ## Core Features & Use Cases - Legal framework guidance: Covers IS 5568 anchored to WCAG 2.0 AA, revenue-based exemption tiers, the 60-day cure period, the two-track enforcement model (civil damages plus Commission administrative penalties), and the accessibility coordinator (rakaz negishut) duty. - RTL and Hebrew implementation patterns: Provides accessible RTL HTML structure, Hebrew screen reader patterns (NVDA, JAWS, VoiceOver, TalkBack), RTL ARIA form and table patterns, and the mandatory accessibility statement (Hatzaharat Negishot) template. - Regulation 35 widget and audit tooling: Ships copy-pasteable TypeScript/React code for a compliant accessibility preferences widget (with FOUC bootstrap and overlay anti-pattern fences) plus a Python audit script that checks lang, dir, alt text, labels, skip links, and statement pages. - Use Case: A developer launching a Hebrew e-commerce site runs the audit script, fixes RTL form labels and Hebrew error messages, publishes the accessibility statement, and ships the preferences widget to meet IS 5568 obligations. ## Quick Start Audit my Hebrew website for Israeli IS 5568 accessibility compliance and tell me what to fix.

Frequently Asked Questions about israeli-accessibility-compliance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make my Israeli website comply with IS 5568?

Declare lang="he" and dir="rtl" on the html element, add a Hebrew skip-navigation link, label all form inputs, meet 4.5:1 contrast, and publish a mandatory accessibility statement with coordinator contact details. Run the bundled audit script for automated checks, then test manually with NVDA or VoiceOver.

What is the difference between IS 5568 and WCAG?

IS 5568 is anchored to WCAG 2.0 AA and adds Israeli-specific requirements: mandatory Hebrew accessibility statements, RTL direction declarations, Hebrew error messages, an accessibility contact channel, and bilingual content expectations for public bodies serving Hebrew and Arabic speakers.

Which businesses are exempt from Israeli website accessibility requirements?

Exemptions are based on revenue, not employee count. Osek patur dealers are fully exempt, small businesses under the contested 100,000-120,000 NIS threshold get renewable 3-year exemptions, and operators above 1,000,000 NIS must apply to the Commission for a heavy-burden exemption.

Does the audit script work with React or single-page applications?

The bundled audit_a11y.py is a static-HTML auditor and cannot evaluate JavaScript-rendered content or color contrast. For SPAs and contrast checks, use the axe-core plus Selenium path shown in the skill's Step 10 instead.

Can an accessibility overlay widget make my site IS 5568 compliant?

No. Overlays like accessiBe do not make sites compliant, and the FTC fined accessiBe $1M in April 2025 for such claims. A compliant widget only toggles user-controlled CSS preferences; semantic HTML, keyboard operability, and real screen-reader testing must be built into the site itself.

Why is my Hebrew form not announced correctly by screen readers?

Screen readers misread Hebrew forms when dir="rtl" is missing, labels are not associated with inputs, or error messages lack role="alert". Add aria-required and aria-describedby to fields, write error text in Hebrew, and set dir="ltr" on numeric inputs like ID numbers.