Accessibility: what we test and the known gaps
We build this site to WCAG 2.2 Level AA and test it against that standard. The gaps we know about are listed below.
The standard
This site targets the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Most procurement requirements refer to this level. So does guidance for digital services under India’s Rights of Persons with Disabilities Act.
What we check
- Colour contrast. Every colour pair in the design system is checked against the contrast requirement as the system is built, not afterwards. One of our neutral shades exists only because the shade above it measured 3.89:1 and failed.
- Motion. Every animation has a reduced-motion path that settles on its final state. Scrolling reels become plain lists, and the reading progress bar stops easing.
- Keyboard. Interactive elements can be reached and used with a keyboard. The search dialog opens with ⌘K, moves with the arrow keys and closes with Escape.
- Drag and drop. In the admin, every drag action has another way to do it. Native drag-and-drop works with neither a keyboard nor a touchscreen.
- Images. Images have alt text. Decorative images are hidden from assistive technology.
- Headings. Each page has one main heading (h1), and heading levels never skip.
Known gaps
- Services menu. The services menu opens on hover as well as on keyboard focus. It works with a keyboard, but the hover behaviour can be awkward with a trackpad at small sizes.
- Article and case study text. These bodies are entered through the admin, so their structure depends on the author. We clean the markup, but we cannot guarantee that headings are in order.
Fixed since this statement was first written
- Skip link. A “skip to content” link now comes before 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. That happened on every page.
Report a problem
If part of this site does not work for you, email hello@brihatinfotech.com and describe what you were trying to do. We log accessibility reports as defects, in the same queue as anything else that is broken.
If something does not work for you and is not listed above, you can also report it through the contact page.
Last reviewed
We review this statement whenever the design system changes materially.