→ Home

Accessibility Statement

Last reviewed: 28.08.2026

Takukan is a conversational real-estate matching platform. We treat accessibility as part of the product itself: a plain-language conversation is a more accessible interface than a form — and everything around it must meet the same bar.

The standard and level we apply

This site is built to meet the Israeli Equal Rights for Persons with Disabilities (Service Accessibility) Regulations 2013 and Israeli Standard IS 5568 (WCAG 2.0), level AA. The statement covers the public pages on this domain: the home page, the projects lobby and developer pages, project and area pages, the assistant conversation, the public forms, the indexation calculator, the account and privacy pages, and the privacy and accessibility policy pages themselves.

What was tested, when, and how

On 28.08.2026 we ran an internal accessibility review across every page listed above. It covered:

• Keyboard-only operation — tab order, visible focus, focus traps, and every component that opens (the unit dialog, the photo lightbox, the chat drawer, multi-step forms).
• Automated structural checks in the browser: landmarks, heading hierarchy, a label on every field, alternative text on images, and error messages tied to their field.
• Colour-contrast measurement against the real palette, for text and for user-interface boundaries.
• Language and direction checks (Hebrew/RTL against English/LTR) on every page.

What is implemented

• Full keyboard navigation, including a "skip to main content" link first in the tab order and a single focus ring with sufficient contrast on both light and dark backgrounds.
• Semantic HTML: one h1 per page, a heading hierarchy, labelled landmarks, and an explicit label on every field — including choice groups and star ratings.
• Form error messages are associated with their field, and the field is marked invalid — not by colour alone.
• Every drag-and-drop interaction has a keyboard equivalent: move buttons and Alt+arrow keys in the form builder, the flow canvas and the dashboard.
• Full Hebrew and RTL support, with numbers, prices and phone numbers in the correct direction; Hebrew-only content is marked as such so it is not read with an English voice.
• The operating system's reduced-motion preference is honoured — animations and smooth scrolling switch off automatically.
• The chat works in free text, with no dependence on a mouse, dragging or response timing; the conversation log announces an incoming reply without re-reading the whole history.
• Images carry alternative text, decorative images are marked as such, and links and buttons are phrased so their purpose is clear out of context.

Known limitations

We would rather say plainly what is not yet finished:

• The review was internal, automated and keyboard-based. A full screen-reader pass (NVDA/JAWS/VoiceOver) has not yet been carried out, and no external certified accessibility audit has been performed.
• Embedded maps (Google Maps / OpenStreetMap) and embedded video are third-party services whose internal interface we do not control. Everything a map shows — address, city, neighbourhood — also appears as text on the page.
• Project videos uploaded by developers do not necessarily carry captions. If you need a transcript, contact us and we will provide one.
• Documents uploaded by developers (specifications, plans, PDFs) are not necessarily accessible. We will supply their content in an accessible format on request.
• Two design details known to miss the required contrast ratio are being fixed: the reddish accent on certain status labels, and the filter-chip border on the dark band of the projects lobby. In both cases the information is also carried in words, not by colour alone.
• This is a living product that updates frequently; new components may not yet have had a full review. Every report is welcome and acted on.

Accessibility coordinator and how to reach us

The accessibility coordinator role at Takukan is held by the service's operations team. Contact us about anything accessibility-related — a difficulty using the site, a request for an accommodation, or content in an accessible format — at eli@a-in.co.il.

How to report a barrier

Email the address above and tell us: (1) the address of the page where you hit the problem; (2) a short description of what did not work; (3) the assistive technology, browser and operating system you use. We acknowledge every report within two business days and tell you what we are doing about it and when we expect to fix it.

If we have not handled it properly

If you feel a report has not been handled as it should be, you may contact the Commission for Equal Rights of Persons with Disabilities at the Israeli Ministry of Justice.