Accessibility statement

1. What this statement covers

This statement covers three services, and describes the website and the apps separately:

• The website collaro.app, in English and Hebrew.
• The Collaro app for iOS.
• The Collaro app for Android.

Both apps are built from the same code, and so far we have reviewed them together, from their shared code, noting where iOS and Android behave differently. The screen readers of the two operating systems — VoiceOver on iOS and TalkBack on Android — work differently, so using the two apps may not be the same experience. We have not yet tested either app on a device (see section 4).

2. The standard we work to

We work to make the website accessible according to Israeli Standard 5568 Part 1 (2023), which is based on the WCAG 2.0 guidelines, at level AA. In the apps, we work to apply the standard’s requirements as far as possible and as far as they are relevant to an app, using the accessibility features of iOS and Android.

This is our target. We do not claim that the website or the apps meet every requirement of the standard today; the main limitations we know about are listed in section 5.

The website relies on HTML, CSS, JavaScript and WAI-ARIA. The apps rely on the accessibility features of iOS and Android.

3. The accessibility measures we have taken

On the website:

• A clear, consistent page structure: headings and page regions are marked up in the code, and every page starts with a link that skips to the main content.
• You can use the website with a keyboard alone, and the element in focus is clearly marked.
• Images that convey information have a text alternative, except photos that users upload (see section 5); purely decorative images and icons are hidden from screen readers.
• Every page declares its language and text direction — Hebrew right to left, English left to right.
• With the accessibility menu you can enlarge all text, headings included, to 200%. You can also use your browser’s zoom or text-size setting: at 200% the body text doubles, but on screens wider than a phone the page and section titles grow less — at some widths to only about 140% of their size — so to enlarge them fully, use the menu’s text size. Pages adapt to narrow screens without scrolling sideways.
• Text colours are chosen to meet a contrast ratio of at least 4.5:1 against their background. The exception is the faint symbols of the price-level indicator (see section 5).
• When reduced motion is turned on in your device’s settings, or you turn on “Reduce motion” in the accessibility menu, the website stops its moving animations and smooth scrolling; only the loading indicator keeps turning, slowly.
• Changes on the page, such as new results or an error, are marked up so that screen readers can read them out. We have not yet confirmed this with a screen reader (see section 4).
• The accessibility menu: the round “Accessibility options” button at the bottom corner of every page opens a panel where you can enlarge the text (up to 200%), turn on high contrast, underline links, add space between lines, letters and words, reduce motion and show a strong focus outline — and reset them all. It is part of the website’s own code, not a third-party plug-in, and it adds to the accessible structure of the pages rather than replacing it. Your choices are saved only in your browser.

In the apps:

• In the app’s code, we have given buttons, fields, switches and other controls a name, a role and, where relevant, a state, so that the VoiceOver and TalkBack screen readers can read them out. We have not yet confirmed this on devices (see section 4).
• Messages that appear on screen, such as a confirmation, a form error or new search results, are also passed to the screen reader to be read out. An error in a form is also marked with an icon, not only with colour. We have not yet confirmed the read-outs on devices.
• Text grows with your device’s font size setting; in a few places, such as the verification-code boxes and the calendar, only up to a limit. We have not yet checked this on devices.
• Text colours aim for a contrast ratio of at least 4.5:1, in both the light and the dark display mode; the exceptions we know of are listed in section 5. In the calendar, today is in bold, not only shown in another colour.
• Fields that are optional are marked “(optional)”, on screen and for screen readers; all other fields are required. The password requirements are shown under the password field before you submit.
• Sending a booking request does not require dragging: you can drag the control, or tap it once and then again to send (on Android, a keyboard’s Enter key works the same way); tapping elsewhere on the page’s content cancels it. With a screen reader or switch access, a single activation sends the request. We have not yet confirmed this on devices.
• Alternatives to the map: providers are also shown in a list, and so are dog parks — once dog parks are shown, a “List” button next to them lists the parks on the map by name (with their distance when your location is on), and each one opens directions. If the map is too far out to show dog parks, the dog-parks button says so, and tapping it then zooms the map in for you, so no pinching is needed.
• Photo galleries can be browsed without swiping: tap the dots along the bottom of the photos. On a provider’s profile, a screen reader can also step through the photos one at a time — with VoiceOver, swipe up or down on the gallery; with TalkBack, adjust it as you would a slider.
• If access to the camera or the photos is turned off, the app tells you and offers to open your device’s settings.
• Short on-screen messages, such as a confirmation or an error, stay for longer when they are longer (errors at least 8 seconds), you can tap one to close it, and screen readers read them out.
• Lists and dashboards refresh when you return to them after a short while, so pulling down is not the only way to refresh them.
• The apps are available in Hebrew (right to left) and English (left to right), and you can sign up and sign in with an email address and password instead of Google or Apple.

4. How we checked

Our review was carried out in October 2026. It was our own internal review, not an assessment by a licensed service-accessibility professional. It included:

