Important context
Accessibility needs and technology combinations vary. This page describes the design approach; it is not a certification that every page or third-party journey is free of barriers.
Our approach
Clear structure
Pages use headings, landmarks, labels, status messages, and consistent navigation so content can be understood without relying only on visual position.
Keyboard access
Core controls are intended to be reachable by keyboard, with a visible focus state and a skip link where a repeated application shell is present.
Responsive presentation
Layouts are designed to reflow on smaller screens and at browser zoom without requiring precise pointer movement.
Motion and contrast
The interface uses strong text contrast and respects reduced-motion preferences in supported experiences.
Using the portal with assistive technology
Screen readers
Use a current browser and screen reader combination. Form labels, navigation names, headings, tables, alerts, and transaction status regions are intended to provide useful context.
Zoom and text size
Browser zoom and operating-system text settings can help increase readability. On a narrow screen, some tables may be presented in a scrollable region.
Passkeys, QR codes, and documents
Alternative sign-in methods and printable or downloadable records depend partly on browser, device, identity-provider, and document-reader accessibility.
Known areas that may need extra support
Third-party journeys
Identity verification, external payment rails, browser passkey prompts, email clients, and linked services can have accessibility behavior outside the portal’s direct control.
Dense financial information
Statements, receipts, charts, and multi-step approval flows can contain detailed information. Contact support if a format or interaction prevents you from completing a task.
Fallback options
Where available for your account, support, USSD, or another approved channel may provide an alternative way to get information or complete an action.
Report an accessibility barrier
What to include
Tell us the page or task, what happened, the browser and device used, and any assistive technology involved. Do not include a password, PIN, one-time code, or passkey credential.
How to contact us
Email support@fedha.africa or use the support channel supplied for your account. Ask for a response in a format that works for you.
Ongoing review
Accessibility feedback is used to prioritize improvements to customer journeys and shared interface components.