Skip to main content
Tim8Home

הגרסה בעברית

Accessibility Statement · Tim8

Last updated: 31 October 2026 Version: 4.0

Our commitment

Tim8 is software that real estate agents work with every day, and that their clients enter in order to view properties and sign documents. We regard accessibility as part of the work itself and not as an addition to it, and we act so that every person can use the service independently, comfortably and equally, regardless of disability, device or assistive technology.

Level of accessibility and standard

Our target is the Israeli Equal Rights for Persons with Disabilities Regulations (Accessibility Adjustments to a Service), 5773-2013, and Israeli Standard SI 5568 at level AA, which is based on the WCAG 2.1 guidelines of the W3C.

We do not currently declare full compliance with the standard. On 27 September 2026 we tested the site ourselves: an automated check with the axe-core tool against the WCAG 2.1 and 2.2 level AA rules, in light mode and in dark mode, and manual checks of keyboard navigation, zoom and system preferences. This document describes only what was measured in that test, and lists separately what is still missing.

Screens tested

In the test of 27 and 28 September 2026: the home page, the "coming soon" screen, the agent's public showcase page and the property page, the three signing forms (brokerage services order, cooperation between agents, and brokerage order with exclusivity), the tenant details form, this statement, and the office screens: the chat, properties, property page, radar, campaigns, campaign page, calendar, document binder, updates, profile and help.

Screens added after the test

After 28 September 2026 the following screens and components were added to the service. They were built with the same components, the same colours and the same focus frame as the rest of the site, and have not yet been through the test described here:

  • The pricing page: the plan comparison, the monthly and annual switch, and frequently asked questions.
  • The payment page: choosing a plan, the business details for the invoice, and the card fields. The card fields belong to the payment processor, see "Third party components".
  • The credit screens: the monthly usage status, buying a credit pack, and upgrading the plan with the confirmation box.
  • The refer a friend screens: the personal link, the balance and the transaction history.
  • Account deletion: the deletion request, entering the one-time code, and the waiting screen until deletion.
  • The queue page: joining the launch queue and verifying the phone number.
  • The explainer video on the home page.

Third party components

Some components on the site come from external providers. Their accessibility depends on the provider, and we do not have full control over it:

  • The card fields on the payment page (Tranzila). The three card fields are frames of the payment processor. The colours, labels and structure around the fields are ours. What is inside the frames belongs to the provider, and its accessibility has not been tested by us.
  • The "I am not a robot" check (Cloudflare Turnstile). On the sign-in, registration, password reset and password change pages. In most cases the check passes without any action by the user. When it asks for a click, it is a Cloudflare component, and its accessibility has not been tested by us.
  • The accessibility toolbar (Vee). Loads on the public pages: the home page, the contact page, the "coming soon" screen, the about page, the legal documents, the showcases, the signing forms and the signed documents. On the office screens it loads without the floating button. It does not load on the pricing page, the sign-in and registration pages, the payment page or the account page. The toolbar is the provider's component, and does not replace the accessibility of the site itself.
  • The videos (YouTube). The explainer video on the home page and the help videos on the help page in the office. The player is YouTube's player, and it loads only when the video is clicked. The videos do not have captions at present.
  • The map on the property page (OpenStreetMap). A button on the map opens a full map, with a link that opens the location in Google Maps. The accessibility of the map itself to a screen reader has not been tested by us.

