FixMyCity — Accessibility
Last updated: 2026-09-21
This is a civic record for a whole city, so it has to be usable by the whole city. This page says where we have got to, honestly, including what does not work yet.
We aim at WCAG 2.2 Level AA. We have not been independently audited against it, so treat the claims below as our own testing rather than a certification.
What we have done
The app
- Every control has a spoken label, and links announce themselves as links — including the source links beside your MLA and MP, which a screen reader reads as "opens in your browser".
- Text scales with the system font size. Layouts are clamped rather than allowed to overflow, so a larger setting makes text bigger instead of cutting it off.
- Colour is never the only carrier of meaning: a status has a word as well as a colour.
- The whole reporting flow works without typing. If you would rather speak than type, the note step takes dictation.
- Tap targets are sized for a thumb, not a stylus.
- Photographs are the evidence, so they cannot be replaced by text — but every report carries its place, its date and its category as text, and those are what a screen reader reads out.
The website
- One column, real text, no text baked into images.
- Contrast on body text and controls meets AA.
- It works at 200% zoom and on a phone held either way.
What does not work well yet
Saying this plainly is more useful than a clean-looking claim.
- The map is visual. Panning a map of open issues has no equivalent for someone who cannot see it. The feed and search cover the same reports as a list, and that is the route we would point you to today — but it is a substitute, not an equal.
- Kannada is incomplete. The app has Kannada strings, and several screens — sign-in, consent, and the area setup — are still English only. A bilingual city deserves better and this is being fixed.
- No independent audit. Planned, not done.
- Our own contrast checks are automated. Automated checks catch perhaps half of what a person using the product would notice.
Tell us
If something here keeps you out, that is a defect and we want it filed like one: support@orrgo.com. Tell us the screen and what you were using — VoiceOver, TalkBack, a larger font, a switch device. We will say what we can do and by when, rather than thanking you for the feedback.
If the answer does not satisfy you, the Grievance Officer route is open for this as for anything else.