[ accessibility ]
usable by EVERYONE
Aangan Last updated: [06/08/2026]
Aangan should be usable by everyone in Pakistan, including people who browse with a keyboard, a screen reader, a magnifier, or with animation turned off. If it is not usable for you, that is a bug, and we want to hear about it.
What we have done
Keyboard navigation
- Every link, button, filter, form field and dialog can be reached and operated with the keyboard alone
- A visible focus ring follows you as you tab, drawn in our green so it is easy to spot on the warm paper background
- A "skip to content" link is the first thing you reach on every page, so you do not have to tab through the navigation each time
Screen reader support
- Pages use real landmarks — header, navigation, main and footer — so you can jump straight to the part you want
- One heading level one per page, with headings nested in order beneath it
- Images carry a description of what they show; images that are purely decorative are hidden from screen readers instead of being announced as noise
- Form fields have real labels, not just placeholder text, and errors are announced when they appear
- The large hero headline is announced as the sentence it is meant to be, rather than as its three separate visual lines
Contrast
- Text and background pairs are checked against WCAG 2.1 AA — 4.5:1 for body text and 3:1 for large text
- The muted grey used for secondary text was too light on warm paper, so it has been darkened
- A high contrast setting in the footer removes the remaining softness if you want it
Motion
- If your device asks for reduced motion, we honour it: parallax, scroll sequences, drifting illustrations, the marquee and page transitions all stop
- If your device does not ask for it but you want it anyway, the reduce motion switch in the footer does the same thing
- No content depends on animation to be understood
Text size
- The site reflows down to 320px wide and at 200% browser zoom
- The footer also offers two larger text settings, which persist on your device
The map
- Every place on the map is also listed as plain text next to it, with its category, whether it is open, whether it is free, its distance and its address
- The list is keyboard navigable and screen reader readable, so you can find a 24-hour vet without ever touching the map itself
- Emergency numbers are written out as text and as callable links
What we know is not right yet
We are not claiming full WCAG 2.1 AA compliance. These are the parts we know still fall short:
- The map itself is a Leaflet map. The list beside it is the accessible route, but panning and zooming the map with a keyboard is limited
- The mobile map list opens in a draggable sheet. It can be read and operated, but the drag handle has no keyboard equivalent yet
- Some illustrated sections carry meaning in the drawing that is not fully described in text
- We have tested with VoiceOver and with keyboard-only browsing. We have not yet tested thoroughly with NVDA, JAWS or TalkBack
- No part of the site has been audited by an accessibility professional
- Urdu screen reader support has not been tested at all
- Photographs uploaded by other users do not yet have descriptions written by the people who upload them. We want to add that field
We would rather list these plainly than claim a level of compliance we have not earned.
Telling us something is broken
Email aangan.karachi@gmail.com.
It helps if you can say what page you were on, what you were trying to do, and what device, browser or assistive technology you were using — but do not let missing any of that stop you from writing. A single sentence is enough.
Accessibility problems are treated as bugs, not as feature requests. We fix them ahead of new work.