Accessibility
Qafilaa is a safety product. If a rider cannot read the screen that tells them their crew is two kilometres back, that is a safety failure and not a cosmetic one. This is an honest account of where we are, including the parts we have not finished.
- We aim at WCAG 2.2 level AA for this website and for the app.
- We are partially conformant. The gaps are listed below rather than hidden.
- Reduced-motion settings are respected. The site stops animating if you ask it to.
- Email admin@qafilaa.in and a person will answer. That is the accessible support channel.
What this covers
The qafilaa.in website, and the Qafilaa app on iOS and Android. Both are made by Qafilaa.in, Kolhapur, Maharashtra. Contact details are on the Contact page.
What works today, on this site
- Reduced motion. If your system asks for less motion, the scroll journey stops moving: no flying device, no staggered reveals, no typed text. Everything is simply there.
- Keyboard. A skip link is the first focusable element. Every control has a visible focus ring. J and K move between sections, ? lists shortcuts, Esc closes.
- Screen readers. Each section is a landmark with a name. The decorative device mockups are marked as images and removed from the tab order, so you are not walked through several hundred controls that do nothing.
- Target size. Interactive controls are at least 44 px on their smallest side.
- Text. Body text is set at 17 px and up, and reflows to a single column without horizontal scrolling down to 320 px wide.
- Live regions. Status that changes without a page load — an alert countdown, a form result — is announced.
Where we fall short
Stated plainly, because a statement that claims full conformance is usually not true:
- No independent audit yet. These claims come from our own testing, not a third-party assessment. We will name the assessor here when there is one.
- The home page is a scroll narrative. It is navigable by keyboard and readable by a screen reader, but it is long, and a linear read is a slow way to reach a specific fact. The Help centre and these policy pages are plain documents and are the faster route to an answer.
- Some contrast is at the boundary. The small uppercase labels meet AA at their size but are deliberately quiet. If any of them are hard for you to read, tell us — that is exactly the report we want.
- The map is visual. A live convoy map is inherently spatial. Distances, gaps and rider states are also available as text in the crew list and the muster board, but the map itself is not a substitute-free experience yet.
- The app has not been fully audited against VoiceOver and TalkBack end to end. Core flows work; we are not going to claim more than that.
If something is not usable
If you need something from this site in another format — a policy read out, or sent as plain text — ask and we will send it.
Riding-specific settings worth knowing
- Battery mode reduces how often your position updates on long legs and restores it near passes.
- Alerts can be reduced to essentials only for the rest of a trip with a single switch.
- Manual SOS has three routes in — tap, hold the overlay, or flip the phone — because gloves and adrenaline are real.
- Recap and share cards have a dark variant for low light.
Standing behind this
This statement was prepared on 20 August 2026 by self-assessment of the current release, and is reviewed whenever the site or the app changes materially. If you think it overstates what we deliver, that is a report we want: admin@qafilaa.in.