Accessibility statement

Ferrario is built for people organising their financial paperwork — first students, often on a phone, often in a second language, and later people doing it with reading glasses. Accessibility here is not compliance decoration: it is the difference between the product working for that person and not.

What we claim

The signed-in app aims to conform to WCAG 2.2 level AA, the standard referenced by EN 301 549 and by the European Accessibility Act. Based on the testing described below, we consider it substantially conformant, with the known exceptions listed at the end.

This claim is self-assessed. It has not yet been audited by an independent third party or verified by users of assistive technology outside the team, and both are recorded as open items rather than implied.

What has been done

• Every screen was re-audited in September 2026 — layout, type, colour, motion, touch and keyboard — screen by screen, in light and dark, at phone, tablet and desktop sizes.
• Automated checks in the test suite. The signed-in screens and the policy pages are checked with axe in a real browser, at desktop and phone sizes and at both text sizes, and a violation fails the build. This catches contrast, labelling, roles and heading-order problems.
• Larger text is a real setting, not browser zoom — and it is the default. It scales the whole type system, so nothing runs off the side of the screen, and it follows your account to every device.
• Two languages. The app speaks English and Dutch, chosen with the language switch or in settings.
• Light and dark, both designed rather than inverted, with contrast measured for every colour in every one of the thirteen assistant colour schemes, in both themes.
• Keyboard operation throughout: no mouse-only interaction, visible focus, a skip link, and menus built from native elements that work before JavaScript loads.
• Touch — controls meet a minimum touch size, and on tablets and landscape phones the navigation compacts rather than crowding the content.
• Reduced motion — honoured from your device's setting, and also a choice in Settings → How Ferrario looks. With it on, animations end in their final state instead of playing.
• Charts are not colour alone. Every series is labelled, gaps in the evidence are drawn as gaps, document markers are keyboard-reachable links, and every chart has the same figures as a table for screen readers and for pages without JavaScript.
• Plain language. Sentences are written to be understood on the first read, which is an accessibility property and not only a style preference.

Known exceptions

Written down rather than glossed:

• No independent audit. Planned before public launch.
• No formal screen-reader test report. The core flows have been walked with a screen reader; a documented pass over every screen has not been done. Planned with the closed student test.
• The landing page and the onboarding journey are a separately built, highly animated experience. They honour reduced motion, but they are not yet covered by the automated axe checks and have not had the screen-by-screen audit the app has had.
• Some text written by the server is English even in Dutch mode — the dashboard's Pulse line, some forecast sub-lines and some metric notes. The policies themselves are English on purpose: they are the text that was agreed to.
• The document preview is the browser's own PDF viewer. Its accessibility is the browser's and the document's, not ours, and a scanned PDF with no text layer is unreadable to a screen reader whatever we do. Ferrario shows the extracted figure and the exact sentence it came from as real text beside the document, so the evidence is readable even when the file is not.
• A few wide tables scroll sideways inside their own box on a small phone. They are readable, but the pattern is not ideal and is on the list.

Feedback

If something is unusable, tell us — including what you were using at the time. Use Get help in the app, or write to the address on the privacy policy. We treat an accessibility report as a bug, with the same priority as a wrong figure.

If we cannot resolve it, you can complain to the enforcement body for the European Accessibility Act in your country.