Legal · Accessibility
Accessibility statement
For anyone using this site with assistive technology, a keyboard or a slow connection: we commit to WCAG 2.2 Level AA, and say here what is in place and what is not.
Our commitment
The standard is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, applied to this marketing site and carried as a build rule into the application it leads to. Several of the criteria that changed in this version of the guidelines are the ones that matter most for a business owner completing a long process on a phone, and they are treated as rules about how the site is built rather than as things to check afterwards.
What is in place
Each of these was checked in the site’s code before it was written here.
- Skip link (2.4.1 Bypass Blocks)
- The first focusable control on every page is a "Skip to content" link that jumps past the header to the main content. It is visible when it has keyboard focus.
- Landmarks and language (1.3.1, 3.1.1)
- Every page declares its language, has one main landmark, one level-one heading, and navigation regions that announce their purpose. The header and footer are single shared components, so this holds on every route rather than on the ones somebody remembered.
- Target size (2.5.8 Target Size, Minimum)
- The minimum size for an interactive target is a single design value, applied as a floor to the header controls, rather than a per-component review question.
- Consistent help (3.2.6)
- The support affordance (Talk to a person) sits in the same relative position in the header on every page, and in the same column of the footer.
- Accessible authentication (3.3.8)
- No image CAPTCHA anywhere, and password fields accept paste. There is no sign-in on this site today; the rule binds the authenticated application this site leads to, and a field that blocks paste breaks password managers and punishes exactly the people being careful.
- Redundant entry (3.3.7)
- Nothing already given in a process is asked for again in the same process. This is a rule on how forms are built here, and is the difference between finishing and abandoning a long onboarding on a phone.
- No motion, no autoplay, no carousels (2.2.2, 2.3.3)
- There is no animation, autoplaying media or carousel on this site. Pages are text, links and tables, which is also why they load on a slow connection.
- One palette, with a dark theme (1.4.3, 1.4.11)
- Every color on the site comes from one small set of named semantic colors, and the site follows your system’s light or dark preference. Because there is one palette, a contrast fix is made once and applies everywhere.
- Keyboard-scrollable data tables (2.1.1)
- Where a table scrolls sideways on a narrow screen, the scrolling region is reachable and operable from the keyboard and is announced as a named region, on the impact methodology page today, and on the others as they are updated.
Known limitations, stated honestly
A statement that only lists intentions is not one. These are the gaps we know about.
- No full audit has been carried out
- No independent WCAG 2.2 AA audit exists, and no testing with screen readers, switch access or magnification has been recorded. The items above hold by construction or by inspection of the code; they have not been confirmed with assistive technology. We are stating a commitment and the work behind it, not claiming conformance.
- Focus indication is the browser default
- We have not designed a custom focus style, and we have not verified that the default indicator meets the contrast requirement on every background the site uses.
- Some tables are not yet keyboard-scrollable
- On narrow screens, comparison tables on other pages scroll sideways in a region a keyboard user cannot yet focus. The pattern that fixes it is in place on one page and is being applied to the rest.
- English only
- The site is written in English. Support by WhatsApp is in English or Kiswahili, but the pages themselves are not yet available in Kiswahili.
- Interactive tools not yet reviewed by hand
- The readiness check and the two calculators pass automated accessibility checks, but have not had a manual review with assistive technology. If one falls short of this statement for you, report it below.
- Contrast has not been measured everywhere
- Neither the light nor the dark palette has had a full contrast measurement across every surface. The dark theme follows your system preference and is the less inspected of the two.
Preparation of this statement
Prepared by Mtaji Technologies from inspection of the site’s own code and build checks, not from an external assessment. It is revised when a limitation above is closed or a new one is found, and the limitations list is the part most worth re-reading.
How to report a barrier
If something on this site stopped you, tell us through support: WhatsApp for suppliers and distributors, e-mail or in-app for institutions. Describe what you were trying to do and what happened, rather than the technical cause; finding the cause is our job. Say which assistive technology or browser you were using if you know it.
We would rather hear about a barrier than not, and we will tell you what we are doing about it. A barrier that stops you completing something you need to do is treated with the same priority as a payment problem.