Accessibility Statement

Accessibility matters because this site is meant to be practical in real usage moments. People often visit when they need a fee quickly, want to compare payment options, or are checking a limit before making a transaction. That means the experience should stay usable across different devices, assistive needs, and browsing habits.

The goal is steady improvement, not a one-time checkbox. If a page is hard to read, difficult to navigate, or confusing to operate with assistive tools, that is treated as a real product issue.

Keyboard Support

Core navigation, content links, and calculators are intended to work with keyboard navigation. Buttons, links, forms, and expandable FAQ sections should be reachable without depending on a mouse or touch interaction.

Where a calculator accepts amount input, the goal is to keep fields clearly labeled, allow standard keyboard submission behavior, and avoid trapping focus inside UI elements.

Readable Content

The content strategy on this site favors direct wording, clear headings, and practical tables so people can scan a page quickly. This is especially important on finance-related guides where ambiguous wording can create avoidable mistakes.

• headings should describe the section clearly;
• tables should show fee bands and limits in a straightforward way;
• calculator labels should explain what the user is entering and what the result means;
• important warnings should be visible in normal reading flow, not hidden in fine print.

Responsive Use on Phones and Tablets

Because most M-PESA usage in Kenya happens on mobile devices, pages should remain readable and tappable on smaller screens. The site is designed so the main content, calculator controls, and support links remain accessible on phones and tablets without requiring desktop-only interaction patterns.

Assistive Technology Goals

The site aims to support semantic headings, labeled form fields, visible focus behavior, and content ordering that makes sense to screen readers and other assistive technologies. Decorative elements should not carry the meaning of a section on their own.

Known Limitations

Accessibility work is ongoing. Some pages may still need refinement in areas such as table density on smaller screens, calculator helper messaging, or interaction clarity in more advanced tools. When issues are found, the preferred approach is to fix the source problem rather than add vague workarounds.

How to Report an Accessibility Issue

If you run into an accessibility problem, the most helpful next step is to use the contact page and include the page name, your device, browser, and a short description of what went wrong. If keyboard navigation failed, a button was hard to reach, or a result message was unclear, that detail helps a lot.

Frequently Asked Questions

Can I use Mpesa Calculator with a keyboard only?

That is the goal. Core navigation, calculators, links, and FAQ sections should be usable with keyboard navigation without depending on a mouse or touch input.

What should I do if I find an accessibility problem?

Use the contact page and describe the page, device, browser, and issue clearly so the problem can be reproduced and fixed.

Does the site process accessibility feedback?

Yes. Accessibility feedback is useful because it helps improve keyboard flow, readability, calculator interaction, and general page clarity across the site.