Back to home

Accessibility Statement

Last updated: August 18, 2026

Prosperiu is a tool someone opens to see their own money, so it has to be open to everyone. This statement describes what has actually been done to make the system accessible, and just as plainly what has not. There is no claim of full conformance here, because no such audit has been carried out.

1.Standard and current state

This statement covers the site and the application at prosperiu.com, in Hebrew and in English, both the public pages and the screens behind sign in, the chat with Sapir, the assistant in the app, included, and also when Sapir is installed on a phone as a separate app. The same commitment covers them all.

We aim at the international WCAG 2.1 Level AA standard. The Israeli standard SI 5568 is Israel's adoption of the WCAG guidelines at level AA, and its requirements fall inside what we aim at.

And so the picture is accurate, here is where things actually stand:

  • Conformance is partial. Some requirements are met, others are not.
  • No external accessibility auditor has reviewed this product, and no thorough screen reader testing has been carried out.
  • No accreditation, certificate or approval has been issued for this service by anyone, and we do not claim full conformance.
  • The product is in a testing period and changes often. Accessibility is handled as part of that, not as a one off project that finished.

3.What else was done

  • Hebrew and English with full directionality: the interface is built right to left and flips to the correct direction when the language changes, menus and dialogs included.
  • Light and dark modes on a defined colour palette, plus a brightness control for anyone the screen glares at.
  • Visible focus: interface elements take a clear focus ring when navigating by keyboard.
  • Labels for screen readers: every button marked only by an icon, the edit, delete and row menu buttons on the transactions, goals, alerts and budgets screens included, carries a text label that also names what it acts on. Dialogs carry a role and a name.
  • Semantic structure: headings, lists, navigation and main content are marked up as such, rather than as styled text.
  • Reduced motion: the attention animations honour the operating system preference for reduced motion, and the accessibility menu can stop motion altogether.
  • Browser zoom to 200% is supported, alongside the font control in the menu.
  • The browser's own font size survives: the system's base font size is derived from the browser preference rather than fixed to a number in the code, so anyone who changed the font size in their browser settings gets that change here too. The font control in the accessibility menu multiplies that preference instead of replacing it.
  • Every form field carries a visible label, and error messages are given in text rather than by colour alone. The programmatic link between a label and its field exists on some screens only, which section 5 sets out.

4.Keyboard navigation

The system can be operated without a mouse. The main keys:

  • Tab and Shift + Tab: move between elements forward and back.
  • Enter or Space: activate a button, a link or a switch.
  • Arrow keys: move between items in menus, tabs and select lists.
  • Esc: close a dialog, a menu, or the accessibility panel.

5.Known gaps

These are the gaps we know about. They are listed so you can plan around them, not as an excuse.

  • The accessibility menu is only available inside the application, after signing in. On the public pages, the home page, the signup and login screens and the legal documents, it is not shown. There, browser zoom, the browser's own font size setting and the operating system's accessibility settings still apply, and they do take effect on the page.
  • On most screens a form field's label is not programmatically tied to it. The label is visible, but a screen reader does not read it out on reaching the field, and announces the field without saying what goes in it. The fields that are tied are on the login, signup, settings, report preference and cashflow sharing screens. This is a Level A gap in the standard, and it is being worked on.
  • There is no skip to content link at the top of the page, so keyboard navigation passes through the navigation elements first.
  • Charts are not fully accessible. They are visual, and have no full text alternative or equivalent data table at present. The underlying figures are available on the transactions and accounts screens.
  • Screen reader behaviour has not been fully tested across every screen, particularly the more complex investment and research screens.
  • Reduced motion is not applied everywhere. It covers some animations, not every movement in the interface. A full stop is available in the accessibility menu.
  • Some components come from external libraries, and their accessibility depends partly on those libraries.

These are being worked on. If one of them actually blocks you, telling us moves it up the list.

6.An alternative route

If a screen or an action in the system is not accessible to you, there is no need to work around it alone. Write, call or message us, and we will hand over the information or carry out the action another way.

  • We will send the figures you asked for by email, in the message or as a file.
  • We will go through the screen together on a phone call.
  • We will carry out an action that will not work for you, on a request coming from the account's own email address.

The service is provided online only. The business has no branch, office or other place that receives the public, so there are no physical accessibility arrangements to describe. Every approach is made through the channels in the next section.

7.Reporting a problem

If you hit an accessibility barrier, or you have a suggestion, please write to us. The accessibility coordinator is Afik Ben Bocher.

We undertake to answer any accessibility message within 14 business days at the latest, and to say what was done about it.

To let us deal with it quickly, it helps to know:

  • which page or screen the problem appeared on;
  • what you tried to do and what actually happened;
  • which device and which browser;
  • and if you use assistive technology, which one.

If the answer you receive is not satisfactory, you also have the right to approach the Commission for Equal Rights of Persons with Disabilities at the Israeli Ministry of Justice.

8.Updating this statement

This statement was last updated on August 18, 2026. It is reviewed on every material change to the system, and revised when a gap closes or a new one comes to light.

The review behind this update is an internal one, by the person who built the system. No licensed accessibility consultant has examined it and no accessibility approval has been issued for the service, as section 1 sets out.