Israeli Accessibility Compliance
Implement IS 5568–aligned Hebrew RTL accessibility, legal exemptions, and remediation timelines when shipping a site for the Israeli market.
Overview
Israeli Accessibility Compliance is an agent skill most often used in Build (also Ship, Launch) that implements IS 5568–based Hebrew RTL web accessibility with legal and technical guidance.
Install
npx skills add https://github.com/skills-il/localization --skill israeli-accessibility-complianceWhat is this skill?
- Maps Israeli IS 5568 to WCAG 2.0 AA with noted 2.1-aligned additions
- Covers exemptions by revenue tier, dual enforcement paths, and 60-day remediation window
- Documents accessibility coordinator role and Hebrew screen-reader expectations
- Includes RTL-oriented ARIA templates and implementation focus for Hebrew apps
- Scoped to Israeli legal context—not generic WCAG-only guidance
- IS 5568 anchored to WCAG 2.0 AA with selective 2.1-aligned criteria
- 60-day remediation period referenced for corrections
- Skill version 1.2.0 in package metadata
Adoption & trust: 1 installs on skills.sh; 18 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You are shipping a Hebrew RTL site and must reconcile IS 5568 law, WCAG expectations, exemptions, and fix timelines—not generic English-only checklists.
Who is it for?
Indie SaaS, marketing sites, or apps targeting Israeli users that must document negishot compliance and RTL assistive-tech support.
Skip if: Products with no Israeli market, teams wanting WCAG-only audits without IS 5568 law, or native mobile apps outside the skill’s web-focused scope unless you adapt manually.
When should I use this skill?
User asks about Israeli accessibility law, IS 5568, negishot, exemptions, enforcement, coordinator role, Hebrew screen readers, or RTL accessibility audits.
What do I get? / Deliverables
You get actionable Israeli-context requirements, RTL ARIA patterns, and enforcement-aware remediation steps you can apply in code and release planning.
- Compliance-oriented implementation guidance for IS 5568 and RTL patterns
- Audit-oriented answers on enforcement, exemptions, and remediation timing
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build frontend is the canonical shelf because the skill centers on implementing widgets, RTL ARIA patterns, and screen-reader behavior in the product UI. Frontend subphase holds markup, RTL layout, and accessibility widget implementation rather than abstract legal research alone.
Where it fits
Decide whether your revenue tier qualifies for a partial exemption before committing to a full accessibility sprint.
Add an accessibility widget and RTL ARIA labels so Hebrew screen readers announce controls correctly.
Run a compliance-oriented review aligned to IS 5568 before production cutover.
Document coordinator contact and public accessibility statement for Israeli visitors.
How it compares
Use instead of generic accessibility skills when the question is Israeli law and RTL Hebrew—not US ADA or EU EN 301 549 alone.
Common Questions / FAQ
Who is Israeli Accessibility Compliance for?
Solo builders and small teams building Hebrew RTL websites or web apps who need IS 5568, enforcement, and implementation guidance in one agent skill.
When should I use Israeli Accessibility Compliance?
In Build when implementing widgets and RTL ARIA; in Ship when verifying compliance before release; in Launch when preparing for enforcement exposure; and in Validate when scoping whether your site is exempt.
Is Israeli Accessibility Compliance safe to install?
It is documentation- and implementation-guidance oriented; still review the Security Audits panel on this page and avoid pasting secrets when describing your site in chat.
SKILL.md
READMESKILL.md - Israeli Accessibility Compliance
{ "author": "skills-il", "version": "1.2.0", "category": "localization", "tags": { "he": [ "נגישות", "תקן-5568", "נכים", "RTL", "ישראל", "ווידג'ט", "יישום" ], "en": [ "accessibility", "is-5568", "wcag", "rtl", "israel", "widget", "implementation" ] }, "display_name": { "he": "נגישות אתרים ישראלית", "en": "Israeli Accessibility Compliance" }, "display_description": { "he": "מטמיעים נגישות אתרים ישראלית לפי תקן IS 5568, שמעוגן ב-WCAG 2.0 AA (התקן מוסיף חלק מקריטריוני 2.1; המקורות חלוקים), לאפליקציות בעברית עם RTL. שימושי כשמשתמש שואל על חוק הנגישות בישראל, תקן 5568, מי פטור מהנגשת אתר, אכיפה וקנסות, רכז נגישות, תמיכת קוראי מסך בעברית או ביקורת נגישות לאתר. מכסה את הדרישות המשפטיות מכוח חוק שוויון זכויות לאנשים עם מוגבלות, מדרגות הפטור לפי מחזור, שני מסלולי האכיפה (פיצוי אזרחי ועיצום כספי של הנציבות) ותקופת התיקון של 60 יום, תפקיד רכז הנגישות, תאימות לקוראי מסך בעברית ותבניות ARIA ל-RTL. לא מיועד להנחיות WCAG כלליות ללא ההקשר הישראלי.", "en": "Implement 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)." }, "supported_agents": [ "claude-code", "cursor", "github-copilot", "windsurf", "opencode", "codex", "antigravity", "gemini-cli" ] } # Israeli Standard 5568 (IS 5568) Reference ## Legal Framework ### Equal Rights for Persons with Disabilities Act (1998) - The 1998 act (Chok Shivyon Zechuyot Le'Anashim Im Mugbaluyot) established the statutory right to accessibility. - Web and service accessibility are implemented through the **Equal Rights for Persons with Disabilities (Service Accessibility Accommodations) Regulations, 2013** (Takanot Negishut LeSherut), which reference Israeli Standard IS 5568 Part 1. - Mobile applications are covered under the same service accessibility regulations; later amendments and technical updates (2020, 2023) clarified the scope. - Enforcement is carried out by the Commission for Equal Rights of Persons with Disabilities (Netzivut Shivyon Zechuyot) at the Ministry of Justice. ### Who Is Exempt (Website Accessibility) The Service Accessibility Regulations base website-accessibility exemptions on **revenue**, not on employee count. There is no "25 employees" or "300,000 NIS" trigger in the regulations. | Operator | Exemption | |----------|-----------| | Osek patur (VAT-exempt dealer) | Full exemption from website accessibility | | Average annual revenue under 100,000 NIS | Temporary 3-year exemption, renewable every 3 years as long as average revenue stays at or below 120,000 NIS | | Average annual revenue 100,000 NIS to 1,000,000 NIS | 3-year exemption for an existing site whose operation began before 26 October 2017; a site built after that date must be accessible | | Average annual revenue above 1,000,000 NIS | No automatic exemption. The operator must apply to the Commission to claim a heavy-burden exemption | Most of these exemptions are automatic and need no approval, but the operator must re-check revenue every 3 years