What was measured and found in order

  • Signing by drawing or by typing. Every signing form has two tabs above the signature area: Draw, which is the default, and Type. In the Type tab you type your full name, and it is shown as a handwritten signature. The tabs can also be switched with the arrow keys. We filled in and signed each of the three signing forms from start to finish using the keyboard alone. Both methods produce a signature image of the same size and format, and the signed document does not state which method was used. The drawing area has an accessible name and a description saying that you can switch to the Type tab.
  • Language and direction in five languages. The public showcase page and the property page were tested in Hebrew, English, Arabic, Russian and French. In each of them the language and the text direction are declared correctly, so that a screen reader pronounces each language by its own rules. The window title of the property page is also shown in the selected language.
  • Dark mode. The public showcase and the office screens have a dark mode alongside the light mode, and the automated check was run in both.
  • Respect for the reduced motion preference. When the preference is off, the home page has three areas that advance by themselves: the demo carousel, the language rotation and the WhatsApp demo. Each has a pause button that also works from the keyboard. Pausing stops all motion in the area, and resuming continues from the same point. Each of the three areas also stops when it leaves the screen, and continues when it comes back. The other animations on the page stop by themselves: the typing cursor in the header blinks for less than five seconds after the typing ends and then disappears, and the join button at the bottom of the page runs a single cycle of motion, of less than five seconds, when it comes into view, and then stops. When the preference is enabled in the operating system, nothing on the page advances by itself, no animations run, and the pause buttons are not needed and are not shown.
  • Zoom to 200 percent. On every screen tested, no horizontal scrolling appeared.
  • Keyboard navigation. On every screen tested, no focus trap was found. Every element that receives keyboard focus has a visible focus frame, in the same style across the whole site, in light mode and in dark mode.
  • Skip to content link. Every screen has a skip link that moves the focus to the start of the main content. On the public pages it is the second keyboard stop, from the accessibility plugin, and it works both when a page loads and after moving to another page within the site. On the office screens it is the first keyboard stop.
  • Structure. Every screen tested has a main content area and a heading structure, including the chat screen, where the headings are for screen readers only.
  • Labels and contrast. The automated check found no fields without a label and no text with insufficient contrast on the screens tested. Darkened demonstration parts on the home page, which are inactive and hidden from screen readers, are marked as such. On 28 September 2026 we also checked, on the home page, the elements the automated check could not decide on, against the lightest and darkest background behind the text, on desktop and on mobile, and all of them meet the standard. Text inside the demonstration pictures and the site logo are not included in this check, as the standard allows.

Known limitations

1. Scope of the test. An automated check finds only some accessibility problems. No test with a screen reader has been carried out yet, and no review by an external accessibility expert has been carried out yet. So what is found in order above does not guarantee that there are no further problems.

2. Office screens in other languages. The office screens were tested in Hebrew only. Language and direction in the other languages were tested on the public showcase and the property page.

3. PDF files. Signed copies are sent as PDF files. The accessibility of the files themselves, for example reading them with a screen reader, has not been tested.

4. Language of this statement. The statement exists in Hebrew and in English only. Anyone using the site in Arabic, Russian or French is directed to the English version.

5. Screens added after 28 September 2026. The screens listed in "Screens added after the test" have not yet been tested.

6. Third party components. The card fields, the "I am not a robot" check, the video player and the map are components of external providers, and their accessibility has not been tested by us. The videos do not have captions at present. Each of these components has an alternative, as set out in the next section.

We are working on these items, and this statement will be updated as they are completed.

An alternative way to receive the service

  • A form or a signature. Anyone who has difficulty filling in or signing a form on the site can contact the agent who sent them the link to the form directly, and arrange to fill it in and sign it in another way. The agent's name appears at the top of every form.
  • Payment, upgrade, credit pack or account deletion. Anyone who has difficulty with these actions on the site can contact the accessibility coordinator at the email address below, and we will help them carry out the action, after identity verification.
  • Sign-in or registration, when the "I am not a robot" check prevents continuing: contact the accessibility coordinator at the email address below.
  • A video: you can ask us for the content of the video in writing.
  • In any other case you can contact us at the email address below, and we will help find a suitable way.

Contacting us about accessibility

Did you encounter a difficulty, a fault or a component that is not accessible? We would be glad to hear about it, and we will handle the enquiry promptly.

Accessibility coordinator: Shlomi Baruch Dedicated email for accessibility enquiries: support@mytim8.com

So that we can handle the enquiry in the best way, we would be grateful if you could include the following details:

  • A description of the difficulty or the fault.
  • What you were trying to do.
  • The address of the page on which you encountered the problem.
  • The browser type and version.
  • The operating system.
  • The assistive technology you were using, if any.

Details of the operator

The service is operated by Tim8, Shlomi Baruch · Licensed business (Osek Murshe) no. 300613999, and is provided online only, with no premises open to the public. For enquiries concerning personal information: support@mytim8.com

Language. This is a translation for convenience. The Hebrew version of this statement is the binding one, and in any discrepancy between the versions the Hebrew text prevails.