• A review of the website’s code and the apps’ code, screen by screen, against the WCAG accessibility guidelines (versions 2.0 to 2.2) at level AA, and a second review of the changes we made after it.
• Automated tests of the website in the Google Chrome browser (with the axe-core tool), in English and Hebrew, at phone and desktop widths, and checks of keyboard navigation, of the accessibility menu and of text enlarged up to 200% on screens as narrow as 320 pixels.
• Automated tests of the apps’ components, which check in the code the names, roles, states and messages that screen readers receive.

We reviewed the apps through their code only: we have not yet tested them on a device — not with VoiceOver or TalkBack, not with large text, and not with switch or keyboard access. We have not tested the website with a screen reader either. Such testing may reveal further problems, and we will update this statement accordingly.

5. Known limitations

These are the main limitations we know of. If one of them stops you from using the service, contact us (see section 7) and we will help you another way.

• The map (in the apps) can’t be explored with a screen reader, switch access or a keyboard. Everything it shows is also available in a list: providers in the list view, and dog parks through the “List” button that appears next to the dog-parks button.
• Photos that users upload (photos of dogs and of providers, on the website and in the apps) are shown without a text description, and there is not yet a way to add one.
• Documents the app generates (booking summaries as PDF or Excel files, and the yearly payment-records export in Excel) have not been checked for accessibility. On request, we will give you the information in them in an accessible format.
• The price-level indicator (on the website and in the apps): the faint symbols that show the rest of the scale have low contrast, on purpose, so that the number of bold symbols reads as the level. The level itself is shown by the bold, darker symbols, and screen readers read it out in words (for example, “Price level 2 of 3”).
• Contrast of graphical elements (in the apps): some non-text elements — the borders of fields, a switch in its off position, the selected option in option selectors, the dots of photo galleries and, in the light display mode, rating stars — stand out from their background less than they should (a contrast ratio below 3:1). Their labels and states are also shown in text and read out by screen readers.
• Some small text (in the apps) has a contrast ratio slightly below 4.5:1 in the light display mode: the prompt inside an empty photo field, and the letters shown instead of a photo for a female dog.
• Closed conversations (in the apps): in the chat list, closed conversations are shown faded, so some of their text has a contrast ratio below 4.5:1. Their status is also shown in words (“Closed”).
• The side menu (in the apps): the screen you are on is marked in the menu mainly by colour; screen readers announce it as selected.
• Calendar days (in the apps) are smaller touch targets (about 32 points) than Apple (44 points) and Google (48 dp) recommend, so that a whole month fits on small screens, and unavailable days are marked only by being shown faded (screen readers say “Unavailable”, and they can’t be picked). If this makes choosing a date difficult, contact us and we will help.
• Short on-screen messages (in the apps) still disappear on their own after several seconds. Screen readers read them out; if you need more time to read them, contact us and we will help.
• The contact form in the apps is available only to signed-in users. You can always contact us by email instead, without an account.
• Behaviour we have not yet checked on devices (in the apps), for example: whether screen readers announce the new value when you turn the time-picker wheels; sending a booking request by tapping or with a keyboard; browsing photo galleries with the dots or with a screen reader; where the screen reader’s focus lands after the menu or a pop-up window closes, and after you sign up and the email-verification screen appears; the reading order on the map screen; and the order in which a screen reader reads a chat’s messages, which are listed newest first.

6. Third-party components

Parts of the service rely on third-party components whose accessibility we do not control:

• The Google and Apple sign-in screens — you can sign up and sign in with an email address and password instead.
• The map tiles (CARTO) and map data (OpenStreetMap) — providers and dog parks are also shown in a list (see section 5).
• The navigation apps (Waze and Google Maps) that the app opens for directions, and your device’s share and save screens for documents.
• The app’s pages on the App Store and Google Play, and your device’s photo picker and camera.

If one of these components stops you from using the service, contact us and we will help you another way.

7. Contacting us about accessibility

Write to us at contact@collaro.app to tell us about something on the website or in the apps that is not accessible, to ask us to make something accessible, or if you need information or a service in another accessible way. You don’t need an account in the app. On request, we will also give you information about the service, and help you use it, by email.

To help us respond quickly, please tell us:

• which page of the website or which screen of the app the problem is on, and what you were trying to do;
• which device and operating system you were using — for example an iPhone, an Android phone, or a computer and browser;
• which assistive technology you were using, if any — for example a screen reader, enlarged text or a keyboard.

We will acknowledge your message and deal with it as soon as possible, and until the problem is resolved we will offer you, as soon as possible, another way to get the information or the service — for example by email. If the problem is in a component we do not control (section 6), we will tell you and offer you another way.

8. Updates to this statement

This statement was prepared in October 2026. On the website, you can reach it from the footer of every page and from the accessibility menu. In the apps, you can reach it from the side menu and, before you sign in or finish signing up, from the sign-in screen, the provider list you see before signing in, the sign-up screen and the email-verification screen; it is also linked from the screen that asks you to accept updated terms. We will update it when we make changes to the accessibility of the website or the apps and when we complete further testing; the date it was last updated is shown at the top of this page. If an accessibility feature or service is unavailable for more than a week, we will say so on this page, together with the alternative we offer meanwhile.