Skip to main content

Accessibility Statement

Last updated: 13 April 2026

Plain-language summary: We want everyone to be able to use Kahal, including people with disabilities. We follow the Israeli accessibility standard (IS 5568, level AA) and we keep working on it. If something doesn't work for you, tell us at support@mykahal.com and we will fix it.

1. Our commitment

Kahal, operated by AmihaiTech, is committed to making its platform accessible to people with disabilities, in accordance with the Equal Rights for Persons with Disabilities Law, 5758–1998 and the Equal Rights for Persons with Disabilities Regulations (Service Accessibility), 5773–2013.

We treat accessibility as a continuing obligation, not a one-time project. New features are reviewed against accessibility criteria before release, and we re-test the platform regularly.

2. Standard we follow

Kahal is being built to conform with Israeli Standard 5568, which adopts the W3C Web Content Accessibility Guidelines (WCAG) 2.0 at conformance level AA.

3. What we have done

  • Semantic HTML structure with proper landmarks, headings, and form labels.
  • Keyboard navigation across all primary flows (sign-in, booking, payment, admin management).
  • Color contrast ratios meeting WCAG 2.0 AA for body text and interactive elements.
  • Visible focus indicators on all interactive elements.
  • Text content that resizes cleanly up to 200% without breaking layout.
  • Form fields with associated labels and clear, programmatically-linked error messages.
  • Alternative text on meaningful images; decorative images marked as such.
  • Magic-link sign-in (no passwords) reduces cognitive and motor load for users who struggle with traditional auth.
  • Right-to-left language support for Hebrew content where present.

4. Known limitations

We are honest about the gaps we are still working on:

  • Some calendar and scheduling components have not yet been fully audited with screen readers (NVDA, JAWS, VoiceOver). Improvements are planned.
  • Card-entry pages are hosted on Sumit's own domain (we redirect to them, then back); their accessibility is governed by Sumit's own accessibility statement.
  • QR-code based check-in flows assume a working camera; we provide a manual code-entry alternative as a fallback.
  • Some legacy admin screens may have inconsistent heading levels — we are normalizing these.

If you encounter an additional barrier not listed here, please tell us — we treat reports as priority bug reports.

5. Pages and parts not covered

Content uploaded by community centers (organization logos, custom space descriptions, health declaration text, instructor bios, member-uploaded files) is the responsibility of the community center. We provide accessibility-friendly defaults and editing tools, but we cannot guarantee that every piece of customer-supplied content meets the standard.

6. Accessibility coordinator

Our accessibility coordinator (רכז נגישות) handles accessibility requests, complaints, and improvement suggestions:

Amihai Bouskila — AmihaiTech
Email: support@mykahal.com
Subject line: please use "Accessibility" so we can route it quickly.

We aim to acknowledge accessibility requests within 2 business days and to provide a substantive response — including a fix, a workaround, or a timeline — within a reasonable period that depends on the complexity of the issue.

7. Filing a complaint

If you are not satisfied with our response, you may file a complaint with the Commission for Equal Rights of Persons with Disabilities at the Ministry of Justice (נציבות שוויון זכויות לאנשים עם מוגבלות):

Website: gov.il / Ministry of Justice

8. Date of statement and review

This statement was last reviewed and updated on 13 April 2026. We review it at least once every 12 months, and whenever we make significant changes to the platform.