सुगम्यता

Grihvatika targets WCAG 2.2 level AA. This page says what that means in practice, what we have tested, and what is still open — because an accessibility statement that only makes claims is not much use.

What is built in

Keyboard — every link, button, filter chip, accordion and form field is reachable and operable by keyboard, in a sensible order. A Skip to content link is the first thing you reach and becomes visible when focused.

Visible focus — a 2px accent outline on every interactive element, shown for keyboard use and never removed.

Forms — every field has a real label. When something is wrong we say what is wrong, in words, next to the field and in a message at the top of the form that screen readers announce — never a red border alone.

Headings — one H1 per page, then H2 and H3 in order, so a screen reader can be used to navigate rather than read.

Images — photographs that carry meaning have text alternatives; decorative ones are hidden from screen readers. No instruction, sowing month or plant name exists only inside an image.

Contrast — body text sits at 4.5:1 or better against its background, large text and interface chrome at 3:1 or better.

Motion — we honour prefers-reduced-motion: transitions and hover movement stop when your system asks for that.

Zoom and touch — the layout reflows to 400% zoom and down to a 320px screen without horizontal scrolling. Form fields are 16px on mobile so iOS does not zoom on focus, and buttons, nav links and accordions are large enough to hit with a thumb.

Known gaps

Some older plant photographs still need better alternative text. PDFs we send on request are not yet tagged for screen readers — ask and we will send the content as accessible HTML or plain text instead. Hindi content relies on your browser having a Devanagari font.

Tell us

If something on this site blocks you, write to us through the Contact page and say what you were trying to do. We treat access faults as bugs, not requests.