Accessibility Statement
Version:
We want everyone to be able to use KAA, in Hebrew and in English, on the website and in the iPhone app. This statement follows regulation 35 of the Equal Rights for Persons with Disabilities (Accessibility Adjustments for Service) Regulations, 2013. Last reviewed 2026-09-30.
The standard we follow
The legal level in Israel is Israeli Standard IS 5568, which is based on WCAG 2.0 at level AA. We aim higher: WCAG 2.2 at level AA, on the website and in the app.
How we check
At each review we run automated checks (axe) on every screen in Hebrew and English at phone size, use the website with a keyboard only, enlarge text to 200 percent, narrow the screen to 320 pixels, turn on reduced motion, and use the iPhone app with VoiceOver and the largest iOS text size.
What is accessible, and how
- Keyboard: every control can be reached and used with a keyboard, in a logical order, with a clearly visible focus ring. Legal pages have a "skip to content" link.
- Screen readers: buttons, links, form fields and map markers have names, pages have headings and landmarks, and the current tab is announced.
- Text size: pinch zoom is never blocked. In Settings, under Accessibility, you can make the text larger, and the iPhone app follows iOS Larger Text, up to twice the normal size. Text wraps onto more lines; a few long names are shortened in lists and shown in full when you open them.
- Contrast: text has a contrast of at least 4.5 to 1, and Settings has a high contrast option.
- Touch: everything you can tap is at least 24 by 24 pixels, and the main buttons at least 44.
- Motion: nothing moves or fades when your device asks for reduced motion, and you can also stop animations in Settings.
- Language and direction: Hebrew reads right to left and English left to right, and you can switch at any time.
- More in Settings, under Accessibility: underlined links, a plain readable font and a larger focus outline. Your choices stay on your device.
- KAA has no audio or video, so there is nothing to caption. Photos have text alternatives.
- We do not use an accessibility overlay or toolbar.
Known limitations, and the accessible alternative
| Part | Limitation | Accessible alternative |
|---|---|---|
| The map (MapTiler with OpenStreetMap data, or Google Maps) | Moving and zooming a map with a keyboard or a screen reader is hard | Every place and event on the map is also in the Tonight lists and the category pages, each with a Navigate button |
| Google's place details and place search (Google Places UI Kit) | Made by Google; we cannot change how they read | Our own place sheet has the name, category, area, members' ratings, tips and Navigate |
| Event listings from phangan.events | The descriptions are written by the organisers | Our event page shows the time, the venue and a Navigate button in plain text |
| Scanning a friend's code with the camera | Needs the camera | Search for them by @handle or by name in People |
| What members post | A photo or text may not have a description | Report it, and we will ask the member to fix it |
Ask for help or an accommodation
If something is hard to use, or you need information in another way (for example read out to you, or in larger print), tell our accessibility coordinator. Say which page and what happened. We reply within 5 business days, and sooner when it stops you from using KAA.
Accessibility coordinator: Igal Tal Merom, accessibility@kohvra.com, +972 52 249 1312.
Write to accessibility@kohvra.com. A person reads every message.