Skip to content

Version 1.3 · Effective 2026-10-13

Accessibility Statement

Emaride EU S.à r.l. is committed to making its digital offerings accessible in line with the European Accessibility Act (EAA, Directive (EU) 2019/882). Our benchmark is WCAG 2.2, level AA (identical to the standard ISO/IEC 40500:2025), which also covers the requirements of EN 301 549 (currently based on WCAG 2.1 AA). This statement describes the current state of implementation.

1. Scope

This statement applies to:

  • the Emaride website at www.emaride.lu (public pages),
  • the web dashboard for fleet partners and administrators at www.emaride.lu/app,
  • the Emaride mobile app for customers, drivers, and fleet partners (iOS and Android).

Date of this statement: 2026-10-13.

2. Conformance status

These offerings are partially conformant with WCAG 2.2 AA / EN 301 549. The content that does not yet meet the requirements and the limits of the checks carried out so far are listed in section 3.

3. Non-accessible content

3.1 PDF documents (WCAG 1.3.1, 1.3.2)

Invoices, receipts, and PDF exports are not tagged: they contain no structure (headings, tables, reading order) that a screen reader can use. Arabic text is stored in display order and is therefore not read out in the correct order. The document language and title are set.

As alternatives:

  • Newly issued invoices can be viewed as text in the web dashboard ("View as text"). Invoices issued before this view was introduced have no text version.
  • Every PDF export of a table is accompanied by a CSV export.
  • In the app, the details of an invoice are also shown as text on screen.

3.2 Mobile app until the next app version (WCAG 1.3.1, 1.3.4, 1.4.4, 2.2.1, 2.4.3, 4.1.2, 4.1.3)

The improvements to the app have been implemented but will only reach the stores with the next app version; we cannot give a date yet. Until then, the currently available app has the following limitations:

  • Error messages and status changes (for example "Driver has arrived") are not consistently announced by screen readers.
  • Input fields, including the code entry, do not always pass their label to the screen reader; errors are not linked to the field.
  • The star rating, some switches, and selection fields do not announce their state or value.
  • Focus is not managed when dialogs open and close.
  • The response deadline of a ride offer for drivers is not announced.
  • With a large system font, some texts are cut off.
  • The app is locked to portrait orientation.

3.3 Maps (WCAG 2.1.1, 1.1.1)

The map surfaces themselves (live map in the dashboard, map views in the app) cannot be fully operated by keyboard or screen reader. The content is also available without the map: drivers with an ongoing ride can be reached as named buttons, active rides are also shown as a list, zone blocks can be entered as coordinates or GeoJSON, and addresses and arrival times appear as text.

3.4 Third-party content

The payment form of the payment service provider Stripe and the map data from Mapbox are provided by third parties. We have no direct influence on their accessibility.

3.5 Tests with assistive technology are pending

The checks are automated (section 4). No test with screen readers on real devices — VoiceOver (iOS), TalkBack (Android), and desktop screen readers — has taken place yet. For the app, there is also no measurement with a large system font on devices.

4. Preparation of this statement

This statement was prepared on 2026-10-13. It is based on a self-assessment using automated checks in the source code:

  • axe-core with the rules for WCAG 2.0, 2.1, and 2.2 (levels A and AA) on every page of the website and the dashboard in its initial state (without open dialogs), without login and with test accounts for fleet partners, administration, and business customers, in German and Arabic,
  • static analysis of the web interface (eslint-plugin-jsx-a11y),
  • keyboard tests on selected pages (reachability, visible focus, focus trap and focus return in dialogs) on desktop and at a width of 360 px,
  • contrast checks of the design's colour values in light and dark mode (text 4.5:1, focus ring, field borders, and switches 3:1),
  • every page at a width of 320 px without horizontal scrolling and with controls of at least 24×24 px, every page with a title,
  • for the app, automated checks for controls, images, and fields without an accessible name.

No external audit (e.g. by an independent testing body) has taken place.

5. Feedback and contact

If you encounter a barrier that makes it difficult for you to use our services, please let us know.

Please report barriers by email to support@emaride.lu (subject "Accessibility"). This address is expressly also responsible for accessibility reports.

6. Enforcement procedure

If you are not satisfied with the response to your report, you can contact the competent enforcement body.

In Luxembourg, this is the Office de la surveillance de l'accessibilité des produits et services (OSAPS), established by the Law of 8 March 2023 on the accessibility requirements for products and services — email info@osaps.etat.lu, phone +352 24 77 65 55.