Explore the app Accessibility
PayGap aims to build accessible web and mobile experiences and to provide information in alternative formats where reasonably possible.
We want people to understand and use PayGap with confidence, including people with disabilities, language barriers, limited digital experience or circumstances that make financial tasks harder. We will work towards WCAG 2.2 Level AA for the website and appropriate accessibility standards for the app. The current product has not undergone a complete accessibility assessment. We therefore do not claim full conformance. Our target follows W3C's WCAG 2.2 standard.
Our proposed approach includes clear language, readable contrast, keyboard access, meaningful labels, understandable errors and alternatives to unnecessary motion. Important payment information should remain available without depending on an animation, colour alone or audio alone. Tell us if you need a different document format, help understanding a step or a suitable communication arrangement. We will discuss what we can provide and explain any limitation. We will not ask you to disclose a medical diagnosis just to describe an accessibility barrier.
Use the Contact form with the page or app screen, what you were trying to do and the difficulty you encountered. Device or assistive-technology details can help, but are optional. Tell us your preferred way to receive a response. We will acknowledge the report, assess the issue and explain the available workaround or intended next step.
A verification or payment step may be operated by a partner. We will help route accessibility concerns to that provider and remain responsible for issues within our own service. We will not describe a third-party screen as accessible without checking it. A trusted representative may assist through an authorised process. We will verify their authority without asking you to share passwords or one-time codes. If you are unhappy with the support provided, you may use the Complaints Policy.
The website includes a Pause motion control and respects reduced-motion preferences. Payment explanations and policy text remain available without relying on the animated illustration. Contact and complaint fields have visible labels, required-field indicators and length limits. These features do not establish complete WCAG conformance. If an interaction, error message, reading order or partner step prevents access, describe the barrier through Contact. An alternative way to complete a task may need coordination with the provider responsible for that step.
Design target: WCAG 2.2.
PayGap · Technology that connects