Skip to content
Same-day windows · every order tracked live
Accessibility report

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

22
Supports
26
Partially supports
0
Does not support
2
Not evaluated
5
Not applicable

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.

1. Perceivable WCAG 2.2 success criteria
CriterionLevelStatusAssessment
1.1.1Non-text contentAPartially supportsDecorative 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)ANot applicableNo prerecorded audio-only or video-only content is published in the product.
1.2.2Captions (prerecorded)ANot applicableNo prerecorded video with audio is published in the product.
1.2.3Audio description or media alternative (prerecorded)ANot applicableNo prerecorded video is published in the product.
1.2.4Captions (live)ANot applicableNo live audio or video streams are part of the product.
1.2.5Audio description (prerecorded)AANot applicableNo prerecorded video is published in the product.
1.3.1Info and relationshipsAPartially supportsLandmarks, 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 sequenceASupportsDOM order follows the visual reading order, including the mobile navigation dialog.
1.3.3Sensory characteristicsASupportsInstructions do not rely on shape, size, sound or location alone.
1.3.4OrientationAASupportsResponsive layouts support portrait and landscape; orientation is not restricted.
1.3.5Identify input purposeAAPartially supportsAutocomplete 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 colourAPartially supportsStatus pills include text as well as colour. Some chart series and map markers rely on colour for identification.
1.4.2Audio controlASupportsNo audio plays automatically.
1.4.3Contrast (minimum)AASupportsMuted 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 textAAPartially supportsResponsive layout and browser zoom work, but 200% text-only scaling has not been formally tested.
1.4.5Images of textAASupportsThe wordmark and headings are text, not images of text.
1.4.10ReflowAAPartially supportsPlaywright 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 contrastAASupportsInputs, 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 spacingAANot evaluatedThe product has not been tested with the WCAG text-spacing overrides.
1.4.13Content on hover or focusAAPartially supportsMost 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.

2. Operable WCAG 2.2 success criteria
CriterionLevelStatusAssessment
2.1.1KeyboardASupportsNative 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 trapASupportsThe mobile drawer closes with Escape and returns focus to its trigger; this is covered by Playwright.
2.1.4Character key shortcutsASupportsNo single-character keyboard shortcuts are implemented.
2.2.1Timing adjustableAPartially supportsQuote expiry is shown as a countdown, but there is no control to extend the time limit.
2.2.2Pause, stop, hideAPartially supportsReduced-motion preferences are honoured. The marquee pauses on hover but not through a keyboard-operable control.
2.3.1Three flashes or below thresholdASupportsNo flashing content is used.
2.4.1Bypass blocksASupportsA 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 titledAPartially supportsBooking, 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 orderAPartially supportsFocus 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)APartially supportsIcon-only controls have accessible names. Some repeated “View” and “Open” links do not include the record name in their accessible name.
2.4.5Multiple waysAAPartially supportsGlobal 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 labelsAAPartially supportsShared shells use headings and labels. Some dense admin filters use placeholders without a persistent visible label.
2.4.7Focus visibleAASupportsA global :focus-visible rule draws a 2px ring with a 2px offset.
2.4.11Focus not obscured (Minimum)AANot evaluatedSticky headers and drawers have not been tested for obscuring focused content at every viewport.
2.5.1Pointer gesturesASupportsNo path-based or multipoint gestures are required to operate a control.
2.5.2Pointer cancellationASupportsActions use native click/up activation; there are no down-event-only actions.
2.5.3Label in nameAPartially supportsVisible labels generally match accessible names. Icon-only controls depend on aria-label and need a full pass.
2.5.4Motion actuationASupportsNo functionality is triggered by device motion.
2.5.7Dragging movementsAASupportsThe 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)AAPartially supportsMost 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.

3. Understandable WCAG 2.2 success criteria
CriterionLevelStatusAssessment
3.1.1Language of pageASupportsThe root document sets lang from the selected locale.
3.1.2Language of partsAAPartially supportsHindi interface strings exist, but inline language changes are not marked with lang attributes.
3.2.1On focusASupportsFocusing a control does not change context.
3.2.2On inputASupportsEntering data does not automatically submit or change context except where a submit button is explicit.
3.2.3Consistent navigationAASupportsMarketing and portal shells keep navigation in a consistent order.
3.2.4Consistent identificationAASupportsShared components use consistent labels and icons for the same actions.
3.2.6Consistent helpAPartially supportsSupport links are consistent in the main shells but not present on every flow.
3.3.1Error identificationAPartially supportsAuth forms use role="alert" and descriptive messages. Other forms have not all been audited.
3.3.2Labels or instructionsAPartially supportsLabels and helper text exist on auth and key booking forms. Some admin filters use placeholder-only fields.
3.3.3Error suggestionAAPartially supportsAuth errors suggest a correction. Not every form validates with an actionable suggestion.
3.3.4Error prevention (legal, financial, data)AAPartially supportsDestructive and financial actions have confirmations. Not every data-changing action has review, confirmation or undo.
3.3.7Redundant entryAPartially supportsBooking keeps data within the flow. Re-entering the same information across related flows has not been audited.
3.3.8Accessible authentication (Minimum)AAPartially supportsPassword 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.

4. Robust WCAG 2.2 success criteria
CriterionLevelStatusAssessment
4.1.2Name, role, valueAPartially supportsNative 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 messagesAAPartially supportsForm 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

Known accessibility defects, impact, priority and remediation
CriterionIssueImpactPriorityRemediation
1.3.1 / 1.3.5Some card groups and secondary fields remain implicitDense dashboard cards and a few secondary forms still rely on visual layout rather than programmatic grouping or input-purpose tokens.MediumGive remaining grouped cards list/table semantics and add input-purpose tokens to the remaining secondary business contact forms.
Evaluation gapNo human screen-reader or third-party audit yetThe browser accessibility-tree audit found structural gaps, but it cannot hear announcements or judge the experience with NVDA, JAWS, VoiceOver or TalkBack.HighCommission 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 .