Accessibility
Last updated · Aqualeo India Pvt Ltd
What we are aiming for
We are working towards WCAG 2.2 Level AA, the standard referenced by India’s Guidelines for Indian Government Websites and by the Rights of Persons with Disabilities Act 2016. We are not claiming full conformance today. The gaps below are the honest list.
What is built in already
- Tap targets of at least 44×44 pixels on every navigation link, button and form control. This is a floor in our design system, not a target.
- A visible focus ring on everything reachable by keyboard, so you can always see where you are without a mouse.
- Status is never colour alone.Anything that says “verified”, “pending” or “granted” carries an icon and a word as well as a colour, so it still reads if you cannot distinguish the colours.
- Text contrast is checked in both light and dark themes, and the theme follows your operating system unless you override it.
- The page language is declared correctly. When you read the app in Hindi, Bengali, Tamil, Kannada, Telugu, Malayalam, Marathi, Gujarati, Odia or Assamese, screen readers are told which language it is, so pronunciation and line-breaking follow that script rather than English rules.
- Text resizes. Layouts use relative units, so increasing your device or browser text size enlarges the app instead of clipping it.
- Forms have real labels, and errors are described in text next to the field they belong to.
Known gaps
You should hear these from us rather than discover them at the worst moment. As of the date at the top of this page:
- The map view on listings has no equivalent non-map way to browse by area yet. The locality filters in the list view are the workaround; a fuller text-based area browser is planned.
- Alt text on listing photos is written by advertisers, so quality varies. We do not yet require it.
- Some longer flows — identity verification, and the house agreement steps — have not been tested end to end with a screen reader. We expect problems there and have not found them all.
- There has been no formal third-party audit. Everything above is our own testing.
- Translated screens have had far less accessibility testing than the English ones.
Using FlatJugaad with assistive technology
This is a standard website, so your own tools work with it: browser zoom, system text size, high-contrast and dark modes, VoiceOver on iOS and macOS, TalkBack on Android, NVDA and JAWS on Windows. You do not need a separate accessible version, because there is not one — there is one product and it is meant to work.
If you use a screen magnifier or a very large text size, the phone-width layout is usually easier than the desktop one, even on a large screen.
Tell us when something blocks you
Email accessibility@flatjugaad.in. It helps if you can say what you were trying to do, which page you were on, and what device, browser and assistive technology you were using — but please write even if you cannot give all of that. A one-line “I cannot get past the phone number step with VoiceOver” is a useful report.
We aim to reply within 5 working days and to tell you either how to work around it now or when we expect to fix it. If something stops you completing a task that matters — sending an interest on a room, reporting a person — say so, and we will help you do it another way in the meantime.
Escalating
If we have not resolved an accessibility complaint to your satisfaction, escalate to our grievance officer at grievance@flatjugaad.in. You also retain your rights under the Rights of Persons with Disabilities Act 2016, including complaining to the Chief Commissioner for Persons with Disabilities or to your State Commissioner.