Accessibility Statement

Last updated: 20 October 2026 · app version 1.0.0

1. Commitment to accessibility

Foryou Srl is committed to making the Flovvy app accessible in accordance with Directive (EU) 2019/882 (European Accessibility Act), applicable since 28 June 2025, and with the harmonised standard EN 301 549 v3.2.1, which adopts WCAG 2.1 level AA for software.

This statement applies to:

• the Flovvy mobile app for iOS and Android, version 1.0.0;
• the flovvy.app website.

The service. Flovvy records personal and shared expenses: from a photo of a receipt it builds the expense with AI (products, prices and category), and it keeps accounts, budgets, shopping lists and costs split with other people. How it works is explained on the home page of this site and, inside the app, step by step in Menu → Flovvy tours.

2. Conformance status

Partially conformant with EN 301 549 v3.2.1 (WCAG 2.1 AA). Known limitations and excluded content are listed in section 4.

“Partially conformant” is the wording the standard prescribes as long as even a single criterion has not been verified directly on a device. Claiming full conformance without having measured it would be the most serious mistake possible in a document like this one.

3. What has been done

Accessibility was verified through static analysis of the source code, computed contrast ratios across every colour combination in both themes and all selectable accent colours, and hands-on testing with TalkBack on Android and VoiceOver on iOS.

Criteria addressed, in WCAG order:

• 1.1.1 Non-text content — decorative graphics are declared as such on both platforms; charts have a text alternative carrying the same figures (total, individual items and amounts).
• 1.3.1 / 1.3.2 Info, relationships and meaningful sequence — visible labels are programmatically linked to their fields; detail tables are read one row at a time, with each value attached to the row it belongs to.
• 1.3.4 Orientation — the app works in portrait and landscape.
• 1.3.5 Identify input purpose — fields collecting personal data declare their purpose to the operating system.
• 1.4.3 / 1.4.11 Contrast — text at least 4.5:1, graphical and user-interface components at least 3:1, in both light and dark themes.
• 1.4.4 / 1.4.10 Resize text and reflow — the app follows the system text size up to 200% (large titles and amounts grow proportionally less, as Android itself does) and screens reflow up to 200%.
• 2.4.3 Focus order — when a dialog, a sheet or a full-screen page closes, focus returns to the control that opened it, with the Android exception listed in section 4.
• 2.5.3 Label in name — the announced name contains the visible text.
• 3.3.1 / 3.3.2 / 3.3.3 Errors and labels — fields declare their label, whether they are required and the expected format; when a value is rejected the error becomes part of the field name, so it is heard on reaching the field.
• 4.1.2 Name, role, value — no control without a name; controls contained in a row are exposed as actions of that row.
• 4.1.3 Status messages — outcomes that appear without moving focus (saved, deleted, added) are announced to the screen reader without stealing focus.

No tracking of assistive technologies

Foryou Srl does not use tracking techniques, its own or third parties’, from which a user’s disability could be inferred. The app does not record or send to anyone whether a screen reader, larger text or other accessibility settings are in use: where it reads them, it is only to adapt the interface on the phone. The website’s statistics (Google Analytics 4, loaded only after consent in the cookie banner) do not detect them and are not used for this purpose.

4. Non-accessible content

Known limitations

• Language of the interface on Android. Flovvy lets you choose its language independently of the phone (11 languages). On iOS the chosen language is passed to VoiceOver; on Android the app framework (React Native) offers no way to do the same, so TalkBack keeps reading with the voice set in the system. If you choose in the app a language different from the phone's, words may be pronounced with the wrong voice, spelled letter by letter or skipped (for example Cyrillic or Greek read by an Italian voice). Workaround: set the phone to the same language you choose in the app.
• Focus after closing some sheets on Android. When some sheets and dialogs close, TalkBack resumes reading from the title of the screen instead of the control that opened them. Nothing becomes unreachable: swipe forward to get back to where you were. On iOS, VoiceOver returns to the control.

Known refinements

• In a few fields the announced name is a filling example (“e.g. Debit card”) rather than the field name. Criterion 3.3.2 requires “labels or instructions” and an example is an instruction, so this is not a non-conformance; it remains a planned refinement.

Out of scope

• The system camera and photo picker used to capture or choose a receipt image, the Sign in with Apple / Google sheets and the App Store / Google Play purchase sheets are provided by the operating system or by the store; their accessibility is Apple's and Google's responsibility.
• Third-party content reached through external links.

5. Feedback and contact

If you encounter a barrier using Flovvy, report it to support@flovvy.app, stating the screen, the assistive technology you were using and what happened.

Foryou Srl replies within 20 working days.

Enforcement procedure

If the reply is unsatisfactory, or does not arrive within the stated deadline, you may contact the competent supervisory authority: AgID — Agenzia per l'Italia Digitale, designated as the supervisory authority for services within the scope of the European Accessibility Act by Article 21 of Italian Legislative Decree 82/2022.

• Reporting platform: segnalazioni.agid.gov.it
• Certified email: protocollo@pec.agid.gov.it
• Website: accessibilita.agid.gov.it

6. Preparation of this statement

• Prepared on 4 August 2026; last reviewed on 20 October 2026.
• Method: self-assessment by the provider, using static analysis of the source code, computed contrast ratios, Google Accessibility Scanner reports, hands-on testing with TalkBack and VoiceOver and, for the website, automated checks (axe-core) with keyboard, zoom and reflow tests.
• The statement is reviewed at every release that changes the user interface.