Accessibility Statement

Last updated: 30 July 2026

This is a self-assessment, not an audit. It was written by Bhapi’s own engineering team from the product’s source code and automated tests. No independent accessibility auditor has reviewed the product or this statement, and no certification is claimed. An independent third-party audit is planned and has not yet taken place.

1. Our commitment

Bhapi is used by guardians, teachers and school administrators to keep children safe. That job should not require a particular way of seeing, hearing, moving or reading. We work to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, and we would rather tell you exactly where we fall short than publish a claim we cannot evidence.

2. Conformance status

The Bhapi web portal is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means some parts of the product do not fully meet the standard.

Of the 50 Level A and Level AA success criteria, our own assessment on 30 July 2026 recorded:

Measured WCAG 2.1 A/AA conformance, Bhapi web portal, 30 July 2026
Result	Criteria	What it means
Supports	15	No known defect against that criterion.
Partially supports	15	Some part of the product does not meet it.
Does not support	4	The product fails that criterion today.
Not applicable	6	The criterion does not apply (for example, we publish no audio or video).
Not evaluated	10	Not measured. Treat as unknown, not as conforming.

The full Accessibility Conformance Report (VPAT® 2.5, WCAG edition), with a row and an evidence basis for every criterion, is published at /legal/accessibility-report. Procurement teams should read that document rather than relying on this summary.

3. What we know does not work yet

These are the failures we have measured. We are not waiting to be asked about them.

Colour contrast. Our primary action colour puts white text at a 3.55:1 contrast ratio, below the 4.5:1 minimum. This affects the main button on most screens.
Focus indicators. On some pages the keyboard focus ring is a low-opacity colour measuring about 1.37:1 against white — effectively invisible.
Charts. The activity, spend and risk charts have no text alternative and distinguish their data series by colour alone, so their content is unavailable if you cannot see them.
Data tables. Most tables do not declare their header relationships and none carry a caption, so screen-reader navigation of them is poor.
Page titles. Most pages share one generic browser-tab title instead of describing themselves.
Mixed languages. Some English text appears inside pages served in Portuguese or Spanish without being marked up as English, so a screen reader mispronounces it.
Reaching every page. Some pages are not linked from the navigation and can currently only be reached by typing the address.

4. What we have not tested

Ten of the fifty success criteria were not measured at all. We have not performed a manual keyboard walkthrough, screen-reader testing, browser-zoom or 320-pixel reflow testing, or any testing with disabled users. Where this statement and the full report say “not evaluated”, that means unknown — it does not mean the product works.

5. What this statement covers

This statement covers the Bhapi web portal at bhapi.ai.

It does not cover, and we make no accessibility claim about:

the Bhapi mobile applications for iOS and Android;
the Bhapi browser extension;
the payment step, which is hosted by Stripe and governed by Stripe’s own accessibility documentation;
documents we generate for download, such as PDF and CSV report exports;
email and SMS notifications.

6. How we assessed the product

Assessment date: 30 July 2026. Methods used:

automated axe-core scans against the WCAG 2.0/2.1 A and AA rule sets, covering seven component and page test suites out of 76 pages;
inspection of the portal’s source code;
arithmetic calculation of contrast ratios from our design-system colour values.

Automated tools detect only a minority of accessibility barriers, and the scans run in a headless environment that cannot evaluate colour or layout. That is why so many criteria are recorded as not evaluated.

7. Tell us where we are failing you

If any part of Bhapi is not usable for you, please write to contactus@bhapi.io. Tell us the page or feature, what you were trying to do, and the assistive technology or browser you use if you know it.

We aim to acknowledge accessibility reports within 10 business days. If we cannot fix something quickly, we will tell you what the workaround is and when we expect to fix it properly.

If you need information that is currently locked inside an inaccessible part of the product — a chart, a table, an exported report — ask us and we will supply it in another format.

8. Status of this statement

Prepared by: Bhapi engineering, 30 July 2026.
Not independently audited. No third party has reviewed the product or this statement.
Not reviewed by legal counsel for the purposes of any specific procurement regime.
Review cycle: this statement is re-measured and re-dated whenever a listed gap is closed, and reviewed at least annually.

Related documents: Accessibility Conformance Report · Privacy Policy · Terms of Service