Everyone needs to get home.
What we've done to make this site usable however you browse it, what we know still falls short, and how to tell us when we've got it wrong.
What we've built in.
We aim to meet WCAG 2.2 Level AA. That is a target, not a certification — no independent audit has been carried out yet, and we would rather say so than imply one.
What is in place
- Contrast. Every text and background pair on this site has been measured against the AA thresholds — 4.5:1 for body text, 3:1 for large text. Where a brand colour failed, the colour changed rather than the standard.
- Keyboard. Everything interactive is reachable and operable by keyboard, with a visible focus ring on every control. A skip link jumps past the navigation to the content.
- Structure. Real headings in order, landmark regions, and labels on every form field — so a screen reader announces the page rather than reading a wall of text.
- Motion. All animation respects
prefers-reduced-motion. With it enabled, content appears rather than sliding, and nothing pulses. - Zoom and reflow. Text scales to 200% without loss of content, and the page reflows to a single column on narrow screens without horizontal scrolling.
- Status messages. Search results, form errors and chat replies are announced politely, so they are not missed by someone not looking at the screen.
Where we know we fall short
Listing these is more useful than claiming they don’t exist:
- No independent accessibility audit has been done. Everything above is our own testing.
- The site is English-only today. For a service operating across India that is a real accessibility gap, not just a localisation one.
- The fare estimator relies on a dropdown of preset routes; it has not been tested with every combination of screen reader and browser.
Riding and driving.
The Snapp apps use the platform’s own accessibility support, so system text size, display scaling, TalkBack and VoiceOver all work as they do elsewhere on your device.
Some things are harder in an app that is mostly a live map. If a part of the app is unusable for you, tell us specifically what you were trying to do — that is far more actionable than a general report, and it is how these get fixed.
If we've got something wrong.
Write to us through the contact form, or email support@snappcab.in. Tell us the page or screen, what you were trying to do, and what got in the way — including the assistive technology you use, if you’re happy to.
We treat these the way we treat any other report: acknowledged within 24 hours, and escalatable through our grievance processif we don’t sort it out.