Built to be read by everyone.

01 Our commitment

We want everyone — including people who use assistive technology — to be able to read our content, use our tools, and reach us. Accessibility is designed and built into this site from the start, not bolted on afterwards, because the people we exist to serve include those who navigate the web by keyboard, screen reader, magnification, captions, or reduced motion.

We treat accessibility the same way we treat the rest of our work: as an ongoing standard to be held, measured, and improved — not a box to be ticked once.

02 The standard we work to

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA — the level the W3C recommends for entire sites, and the benchmark that accessibility law points to across the markets we operate in. WCAG 2.2 AA meets or exceeds the current European harmonised standard (EN 301 549, which today maps to WCAG 2.1 AA), and where a newer or stricter standard is reasonable to meet, we aim higher.

03 How this maps to the law where you are

We operate in India, Europe, the United Kingdom, the United States, and across Asia. Rather than keep a different bar in each place, we hold one standard — WCAG 2.2 AA — that satisfies the relevant law in all of them:

European Union

The European Accessibility Act (in effect since 28 June 2025) and the harmonised standard EN 301 549, which is built on WCAG.

United Kingdom

The Equality Act 2010 duty to make reasonable adjustments, for which WCAG AA is the accepted benchmark.

United States

The Americans with Disabilities Act (ADA) and, for federal-facing contexts, Section 508 — both of which courts and agencies measure against WCAG.

India & wider Asia

The Rights of Persons with Disabilities Act, 2016 and its accessibility guidelines, and equivalent local requirements elsewhere in Asia.

04 Where we stand today

We consider this site to substantially meet Level AA across its core pages and journeys, while recognising that a site of this size will have individual pages or components that still fall short in places. When we find a gap — or you report one — we prioritise it and fix it. This statement reflects our current, honest assessment rather than a finished certification.

05 What we have built in

• Semantic HTML structure with a correct heading order and clear landmark regions (banner, navigation, main, and content-info).
• A visible “skip to main content” link and a consistent, high-visibility keyboard focus ring on every interactive element.
• Full keyboard operability for the navigation, menus, forms, and interactive components — no action requires a mouse.
• Accessible names on every form field, control, and icon-only button, so assistive technology announces each one correctly.
• prefers-reduced-motion support — animation and auto-scrolling are neutralised for people who ask their system for reduced motion.
• Text and interface colour contrast checked against the AA threshold, and layouts that reflow and remain usable when zoomed or viewed on small screens.
• Descriptive alternative text on meaningful images, with decorative graphics hidden from assistive technology so they add no noise.

06 How we test and measure

We take a continuous approach rather than a one-time audit. Our checks combine:

• Automated tooling and browser accessibility extensions run against pages as we build and change them.
• Manual keyboard-only and screen-reader testing of key pages and journeys.
• Design-time review of colour contrast, heading hierarchy, and focus order before new pages ship.
• Fixes prioritised from what our tooling, our testing, and — most importantly — your reports surface.

We are actively expanding automated and manual screen-reader coverage across the full site, and reviewing every data visualisation for a clear non-visual equivalent.

07 Third-party content

Some parts of this site rely on third-party services — for example embedded video, maps, forms, or content hosted elsewhere. We choose accessible providers wherever we can and hold them to the same standard, but we do not control the code they serve and cannot guarantee it meets WCAG 2.2 AA. If a third-party element blocks you, tell us using the details below and we will find you another way to get what you need.

08 How to ask for help

If you encounter a barrier, need content in an alternative format, or want to report an issue, we will help — and we treat every report as a priority. Please tell us the page, what you were trying to do, and the assistive technology or browser you were using, so we can reproduce and fix it quickly.