Accessibility
What we test, and what we know is imperfect.
We build to WCAG 2.2 AA and test against it. What falls short is listed below.
The standard
This site targets WCAG 2.2 Level AA. That is the level referenced by most procurement requirements and by India’s Rights of Persons with Disabilities Act guidance for digital services.
What we actually do
- Every colour pair is checked against the contrast requirement as part of the design system, not after the fact. One of our neutral steps exists solely because the one above it measured 3.89:1 and failed.
- Every animation has a
prefers-reduced-motionpath that settles to the final state. The scrolling testimonial wall becomes a plain list; the reading progress bar stops easing. - Interactive elements are reachable and operable by keyboard. The search dialog opens with ⌘K, moves with arrows and closes with Escape.
- Drag interactions in the admin always have a non-drag equivalent, because native drag-and-drop works with neither a keyboard nor a touchscreen.
- Images carry alt text, and decorative ones are hidden from assistive tech.
- One
h1per page, and heading levels do not skip.
Known gaps
- The services mega-menu opens on hover as well as focus. It is keyboard operable, but the hover behaviour can be fiddly with a trackpad at small sizes.
- Rich text entered through the admin — case study and article bodies — depends on whoever wrote it. We sanitise the markup; we cannot guarantee somebody used headings in order.
- Client logos on the homepage rail are de-saturated until hovered. The names are in the alt text, so nothing is lost, but the visual treatment is lower contrast than the rest of the page by design.
Fixed since this page was written
- A skip-to-content link now precedes the header. Before it, reaching the main content by keyboard meant tabbing past the announcement bar, the logo, five menu triggers, search and a call-to-action — on every page.
Telling us
If something here does not work for you, please say so — email hello@brihatinfotech.com and describe what you were trying to do. We treat accessibility reports as defects rather than as feedback, which means they go into the same queue as anything else that is broken.
This statement is reviewed whenever the design system changes materially.
Next step
Bring us the problem. We will bring the architecture.
A discovery call takes forty-five minutes. You leave with our read on the problem, the shape of the system we would propose, and a straight answer on whether we are the right team for it.
- No sales deck
- An engineer on the call, not an account manager
- NDA before you share anything

