WCAG 2.2 AA conformance report
A criterion-level record of where the MXLaMove web application supports, partially supports or does not yet support WCAG 2.2 Level A and AA, with the evaluation limits stated up front.
Overall result
Partially conformant
The web application is not fully conformant with WCAG 2.2 Level AA. This report is a self-assessment baseline, not a certificate or an independent audit. It covers the shared web shells and the routes listed in the statement; native apps and third-party hosted content are outside scope.
The most significant remaining blocker is the absence of a human screen-reader or third-party audit. Live order, dispatch and driver-location changes now use polite status regions on customer tracking and the admin order, dispatch and live-operations surfaces. The skip-to-content link, muted-text contrast and control-boundary contrast pass and are covered by browser tests.
Report details
- Product
- MXLaMove web application
- Standard
- WCAG 2.2 Level AA
- Report version
- 1.0
- Published
- Last reviewed
- Next review
Criterion summary
55 Level A and AA success criteria assessed. “Not evaluated” means the product has not yet been tested against that criterion; it is not a pass.
Scope
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.
Evaluation methods
Source review against the WCAG 2.2 success criteria, the existing Playwright keyboard and responsive checks, route-level accessibility invariants across every static admin, business, fleet, customer and driver route, and manual spot checks of the shared shells and auth flows. Browser accessibility-tree and keyboard audits of booking, tracking, addresses, recipients, live operations and CRM were run on 16 November 2026; no human screen-reader or third-party audit has been completed.
Success criteria
Each row is a WCAG 2.2 Level A or AA success criterion. “Partially supports” means the criterion works in common flows but has a known gap; it is not a claim of conformance.
1. Perceivable
Information and interface components must be presentable in ways all users can perceive.
| Criterion | Level | Status | Assessment |
|---|---|---|---|
| 1.1.1Non-text content | A | Partially supports | Decorative SVGs are hidden and charts and map illustrations carry labels. User-uploaded proof images rely on surrounding text and still need a full alt-text audit. |
| 1.2.1Audio-only and video-only (prerecorded) | A | Not applicable | No prerecorded audio-only or video-only content is published in the product. |
| 1.2.2Captions (prerecorded) | A | Not applicable | No prerecorded video with audio is published in the product. |
| 1.2.3Audio description or media alternative (prerecorded) | A | Not applicable | No prerecorded video is published in the product. |
| 1.2.4Captions (live) | A | Not applicable | No live audio or video streams are part of the product. |
| 1.2.5Audio description (prerecorded) | AA | Not applicable | No prerecorded video is published in the product. |
| 1.3.1Info and relationships | A | Partially supports | Landmarks, headings, tables and form labels are used across shared shells. Address and recipient forms use fieldset/legend groups and booking stops are grouped per stop. Some data-card grids and map panels still do not expose every visual relationship programmatically. |
| 1.3.2Meaningful sequence | A | Supports | DOM order follows the visual reading order, including the mobile navigation dialog. |
| 1.3.3Sensory characteristics | A | Supports | Instructions do not rely on shape, size, sound or location alone. |
| 1.3.4Orientation | AA | Supports | Responsive layouts support portrait and landscape; orientation is not restricted. |
| 1.3.5Identify input purpose | AA | Partially supports | Autocomplete is set on the auth forms, address, recipient and booking contact/address fields, the customer profile and the business-upgrade form. Some secondary business contact forms are not consistently annotated. |
| 1.4.1Use of colour | A | Partially supports | Status pills include text as well as colour. Some chart series and map markers rely on colour for identification. |
| 1.4.2Audio control | A | Supports | No audio plays automatically. |
| 1.4.3Contrast (minimum) | AA | Supports | Muted metadata now uses #5F6469, about 5.6:1 on cream and 5.9:1 on white, above 4.5:1 for normal text. The accessibility browser spec checks the computed footer colour against its background. |
| 1.4.4Resize text | AA | Partially supports | Responsive layout and browser zoom work, but 200% text-only scaling has not been formally tested. |
| 1.4.5Images of text | AA | Supports | The wordmark and headings are text, not images of text. |
| 1.4.10Reflow | AA | Partially supports | Playwright checks show no page-level horizontal overflow at 360, 768, 844 and 1024 CSS pixels. 320px and 400% reflow are not covered. |
| 1.4.11Non-text contrast | AA | Supports | Inputs, selects and bordered buttons use #8A8178 control borders, about 3.5:1 on cream and 3.8:1 on white. The focus ring uses #C2410C, above 3:1 on light and dark surfaces. Decorative card dividers remain intentionally subtle because they are not control boundaries; the accessibility browser spec checks an input border against its background. |
| 1.4.12Text spacing | AA | Not evaluated | The product has not been tested with the WCAG text-spacing overrides. |
| 1.4.13Content on hover or focus | AA | Partially supports | Most hover treatments have a focus equivalent, but popovers and dense table hover content have not been exhaustively checked for dismissibility. |
2. Operable
Interface components and navigation must be operable by keyboard and assistive input.
| Criterion | Level | Status | Assessment |
|---|---|---|---|
| 2.1.1Keyboard | A | Supports | Native links, buttons and forms are keyboard operable. The live driver map has button controls plus arrow-key pan, +/− zoom and Home reset. CRM cards use a native stage select and an explicit Move button, so choosing a stage with the keyboard does not save until Move is activated. |
| 2.1.2No keyboard trap | A | Supports | The mobile drawer closes with Escape and returns focus to its trigger; this is covered by Playwright. |
| 2.1.4Character key shortcuts | A | Supports | No single-character keyboard shortcuts are implemented. |
| 2.2.1Timing adjustable | A | Partially supports | Quote expiry is shown as a countdown, but there is no control to extend the time limit. |
| 2.2.2Pause, stop, hide | A | Partially supports | Reduced-motion preferences are honoured. The marquee pauses on hover but not through a keyboard-operable control. |
| 2.3.1Three flashes or below threshold | A | Supports | No flashing content is used. |
| 2.4.1Bypass blocks | A | Supports | A skip-to-content link is the first tab stop on marketing, auth, portal, driver, tracking and access-restricted pages. It moves focus to the main landmark; covered by the Playwright accessibility spec. |
| 2.4.2Page titled | A | Partially supports | Booking, tracking, addresses, recipients, dispatch, live operations and CRM now set route-specific titles. Many secondary admin routes still inherit the root title. |
| 2.4.3Focus order | A | Partially supports | Focus generally follows DOM order and drawer focus is managed. Complex maps and dense tables have not been fully audited. |
| 2.4.4Link purpose (in context) | A | Partially supports | Icon-only controls have accessible names. Some repeated “View” and “Open” links do not include the record name in their accessible name. |
| 2.4.5Multiple ways | AA | Partially supports | Global navigation, search and in-page links exist. There is no sitemap and not every deep page has more than one route. |
| 2.4.6Headings and labels | AA | Partially supports | Shared shells use headings and labels. Some dense admin filters use placeholders without a persistent visible label. |
| 2.4.7Focus visible | AA | Supports | A global :focus-visible rule draws a 2px ring with a 2px offset. |
| 2.4.11Focus not obscured (Minimum) | AA | Not evaluated | Sticky headers and drawers have not been tested for obscuring focused content at every viewport. |
| 2.5.1Pointer gestures | A | Supports | No path-based or multipoint gestures are required to operate a control. |
| 2.5.2Pointer cancellation | A | Supports | Actions use native click/up activation; there are no down-event-only actions. |
| 2.5.3Label in name | A | Partially supports | Visible labels generally match accessible names. Icon-only controls depend on aria-label and need a full pass. |
| 2.5.4Motion actuation | A | Supports | No functionality is triggered by device motion. |
| 2.5.7Dragging movements | AA | Supports | The map exposes pan/zoom without dragging, and every CRM card exposes a native stage selector plus an explicit Move button, so no pointer-only movement is required. |
| 2.5.8Target size (Minimum) | AA | Partially supports | Most controls meet 24px. Several 32px icon buttons are below the 44px touch-target guidance used by the design system. |
3. Understandable
Content and operation must be understandable, predictable and forgiving of mistakes.
| Criterion | Level | Status | Assessment |
|---|---|---|---|
| 3.1.1Language of page | A | Supports | The root document sets lang from the selected locale. |
| 3.1.2Language of parts | AA | Partially supports | Hindi interface strings exist, but inline language changes are not marked with lang attributes. |
| 3.2.1On focus | A | Supports | Focusing a control does not change context. |
| 3.2.2On input | A | Supports | Entering data does not automatically submit or change context except where a submit button is explicit. |
| 3.2.3Consistent navigation | AA | Supports | Marketing and portal shells keep navigation in a consistent order. |
| 3.2.4Consistent identification | AA | Supports | Shared components use consistent labels and icons for the same actions. |
| 3.2.6Consistent help | A | Partially supports | Support links are consistent in the main shells but not present on every flow. |
| 3.3.1Error identification | A | Partially supports | Auth forms use role="alert" and descriptive messages. Other forms have not all been audited. |
| 3.3.2Labels or instructions | A | Partially supports | Labels and helper text exist on auth and key booking forms. Some admin filters use placeholder-only fields. |
| 3.3.3Error suggestion | AA | Partially supports | Auth errors suggest a correction. Not every form validates with an actionable suggestion. |
| 3.3.4Error prevention (legal, financial, data) | AA | Partially supports | Destructive and financial actions have confirmations. Not every data-changing action has review, confirmation or undo. |
| 3.3.7Redundant entry | A | Partially supports | Booking keeps data within the flow. Re-entering the same information across related flows has not been audited. |
| 3.3.8Accessible authentication (Minimum) | AA | Partially supports | Password managers and autocomplete are supported, and OTP codes can be pasted. No cognitive-function test or passkey flow is available. |
4. Robust
Content must be robust enough to work with current and future assistive technologies.
| Criterion | Level | Status | Assessment |
|---|---|---|---|
| 4.1.2Name, role, value | A | Partially supports | Native controls and labelled icons are used. Booking stops are named per stop, schedule/payment/vehicle/add-on choices expose aria-pressed, tracking uses a labelled code field and list-based timeline, and the live map controls have explicit names and keyboard shortcuts. Route-level invariants check every static role route for unnamed controls, duplicate IDs, positive tabindex and invalid live-region values. |
| 4.1.3Status messages | AA | Partially supports | Form errors use role="alert". Customer order tracking, public tracking, admin order detail, the dispatch board and live operations use polite atomic status regions for order, dispatch and driver-location changes. Polling and SSE surfaces announce paused/offline and resumed connection states without repeating on every poll. The partial status reflects the lack of a human screen-reader pass and async surfaces outside those flows. |
Known defects and remediation
| Criterion | Issue | Impact | Priority | Remediation |
|---|---|---|---|---|
| 1.3.1 / 1.3.5 | Some card groups and secondary fields remain implicit | Dense dashboard cards and a few secondary forms still rely on visual layout rather than programmatic grouping or input-purpose tokens. | Medium | Give remaining grouped cards list/table semantics and add input-purpose tokens to the remaining secondary business contact forms. |
| Evaluation gap | No human screen-reader or third-party audit yet | The browser accessibility-tree audit found structural gaps, but it cannot hear announcements or judge the experience with NVDA, JAWS, VoiceOver or TalkBack. | High | Commission an independent WCAG 2.2 AA audit and test the core booking, tracking and admin flows with at least two screen readers. |
Report feedback
Report a barrier at accessibility@mxlamove.com or call +91 80000 00000. Include the URL, what you were trying to do and the assistive technology you used. We aim to acknowledge reports within five business days.
Read the accessibility statement for our commitment, scope and review cycle.
Report version 1.0 · published · next review .