Accessibility statement

Our commitment

Hospital staff use software all day, often quickly, often on whatever device is to hand. A site describing that software should be usable by everyone who needs to evaluate it — including people using a keyboard only, a screen reader, magnification, speech input, or a phone in a corridor.

PureBrix is committed to making this website accessible, and to fixing what we are told is not.

Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for making web content more accessible. This website aims to conform to WCAG 2.1 level AA.

Status: partially conformant. Partially conformant means most of the content meets the standard, but some parts do not, or have not yet been confirmed by testing with people who use assistive technology. What we know falls short is listed in section 6.

We describe it this way deliberately. Automated testing reports no failures, but automated testing catches roughly half of what matters, and we have not yet done the other half. Claiming full conformance on that basis would not be honest.

What we have done

The pages are built to the standard rather than retro-fitted to it:

• Keyboard. Every link, button, menu and form field can be reached and operated by keyboard, in a sensible order, with a clearly visible focus outline. A skip link is the first thing you reach on every page.
• Structure. Real landmarks, one main heading per page, and headings in order, so a screen reader can navigate by structure rather than by reading everything.
• Contrast. Text meets the 4.5:1 minimum. Text placed over a gradient was measured by hand at the gradient’s brightest point, because automated tools cannot measure it.
• Colour. No information is conveyed by colour alone.
• Forms. Every field has a visible label. Errors appear in the page next to the field, in words, are linked to the field so a screen reader announces them together, and focus moves to the first field that needs attention.
• Target size. Every link and button is at least 24 pixels tall.
• Motion. Sections fade in as you scroll, and pages transition when you navigate. If your device is set to reduce motion, both are switched off.
• Without JavaScript. Every page reads normally. The navigation becomes a list of links and the questions still open.
• Zoom and small screens. The pages reflow to 320 pixels wide and to 200% zoom without content being cut off or needing sideways scrolling.
• Images. Decorative graphics are hidden from assistive technology rather than announced as meaningless images.

Technical specifications

Accessibility of this site relies on the following technologies working with your browser and any assistive technology you use:

• HTML
• CSS
• JavaScript — used only as an enhancement; every page works without it
• WAI-ARIA, used sparingly and only where native HTML does not carry the meaning

The site is built with no framework and no build step, which keeps the markup close to what a browser and a screen reader actually receive.

How it was assessed

Assessed by PureBrix, self-evaluating, using:

• automated testing with axe-core against the WCAG 2.1 A and AA rules, on every page, at 1440 pixels and 390 pixels wide;
• manual keyboard walkthroughs of the navigation, the questions and the demo form;
• by-hand contrast calculation where a gradient background made automated measurement unreliable;
• checks with JavaScript disabled, and with reduced-motion preferences set.

That testing was last run in full on 17 October 2026 and reports no failures. We re-run it before each release of the site.

This is a self-evaluation. No independent accessibility audit has been commissioned, and we do not claim conformance has been certified by anyone outside PureBrix. We say so plainly because a self-assessment and an audited one are not the same thing, and you are entitled to know which this is.

Known limitations

Being straight about the gaps is more useful than claiming there are none. We know about the following, and are working on them:

• Not yet tested with assistive technology users. Automated checks and our own keyboard testing are not a substitute for someone who uses a screen reader every day. This is the most significant gap.
• The illustrative product screens are not explorable. They are presented as images of an interface and hidden from assistive technology. The point each one makes is also written in the text beside it, so no information is lost — but the screen itself cannot be examined.
• Typefaces load from a third party. If that request is blocked or slow, pages fall back to your system font. Readable, but not what we designed.
• No formal compatibility matrix. We have not systematically tested against specific screen reader and browser combinations, so we cannot list which are known to work.

These pages describe this website. The accessibility of the SanoBrix application itself is a separate question — a dense clinical interface raises issues a marketing site does not — and we will answer it honestly if you ask. As it stands, SanoBrix has not been formally assessed against WCAG, and nothing on this page should be read as a statement about it. We are not going to publish a conformance claim for the application before we have done the work to support one. If accessibility of the application matters to your procurement, raise it with us early and we will tell you exactly where we are rather than what you would like to hear.

Tell us where it fails

If you hit something on this site you cannot use, we want to know. Tell us the page, what you were trying to do, and what you were using — browser, screen reader, anything relevant.

By email

supports@purebrix.com

By post

PureBrix Solutions Pvt Ltd, Innov8, Upper Ground Floor, Graphix Tower 2, A-13, Sector 62, Noida, Uttar Pradesh 201301, India

Or

Through the contact page.

We aim to respond within five working days and will tell you what we can fix and when. If you need information from this site in another format — large print, plain text, or read aloud — ask and we will provide it at no charge.

If we do not put it right

If you are not satisfied with our response, you can escalate.

PureBrix operates in India, where the Rights of Persons with Disabilities Act 2016 applies. Section 46 of that Act, with Rule 15 of the Rights of Persons with Disabilities Rules 2017, requires establishments to provide information and communication technology that is accessible to persons with disabilities, and the Chief Commissioner has applied this to private companies as well as to government bodies.

You can take a complaint to the Office of the Chief Commissioner for Persons with Disabilities, Department of Empowerment of Persons with Disabilities, Ministry of Social Justice and Empowerment, Government of India. Under Rule 38 of those Rules a petition may be made in person, through a representative, by registered post or by email. Details of how to file are published at ccpd.nic.in. If you are in a State that has appointed a State Commissioner for Persons with Disabilities, you may go there instead. You are not required to come to us first.