Built for everyone
We target WCAG 2.1 Level AA compliance across the public LocalSaathi experience. Our last full audit closed in Q1 2026 — here's what that means in practice.
What we do today
Six commitments we hold ourselves to on every public page.
Keyboard navigation
Every interactive element — forms, modals, menus, tabs — is reachable and operable with Tab / Shift+Tab / Enter / Escape.
Screen-reader friendly
Semantic HTML throughout. Landmark regions (<nav>, <main>, <article>) let NVDA and VoiceOver users jump around fast.
AA colour contrast
Body text ≥ 4.5:1 contrast, UI elements ≥ 3:1 — verified with automated tooling on every deploy.
Readable typography
Minimum 14px body text, scalable up to 200% without horizontal scroll, and no text inside images.
Large touch targets
All tappable elements meet the 44×44px minimum, with generous spacing so thumbs don't misfire.
Form error messages
Errors are announced in real time, tied to the specific field, and never communicated by colour alone.
Known gaps
Every gap we know about, with a concrete remediation target. No sweeping things under the rug.
Some third-party video content lacks captions
Fix: Q2 2026A few older admin screens use colour-only status indicators
Fix: Q2 2026PDF invoice downloads are not yet tagged for screen readers
Fix: Q3 2026Keyboard shortcuts
Power users can move through LocalSaathi without touching the mouse.
Found an accessibility barrier?
If you encounter anything that prevents you from using LocalSaathi, please tell us. We triage accessibility bugs within one business day and ship fixes on priority.