Accessibility of Kivra's payment function

This statement concerns the accessibility of our payment function, i.e. the function for paying invoices in Kivra, on the iOS, Android and Web platforms. Here we describe how the payment function meets the requirements of the Accessibility Act (The Act on the Accessibility of Certain Products and Services, LPTT), any accessibility issues and how you can report deficiencies to us.

Legal requirements for our payment function

The Accessibility Act (LPTT) requires that certain products and services aimed at consumers in several different areas must be accessible. One of these areas is banking and payment services. Since you can pay invoices in Kivra, the law applies to that part of Kivra's service.

Even if not all of Kivra's service is covered by the legal requirement, our goal is to work to ensure that all parts of Kivra are accessible. Read about how we work with accessibility in Kivra.

How accessible is the payment function?

The payment function is mainly compatible with the Accessibility Act (LPTT).

However, we are aware that some parts of the function are not fully accessible. None of the identified shortcomings are currently considered to be blocking any user.

Supervision

Those tasked with reviewing us and ensuring that we comply with the legal requirement are the supervisory authority Post and Telecom Agency (PTS). If you are not satisfied with how we handle your comments, you can contact PTS and report it.

Technical information about the payment function accessibility issues

Android

What we list below applies to version 3.40.1 of the app and later versions. If you are using an earlier version, more deficiencies may occur.

  • PDF documents are read out unstructured by screen readers The screen reader (TalkBack) reads out the entire PDF document as a single block. This means that users cannot navigate by heading, paragraph, links or landmarks. *(UP-758)

Web

  • PDF document lacks meaningful structure and image descriptions This makes navigation and understanding difficult for users using screen readers or keyboards.*(PMNT-3065)

  • Selected page in navigation menu not indicated to screen readers The current page is visually highlighted but not spoken by screen readers, which means that users with screen readers do not receive information about which page is selected. *(PMNT-3074)

  • Incorrect header structure in some views *(PMNT-3073, PMNT-1429)

  • Unnecessary repetition of reference numbers and bank giro numbers for screen readers *(PMNT-1428)

  • Unclear reading of reference numbers for screen readers *(PMNT-3174)

  • Menu button in the invoice list is not accessible for screen readers *(PMNT-3063)

  • Checkboxes and menu buttons lack unique labels All check boxes and menu buttons in the invoice list have the same label ( “Select content” and “Manage menu”), which makes it impossible for users with screen readers to know which invoice an action applies to. *(PMNT-3072)

For all platforms

  • In some views, screen readers read out bank account numbers in an unclear and inconsistent way. (*PMNT-3065)

*internal reference code

Action plan

Action plans for known deficiencies are delivered on an ongoing basis.

How we tested the payment function

We have performed a self-assessment (internal testing) and had certified accessibility specialists from Useit perform an independent review of the payment function.

The last major assessment was made on March 31, 2025.

The report was last updated on June 5 2025.

Help us improve accessibility

We are constantly striving to improve accessibility. If you experience problems that are not described on this page, or if you believe that we are not meeting legal requirements, we want to know. Your feedback helps us make Kivra even better for everyone.

Contact us