Accessibility statement
This statement describes accessibility as it actually stands, including what has not been tested. No external accessibility audit has been carried out here.
We want everyone to be able to look for an apartment here and to run their tenancy, whatever their disability and whatever assistive technology they use. This page sets out what we have already done, what we have not, and how to tell us about a problem.
Our commitment
The site was built against WCAG 2.1 level AA from the start, rather than retrofitted to it. Those rules apply to every new page written here.
In Israel the relevant standard is IS 5568, which adopts WCAG 2.0 level AA; we work to the later version. «Built against the standard» is not the same as «independently tested against it» — the difference is set out under «What has not been done».
What is implemented on the site
- The site is built small-screen first. Every button and field you can operate by touch is at least 44 pixels tall.
- The Hebrew interface runs right to left. The layout is written with logical properties, so the same design is correct in both reading directions and not only in one.
- The site can be navigated by keyboard, focus is clearly and visibly marked, and every page starts with a link that skips straight to the content.
- Every page has a hierarchical heading structure and marked regions — header, main content and footer — declared once for the whole site.
- The colour pairs in use were checked against the required contrast ratio, and the measured values are recorded in the code beside the colour itself.
- We do not force a scrolling animation when you jump to a section within a page, so it cannot fight your operating system's «reduce motion» preference.
- A region that scrolls sideways — a wide table, for instance — can be focused by keyboard and has a name, because a region you cannot focus is a region you cannot scroll without a mouse.
The WhatsApp agent's accessibility
- The conversation with the agent is ordinary text inside WhatsApp, so your phone's screen reader, text scaling and every other accessibility tool work on it as usual.
- Replies are one consolidated message with at most three reply buttons, so there are no crowded screens and no choosing from a long list.
stopstops everything, at any point.- The accessibility of the WhatsApp app itself is not within our control.
What has not been done, and what we know is missing
- No external accessibility audit has been carried out and no accessibility opinion has been issued. This statement rests on internal testing only.
- We have not tested every screen one by one with a screen reader. The interactive map and the denser data views are where gaps are most likely to be found.
- The site has no high-contrast mode and no dark mode.
- Third-party content — images that came with listings, and the WhatsApp app itself — is not within our control.
Accessibility coordinator and contact details
We have not appointed an accessibility coordinator and we have not published dedicated contact details for the subject. We are not inventing a name and an address. Until they are published, the way to report a problem is the agent on WhatsApp — see the next section.
The scope of the accessibility duties that apply to us — including appointing a coordinator and issuing an accessibility opinion — is under legal review, and depends on details of the operating entity that have not yet been published.
Reporting an accessibility problem
Ran into a page or an action you could not complete? Write to us on WhatsApp and describe what you were trying to do, on which page, and on which device or assistive software. The more precise the description, the faster the fix.
Your message goes to +15556664923
We’re in a pilot, and this number cannot yet reply to everyone who writes to it — we may not get back to you in the conversation.
We treat a report like that as a defect, not as a feature request.
What happens to the information you send us in such a report is set out in the privacy notice.