This is a translation provided for convenience; the Macedonian version is the authoritative, legally binding text.

Accessibility statement

Last reviewed: 9 June 2026

At iSplit we believe everyone should be able to book a taxi and track a ride without obstacles. We are committed to making our web app and site accessible to as many people as possible, including people with disabilities. This statement explains the standard we aim for, what we have already done, the limitations we know about, and how to report a problem to us.

Compliance goal

We aim for compliance with the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. These international guidelines define how content on the internet should be accessible to people with a wide range of disabilities, including impairments of sight, hearing, motor skills, and cognitive difficulties. We treat accessibility as an ongoing process, not a one-time task.

What we have done so far

While building iSplit, we built several accessibility measures directly into the design and the code:

Semantic HTML — we use correct markup for headings, buttons, forms, and region landmarks, so that screen readers can understand the structure of the page.
Keyboard navigation — all interactive elements are reachable and operable with the keyboard alone, with no need for a mouse.
Visible focus — a clear, visible focus ring (focus-visible) marks the element you are on as you move with the keyboard.
Reduced motion — we honor the "prefers-reduced-motion" setting, so animations are kept to a minimum for users who prefer calmer screens.
Color contrast — text and important interface elements are designed to meet the contrast ratio for level AA for better readability.
Alternative text — we add descriptive alternative text to images and icons that convey meaning, while purely decorative elements are hidden from screen readers.
Associated forms — every form field has an associated label, an appropriate input type, and an error message that explains what needs to be fixed.
Large enough tap targets — buttons and links are large enough to tap easily on mobile devices.
Multilingual support — the page's language attribute is set correctly (mk, sq, or en), to help screen readers pronounce the text accurately.

Known limitations

Despite our efforts, some parts are still not fully accessible. We are aware of the following limitations and are working to resolve them:

Interactive map — the real-time display of vehicles on the map is largely visual. For users who cannot use the map, we provide the key information (status, arrival time) as text too, but the screen-reader experience on the map itself is still being improved.
Third-party content — some embedded services, such as the map and authentication components, are partly outside our control and their accessibility depends on the provider concerned.
Dynamic updates — real-time notifications about the ride status are being refined so they are announced more consistently through assistive technologies.

Improvement plan

Accessibility is part of our ongoing development. We carry out regular checks with automated tools and manual testing with the keyboard and screen readers, and we include the issues we find in the plans for upcoming releases. When we receive a report from a user, we review it as a priority and aim to offer a solution or a temporary alternative within a reasonable time.

Feedback and contact

If you run into an obstacle using iSplit because of an accessibility problem, please let us know. Describe the page or action where the problem occurred, which device and assistive technology you use, and what you expected to happen. We take all reports seriously and will help you complete your request.

Accessibility email: info@isplit.mk

We will respond to accessibility reports as soon as possible. If we cannot resolve the problem right away, we will offer you an alternative way to complete the task you requested.

Status of this statement

We update this accessibility statement regularly as the app and our practices change. The date of the last review is shown at the top of this page.

← Back to home