Accessibility Statement

Provider: MiRide Technology (Private) Limited · Effective 13 May 2026

Our commitment to accessibility

MiRide Technology (Private) Limited is committed to making the MiRide website and mobile app usable by as many people as possible, regardless of disability, assistive technology, or browsing context. We believe accessible design is good design, and we are working to embed accessibility into every part of how we build.

This statement covers miride.app and the MiRide mobile app available on the App Store and Google Play.

Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. There are three levels of conformance: Level A, Level AA, and Level AAA.

miride.app is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not yet fully conform to the accessibility standard. A full independent audit has not yet been completed. The specific limitations we are aware of are listed in the Known limitations section below.

The MiRide mobile app has not yet undergone a formal WCAG conformance assessment. We follow platform accessibility guidelines (Apple Human Interface Guidelines and Material Design accessibility guidance) and are working toward a formal audit.

Technical specifications

Accessibility of miride.app relies on the following technologies:

  • HTML5 with semantic landmark elements
  • CSS (Tailwind CSS utility classes) with no inline style overrides that suppress user stylesheets
  • WAI-ARIA roles, states, and properties where native semantics are insufficient
  • SVG for all icons, using aria-hidden="true" on decorative graphics

These technologies are relied upon for conformance. The website is tested in current versions of Chrome, Firefox, and Safari on desktop and mobile.

What we have implemented

Website (miride.app)

  • Semantic HTML structure: every page uses <nav>, <main>, <article>, <section>, and <footer> landmarks with descriptive aria-label attributes
  • Heading hierarchy: a single <h1> per page with a logical descending hierarchy through <h2> and <h3>
  • Keyboard focus: all interactive elements carry a visible focus ring using focus-visible:ring-2 focus-visible:ring-teal-400; focus is never suppressed
  • Colour contrast: the primary teal (#136C75) on white background meets the WCAG 2.1 AA minimum contrast ratio of 4.5:1 for normal text
  • Images: meaningful images carry descriptive alt text; purely decorative SVG icons use aria-hidden="true"
  • Breadcrumb navigation: breadcrumbs use role="list", separator characters are aria-hidden="true", and the active page is marked with aria-current="page"
  • FAQ accordions: built with native <details> and <summary> elements, which are keyboard operable and announced correctly by screen readers without additional ARIA
  • Reduced motion: entrance animations are disabled for users who have set prefers-reduced-motion: reduce at the OS level
  • Text size: body text is set at 1rem (16px), which prevents iOS Safari from triggering unwanted auto-zoom on form inputs; the viewport meta tag does not disable user zoom
  • Language: lang="en" is declared on the <html> element
  • SVG icons: all icons use stroked paths rather than filled bitmaps, so they scale correctly at any zoom level and in high contrast mode

Mobile app (iOS and Android)

  • Platform standard controls are used wherever possible to inherit built-in accessibility behaviour from iOS and Android
  • Minimum touch target sizing follows Apple Human Interface Guidelines (44x44 pt) and Material Design guidelines
  • System text scaling (Dynamic Type on iOS, font size preferences on Android) is supported throughout the app
  • Screen reader testing (VoiceOver and TalkBack) has been conducted on the primary user flows: sign-up, booking a ride, tracking a trip, and payment

Known limitations and what we are working on

We are honest about where we have not yet achieved full conformance. The following limitations are known:

  • No complete independent audit: a full third party WCAG 2.1 AA audit of miride.app has not yet been completed. Some content pages may have conformance gaps we have not yet identified.
  • Older content pages: some less frequently visited pages were built before our current accessibility standards were established and may not fully meet all criteria. We are reviewing these systematically.
  • Skip to main link: a skip navigation link is provided through the BaseLayout but has not been independently verified across all page templates.
  • Mobile app formal audit: the mobile app has not yet undergone a formal WCAG 2.1 AA or EN 301 549 assessment. We plan to commission this before our next major release.
  • Complex map interactions: the map in the app used for ride booking and tracking relies on platform map components (Google Maps SDK). Accessibility of these components is subject to what the platform SDK exposes; we provide text based alternatives for all critical information shown on the map.

We are actively working to address each of these gaps. If you encounter a barrier that is not listed here, please report it using the contact details below.

Feedback and contact

We welcome feedback on the accessibility of MiRide. If you experience any barrier that prevents you from accessing content or completing a task, please let us know so we can address it.

Email: [email protected]

Subject line: Accessibility barrier report

In your message, please describe the barrier you encountered, the page or feature affected, the assistive technology or browser you were using, and your operating system. This helps us reproduce and fix the issue faster.

We aim to acknowledge accessibility reports within 2 business days and to provide a substantive response within 14 business days.

Formal complaints

If you are not satisfied with our response to an accessibility report, you may escalate the matter by writing to MiRide Technology (Private) Limited at:

MiRide Technology (Private) Limited

7 Tweed Road, Eastlea

Harare, Zimbabwe

[email protected]

Assessment approach

MiRide Technology (Private) Limited assessed the accessibility of miride.app through the following methods:

  • Self evaluation: the development team reviews new pages and components against WCAG 2.1 AA success criteria before they are published
  • Automated tooling: browser developer tools and Lighthouse accessibility audits are used during development
  • Screen reader testing: primary flows have been tested with VoiceOver (macOS and iOS) and TalkBack (Android)
  • Keyboard only navigation: all interactive elements are tested without a mouse to verify focus order, operability, and visible focus states

We intend to commission an independent third-party audit and will update this statement with the results.

This statement was prepared on 13 May 2026 by MiRide Technology (Private) Limited. Questions? Email [email protected].