Delivery should work for everyone.
We are building MXLaMove so that customers, drivers, fleets and operations teams can use it with a keyboard, a screen reader, magnification or a touch screen. This page explains where we are and how to tell us when something does not work.
Current status
Partially conformant with WCAG 2.2 AA
The web application meets many Level A and AA checks, but it is not yet fully conformant. Remaining gaps include some incomplete data relationships and verification of live announcements with human screen-reader users. Order, dispatch and driver-location updates now use polite status regions across customer tracking and the admin order, dispatch and live-operations surfaces. A skip-to-content link now bypasses navigation on every shell. This is a self-assessment, not a certification.
Our commitment
Accessibility is part of how we build, not a separate project. We aim to meet WCAG 2.2 Level AA across public pages and the authenticated web portals. We review the shared shells, forms, tables and maps as they change, and we record defects with an owner and a priority rather than treating conformance as a one-time checklist.
- Semantic landmarks, headings, labels and table markup in the shared shells.
- A visible keyboard focus ring and managed focus for dialogs and the mobile navigation drawer.
- Responsive checks at phone, tablet and desktop widths, including landscape.
- Reduced-motion support and text alternatives for charts, illustrations and maps.
- Accessible authentication with password managers, autocomplete and paste-friendly one-time codes.
What this statement covers
Public marketing, help, legal and tracking pages, plus the authenticated customer, business, fleet, driver and admin web portals.
Native iOS and Android apps, third-party map tiles, payment-provider hosted pages and partner systems are outside this report.
The native iOS and Android apps are built and released separately. Their accessibility has not been covered by this web report and needs its own device and screen-reader evaluation.
Known limitations
These are the issues we know about today. The detailed report records the affected WCAG criteria and the remediation work.
Some card groups and secondary fields remain implicit
1.3.1 / 1.3.5 · Medium priorityDense dashboard cards and a few secondary forms still rely on visual layout rather than programmatic grouping or input-purpose tokens.
No human screen-reader or third-party audit yet
Evaluation gap · High priorityThe browser accessibility-tree audit found structural gaps, but it cannot hear announcements or judge the experience with NVDA, JAWS, VoiceOver or TalkBack.
Feedback and alternative access
If a page, form or message is difficult to use, tell us what happened and which page you were on. Include the browser, device and assistive technology you used if you can. We aim to acknowledge accessibility reports within five business days and will offer a workable alternative while a fix is in progress.
- Phone
- +91 80000 00000
If you are not satisfied with our response, ask for it to be escalated to the accessibility lead. This statement and the conformance report are reviewed at least every three months and after a material change to the booking, tracking, dispatch or payments flows.
Statement version 1.0 · published .