Accessibility
Last updated: 27 July 2026
We want this site to work for as many people as possible, whatever technology or way of interacting they use. This statement explains the standard we build to, what we have done, where we know there is still work to do, and how to tell us about a problem.
Our commitment
Accessibility is part of how we design and build, not an afterthought. We treat clear structure, legible type and operable controls as core to the site’s quality, and we improve them as we find issues.
The standard we build to
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, and we align with the newer 2.2 criteria where practical. These guidelines are organised around content being perceivable, operable, understandable and robust.
Measures in place
- Semantic HTML structure with a logical heading order and clear page landmarks;
- A “skip to content” target and keyboard-operable navigation and menus;
- A visible focus indicator on links, buttons and form fields for keyboard users;
- Form fields with associated labels and clear instructions;
- Text alternatives for meaningful images, and decorative images marked so assistive technology can ignore them;
- Support for the operating-system “reduced motion” preference, which pauses or removes non-essential animation;
- Colour and contrast chosen for legibility, with information never conveyed by colour alone;
- A responsive layout that adapts to different screen sizes and zoom levels; and
- A print / save-as-PDF stylesheet so pages can be read cleanly on paper.
Known limitations
We are honest about where the experience is not yet perfect, and we are working on these areas:
- Some of the site’s interactive data visualisations and selectors (for example, the BRSR overview and persona and standards selectors) offer a richer experience with a pointer than with a keyboard or screen reader. Where that is the case, the underlying information is also available as on-page text.
- Third-party pages we link to (such as image-licence and source pages) are outside our control and may not meet the same standard.
Compatibility
The site is designed to work with current versions of the major browsers and to be usable with common assistive technologies. If you use an older browser or configuration, some features may behave differently.
Feedback — and how to reach us
If you encounter a barrier on this site, or need information from it in a different format, please tell us at contact@teravora.in. Let us know the page and what went wrong, and we will do our best to help and to put the issue right. We treat accessibility feedback as a priority and aim to respond promptly.
Enforcement
If you contact us about an accessibility problem and are not satisfied with our response, you can raise the matter with our Grievance Officer using the same address; details are in our Privacy Policy.