Israeli Accessibility
Trusted73/100The Problem
Israeli websites must comply with IS 5568 (based on WCAG 2.1) under the Equal Rights for Persons with Disabilities Law, but standard accessibility tools and practices do not address Hebrew RTL-specific patterns, Hebrew ARIA labels, or Israeli-specific requirements like the mandatory accessibility statement.
Author: @skills-il
Audit and implement web accessibility compliance per Israeli Standard IS 5568 and the Equal Rights for Persons with Disabilities Law
npx skills-il add skills-il/security-compliance --skill israeli-accessibilityWhen to Apply
- When auditing an Israeli website for IS 5568 accessibility compliance
- When implementing RTL-specific keyboard navigation and screen reader support
- When writing Hebrew ARIA labels and accessible names for UI components
- When creating an Israeli accessibility statement (Hatzaharat Negishot)
- When testing a Hebrew website with screen readers like NVDA or JAWS
Israeli Accessibility
Instructions
Israeli Accessibility Law
The Equal Rights for Persons with Disabilities Law (Chok Shivyon Zchuyot, 1998) with 2005 and 2013 amendments mandates IS 5568 compliance. Government websites, public bodies, businesses serving the public, companies with 50+ employees (Note: accessibility regulations apply based on public-facing service type, not solely employee count), and e-commerce sites must all comply at AA level. Penalties up to 50,000 NIS per violation.
IS 5568 Standard
Based on WCAG 2.1 with Israeli-specific additions: accessibility statement (Hatzaharat Negishot) required on every page, accessibility menu/widget, lang="he" and dir="rtl" attributes, accessibility coordinator contact published.
RTL Accessibility Patterns
Tab order: right to left, top to bottom. Arrow keys in menus: left opens submenu (reversed from LTR). Use CSS logical properties (margin-inline-start instead of margin-left). Focus indicators must be 3px minimum.
Hebrew ARIA Labels
Common labels: תפריט ראשי (main nav), חיפוש באתר (search), סגירה (close), דלגו לתוכן הראשי (skip to content), טוען... (loading). Mixed content needs proper dir attributes on numbers and emails.
Audit Checklist (IS 5568 AA)
Perceivable: alt text in Hebrew, captions, 4.5:1 contrast. Operable: keyboard access, RTL tab order, skip nav. Understandable: lang="he", Hebrew error messages. Robust: valid HTML, correct ARIA.
Testing
Automated: axe DevTools, Lighthouse, WAVE, Pa11y, jest-axe. Manual: keyboard nav RTL, NVDA/JAWS Hebrew, VoiceOver, zoom 200%, high contrast mode.
Examples
Example 1: Audit a Hebrew E-Commerce Site for IS 5568
User says: "Check my Hebrew e-commerce site for Israeli accessibility compliance" Actions:
- Verify
<html lang="he" dir="rtl">is set - Check skip navigation link exists and works with keyboard
- Validate all images have Hebrew alt text (not English)
- Test form labels are associated with inputs and read correctly in Hebrew
- Verify color contrast meets WCAG 2.1 AA (4.5:1 for text)
- Check tab order follows RTL flow (right-to-left, top-to-bottom)
- Test with NVDA screen reader in Hebrew mode
- Verify accessibility statement page exists in Hebrew Result: Compliance report with pass/fail per IS 5568 criterion and remediation guidance
Example 2: Add Accessibility to a React RTL Application
User says: "Make my React app accessible for Israeli users" Actions:
- Add
dir="rtl"to root element, use CSS logical properties - Implement skip-nav component with Hebrew label ("דלג לתוכן הראשי")
- Add ARIA labels in Hebrew for all interactive elements
- Implement keyboard navigation (arrow keys reversed for RTL)
- Add accessibility statement page per Israeli law requirement
- Configure focus indicators visible in both light and dark themes Result: React app with IS 5568 compliant accessibility features
Bundled Resources
Scripts
scripts/a11y_checker.py-- Validates HTML files against IS 5568 Israeli accessibility requirements including RTL attributes, Hebrew ARIA labels, skip navigation, and form labels. Run:python scripts/a11y_checker.py --help
References
references/is-5568-checklist.md-- Complete IS 5568 compliance checklist covering legal framework (Equal Rights for Persons with Disabilities Act, 1998), WCAG 2.1 AA mapping, RTL-specific requirements, Hebrew ARIA patterns, and testing tools. Consult when performing a full accessibility audit or when you need the detailed per-criterion checklist.
Troubleshooting
Error: "Screen reader not reading Hebrew content correctly"
Cause: NVDA/JAWS may not switch to Hebrew speech engine automatically
Solution: Ensure lang="he" is set on the HTML element and on any content sections. Use aria-label in Hebrew for custom widgets. Test with NVDA's Hebrew speech synthesizer (eSpeak or Vocalizer).
Error: "Focus indicator not visible in dark theme"
Cause: Default browser focus outline may be invisible on dark backgrounds
Solution: Use a custom focus indicator with sufficient contrast in both themes. Use outline: 2px solid with a color that has 3:1 contrast against both light and dark backgrounds. CSS: *:focus-visible { outline: 2px solid #4A90D9; outline-offset: 2px; }
Error: "Tab order incorrect in RTL layout"
Cause: CSS flexbox/grid items may not follow visual RTL order for keyboard navigation
Solution: Ensure dir="rtl" is on the container element. Avoid tabindex values greater than 0. Use CSS logical properties (margin-inline-start instead of margin-left) so layout and tab order stay aligned.
Metadata
GitHub:israeli-accessibility
installs:1
views:127
reviews:0 (0.0)
Created:March 3, 2026
Updated:March 5, 2026
Supported Agents
Claude CodeCursorGitHub CopilotWindsurfOpenCodeCodexAntigravity
Tags
accessibilityis-5568wcagcompliancertlequal-rights
Best Practices
- Set both lang="he" and dir="rtl" on the HTML element as the foundation for RTL accessibility
- Use CSS logical properties (margin-inline-start) instead of physical properties (margin-left) for RTL-safe layouts
- Wrap numbers, phone numbers, and email addresses in span dir="ltr" for correct screen reader pronunciation
- Include a Hebrew skip navigation link (דלגו לתוכן הראשי) accessible via keyboard
- Publish a complete accessibility statement (Hatzaharat Negishot) with audit date, compliance level, and coordinator contact
Avoid
- Do not rely solely on an accessibility toolbar/widget to achieve compliance; it supplements but does not replace built-in accessibility
- Do not use tabindex values greater than 0 as they break the natural RTL tab order
- Do not assume LTR keyboard navigation patterns; RTL reverses arrow key behavior in menus and sliders
- Do not skip manual testing with Hebrew screen readers as automated tools miss RTL-specific issues
Try These Prompts
Full IS 5568 Accessibility Audit
Audit our Israeli e-commerce website for IS 5568 AA compliance, including RTL keyboard navigation, Hebrew ARIA labels, color contrast, and accessibility statement requirements
Hebrew Form Accessibility
Make our Hebrew registration form accessible with proper labels, ARIA attributes, RTL validation messages, and keyboard navigation in RTL order
Accessibility Statement Template
Create a Hebrew accessibility statement (Hatzaharat Negishot) for our website that meets IS 5568 requirements, including compliance level, known limitations, and coordinator contact
Security Analysis
73/100
Trust Score
Code Quality58
Permissions40
Data Handling100
Publisher Reputation70
Maintenance100
Documentation100
Passed security checksv13/5/2026
Quality Score
70Architecture72
Maintainability68
Content80
Spec Compliance88
Community40
Installs by Agent
Claude Code1
Frequently Asked Questions
Related Skills
Israeli Privacy Compliance
Author: skills-ilTrusted73/100
New
Israeli privacy law implementation code patterns for the Protection of Privacy Law (Chok Haganat HaPratiyut, 1981). Provides consent management code, DSAR workflow implementation, PPA database registration API integration, cross-border data transfer patterns, and GDPR dual-compliance bridging code. Use when user asks to implement privacy compliance in code, build consent forms, handle data subject requests, integrate with database registry, or write GDPR-compatible Israeli privacy code. Do NOT use for regulatory overview (use israeli-privacy-shield instead).
0.00388
Claude CodeCursorGitHub Copilot+4
Hebrew Legal Research
Author: skills-ilTrusted73/100
New
Assist with Israeli legal research including legislation lookup, case law concepts, Hebrew legal terminology, and legal document preparation guidance. Use when user asks about Israeli law, "chok", "mishpat", "bagatz", court procedures, employment law, contract law, real estate law, or needs help with Hebrew legal terms. Covers civil, commercial, employment, and administrative law. Do NOT use for providing formal legal advice — always recommend consulting a licensed Israeli attorney (orech din). Do NOT use for non-Israeli legal systems.
0.01328
Claude CodeCursorGitHub Copilot+4
Israeli Cyber Regulations
Author: skills-ilTrusted73/100
New
Israeli cybersecurity regulatory framework guidance covering INCD (Ma'arach HaSyber) national directives, Bank of Israel Directive 361 (cyber for financial institutions), Directive 357 (payment security), ISA requirements for TASE-listed companies, and sector-specific rules for fintech and healthtech. Use when user asks about cyber regulation Israel, INCD compliance, Bank of Israel directives, ISA cyber requirements, or sector cyber rules. Do NOT use for privacy law compliance (use israeli-privacy-compliance instead).
0.0086
Claude CodeCursorGitHub Copilot+4
Want to build your own skill? Try the Skill Creator · Submit a Skill
Reviews (0)
No reviews yet. Be the first to write one!