मुख्य सामग्री पर जाएँ
Accessibility

Accessibility statement

What we aim for, what is actually built in, and what we know is still missing. The gaps are here on purpose — a statement with no gaps is one nobody checked.

Version 2026-09-24

What we are aiming for

WCAG 2.1 at Level AA, across both languages this site publishes in. We treat that as a floor to clear on every page we ship, not a badge to earn once and stop checking.

This is a stated aim, not a certification — nobody has audited this site against the full standard with real assistive technology across every page, and this statement will keep saying so until that has actually happened.

What is actually built in

A skip link on every showcase page, before the header, for anyone navigating by keyboard.

Filter results, search-parse chips and the offer table's sort order are all announced to a screen reader as they change, and the page moves focus to the result count after a filter changes it — not just to whoever happens to still be listening.

Colour is never the only signal: a link inside a paragraph is underlined, a sortable table column carries `aria-sort` plus a visible arrow, not just a colour change.

Motion, and now transparency, both back off when the operating system says to. Nothing on this site plays a looping animation at a screen reader — the one animated beat on a product page keeps its text in the DOM throughout, opacity is the only thing that moves.

A link that hands off to WhatsApp in a new tab says so in the link text, not only in `target="_blank"`.

Hindi headings get their own minimum line-height — the Latin display face's tight leading clips Devanagari vowel marks if it is not corrected for that script specifically.

The shop listing form collects its validation errors into one linked summary at the top on a failed submit, focused so it's what's read next — the quote-request form has no per-field errors to summarise in the first place, only a single whole-form message, so the same fix doesn't apply there.

Every personal field (phone, email — no postal code exists anywhere, since every listing shares one Nehru Place pincode) carries the right autocomplete token, and the two in-table escape-hatch links this pass found under a real 24px tap target ("Report wrong price", "Call ahead") now have one.

What we know is still missing

No product photography exists in the catalogue yet, so there is no image alt-text policy to audit — that is a gap in the feature, not yet a gap in its accessibility.

Every icon-only button's Hindi label has been checked in the places this pass touched, not audited end to end across the whole site.

Nobody has yet tested this site with TalkBack in Hindi specifically — Devanagari text alongside monospaced prices is a combination screen-reader testing here has not covered.

Tell us what we missed

If something on this site does not work with the keyboard, a screen reader, or magnification, we want to know which page and what happened — that is more useful to us than a general report that accessibility is bad somewhere.

Reach us through the contact page. We do not have a dedicated accessibility inbox yet; a report there reaches the same person who reads everything else.

Questions about any of this go through the contact page.