Our commitment
Mpesa Calculator is built to be usable by everyone, including people who rely on screen
readers, keyboard navigation, screen magnifiers, high-contrast settings, captions, and voice
input. We design with accessibility in mind from the start, and we continually review
changes against WCAG 2.1 AA.
We operate from Kenya and align with the Kenyan Data Protection Act (DPA) and guidance from
the Office of the Data Protection Commissioner (ODPC). Accessibility is part of our product
quality standards, not an afterthought.
Standards & guidelines
- WCAG 2.1 Level AA as our target success criteria.
- Semantic HTML with ARIA only where needed to enhance semantics.
- Color contrast that meets or exceeds AA for text and controls.
- Keyboard operability for all interactive elements, including menus, drawers, banners,
accordions, and forms.
- Clear focus indicators and logical tab order.
- Reduced motion respect: we honor
prefers-reduced-motion where possible.
Built-in accessibility features
- Skip link to bypass navigation and jump to main content.
- Landmarks for header, navigation, main, aside (TOC), and footer.
- Keyboard navigation for menus, mobile drawer, accordions, and cookie
banner actions.
- Visible focus states on links, buttons, form fields, and toggles.
- ARIA labeling on toggles, status messages, toasts, accordions, and form
errors.
- Form guidance with clear labels, required markers, inline errors, and
helper text.
- Responsive layout that preserves readability and tap targets on mobile.
- Status announcements for operational banner and form states via
aria-live.
- Color contrast tuned to meet AA for text and interactive elements.
Compatibility & testing
We test key flows (navigation, calculators, forms, FAQs, drawers) with:
- Keyboard-only navigation (Tab/Shift+Tab/Enter/Space/Esc).
- Screen readers (NVDA, VoiceOver) on modern browsers.
- Desktop: Chrome, Edge, Firefox, Safari (latest).
- Mobile: Chrome/Android, Safari/iOS.
- High-contrast modes and zoom up to 200% without loss of functionality.
If you encounter an issue with a specific assistive technology, please tell us the device,
browser, tool, and page so we can reproduce and fix it quickly.
Known limitations
- Historical screenshots or legacy PDFs may not have text alternatives; we can provide
accessible formats on request.
- Third-party embeds (e.g., analytics consent scripts) may have their own accessibility
constraints; we monitor and adjust when feasible.
- Occasional update notices may not auto-focus; use the skip link or refresh if you miss a
message.
We track and remediate issues in our release backlog with priority.
Request support or alternative format
If you need calculator results or documentation in an alternative format (e.g., large print,
plain text, audio description), contact us and include the specific page or calculator.
We respond within one business day and will provide an estimated timeline if a custom format
is needed.
Report an accessibility issue
Tell us what happened and where:
- Page URL, device, browser, assistive tech (if any).
- Steps to reproduce and the expected outcome.
- Screenshots or screen reader logs, if available.
Report via Contact page or email
mynetpaykenya@gmail.com. Critical issues are
prioritized
for same-day triage.
Ongoing improvements
- Continuous WCAG 2.1 AA review during feature releases.
- Broader screen reader coverage and automated linting for aria attributes.
- More robust prefers-reduced-motion handling across interactive charts and banners.
- Extended contrast checks for newly added calculator states and badges.
We publish updates on this page when accessibility changes ship.
Contact & escalation
For accessibility requests or complaints, contact us at
mynetpaykenya@gmail.com or use the
Contact page. If you are unsatisfied with our response and
are based in Kenya, you may escalate to the Office of the Data Protection Commissioner
(ODPC).