Accessibility Statement

Cabify is committed to making its web application for businesses accessible, in accordance with UNE-EN 301549:2022 on accessibility requirements for ICT products and services.

This accessibility statement applies to the Cabify for Business web application: https://cabify.com/app.

Compliance Status

This web application is partially compliant with UNE-EN 301549:2022 due to the following exceptions:

Non-Accessible Content

a) Lack of conformity:

Below are the accessibility issues identified, grouped by error type and with reference to the applicable criteria they fail to meet.

  • Focus management in modal dialogs: In several sections, when a dialog window opens, keyboard focus does not move to the new content, forcing the user to navigate through the underlying content. In addition, focus may leave the dialog and become lost in the main page content. When the dialog closes, focus does not always return to the element that triggered it. (Fails requirement 9.2.4.3 Focus Order).
  • Keyboard trap: In the “Send a delivery” and “Request a ride” forms, once the focus enters certain text fields, it is not possible to move backwards in the tab order, forcing the user to move forward. (Fails requirement 9.2.1.2 No Keyboard Trap).
  • Incorrect focus order: The tab sequence does not always follow a logical order. In some components, such as value adjustment buttons, focus jumps unexpectedly. In other cases, focus stops twice on the same interactive element or lands on non-interactive elements. (Fails requirement 9.2.4.3 Focus Order).
  • Invisible focus indicator: Multiple interactive components, including buttons, form fields, and links, lack a visible focus indicator or have one that is barely perceptible, hindering keyboard navigation. (Fails requirement 9.2.4.7 Focus Visible).

Keyboard operability

  • Elements not operable by keyboard: Some buttons and links, particularly those for clearing fields or within tables, cannot be activated using the keyboard. Likewise, menu buttons for selecting phone prefixes are neither accessible nor operable via keyboard. (Fails requirement 9.2.1.1 Keyboard).
  • Selecting options with the keyboard: In certain dialogs, although it is possible to navigate through different options using the keyboard, none of them can be selected. (Fails requirement 9.2.1.1 Keyboard).
  • Keyboard behavior: On some buttons in the delivery form, the user must tab again to prevent focus from returning to the input field when attempting to activate it and open the dialog. (Fails requirement 9.2.1.1 Keyboard).

Semantics and labels

  • Missing labels and descriptions: Several form components, such as the date picker, vehicle selection button, and prefix button, lack a textual label describing their purpose. (Fails requirements 9.3.3.2 Labels or Instructions and 9.4.1.2 Name, Role, Value).
  • Missing state and property information: Elements such as the vehicle selector do not communicate their state (collapsed or expanded) to assistive technologies. It is also not conveyed that certain fields will display a suggestion list when typing. (Fails requirement 9.4.1.2 Name, Role, Value).
  • Missing semantic structure: The headers of some dialogs are not semantically marked as headings, preventing proper structural navigation. (Fails requirement 9.4.1.2 Name, Role, Value).
  • Inaccessible information: Contextual information provided through tooltips or flags is not available to keyboard users or assistive technologies. (Fails requirement 9.2.1.1 Keyboard).

b) Disproportionate burden

  • Route planner and table architecture: The route planner and the keyboard row selection system in tables are undergoing a complete refactoring within a new component called “Journey builder”. Addressing these issues in the current architecture would require a disproportionate development effort, as the current solution will be replaced in the medium term.
  • Selection components (Comboboxes): Combobox elements display inaccessible keyboard behavior due to a legacy technical dependency. Their replacement requires deep intervention in the application’s architecture, which is considered a disproportionate burden in the short term, although work is already underway on a future solution.

c) Content outside the scope of applicable legislation

Third-party content: Parts of the application rely on third-party services and components beyond our direct control. This includes:

  • Embedded iFrames whose content and title cannot be modified.
  • Data charts generated by an external service. However, the essential information in these charts is always provided in textual format alongside them.
  • Address autocomplete suggestions provided by Google.
  • Forms and error notifications generated by integrated external services.
  • The “Favorite places” table in the “My company” section, whose code is generated by an unmodifiable external server.
  • The shipment platform dialog, where field labels disappear when typing.
  • The ride request form, where validation errors are not communicated in an accessible manner to assistive technology users. No correction suggestions are provided, and focus does not automatically move to the first field with an error.

Preparation of this accessibility statement

This statement was prepared on August 26, 2025.

The method used to prepare the statement was an external manual evaluation conducted by Glocal Quality Solutions SL.

Last review of the statement: August 26, 2025.

Feedback and contact information

You may contact us regarding accessibility requirements, for example to:

  • Report any potential non-compliance of this website.
  • Share any other difficulties in accessing the content.
  • Make any other inquiries or suggestions for improving the accessibility of the website.

By email: accesibilidad@cabify.com

Communications will be received and handled by Cabify’s accessibility team.

Enforcement procedure

If you wish to file a formal complaint regarding compliance with accessibility requirements, you may contact us through our accessibility email or use the government’s digital portal services at https://sede.inclusion.gob.es/reclamaciones-quejas-y-sugerencias

Cabify’s commitment to accessibility

Cabify is committed to digital accessibility and works continuously to improve its services and ensure an inclusive experience for all people. Accessibility is a priority in all projects and a core value of its corporate culture.

Choose which cookies
you allow us to use

Cookies are small text files stored in your browser. They help us provide a better experience for you.

For example, they help us understand how you navigate our site and interact with it. But disabling essential cookies might affect how it works.

In each section below, we explain what each type of cookie does so you can decide what stays and what goes. Click through to learn more and adjust your preferences.

When you click “Save preferences”, your cookie selection will be stored. If you don’t choose anything, clicking this button will count as rejecting all cookies except the essential ones. Click here for more info.

Save preferences