Accessibility Statement

Our commitment

FF Family is built to be usable by every adult, child, and family member regardless of disability or assistive technology. Accessibility is not a feature we add at the end, it shapes how we design and what we ship from day one.

Scope of this statement

This statement covers all Family web properties:

The marketing site at fffam.app.
The three apps at app.fffam.app/life, /biz, and /grows.

Standards we conform to

We aim to conform to:

Web Content Accessibility Guidelines (WCAG) 2.0, Level AA the international standard.
Israeli Standard 5568 (2013) the Israeli adoption of WCAG 2.0 AA, referenced by the Equal Rights for Persons with Disabilities Law, 1998 and the Accessibility of Service Regulations, 5773–2013.

Conformance status

Partially conforms to WCAG 2.0 Level AA. Most screens meet it; the gaps we know of are listed below. Our checks are described under "How we test". No full outside audit has been done yet.

What we do to maintain accessibility

A color palette chosen for WCAG 2.0 AA contrast: body text at 4.5:1, large text and icons at 3:1. A few light grey labels still fall short; we are fixing them.
Semantic HTML landmarks (<header>, <nav>, <main>, <footer>) for screen-reader navigation.
Programmatic labels on form fields: a <label> or an aria-label. Most fields were bound to their labels in September 2026; a few still rely on placeholder text (see below).
Right-to-left (RTL) layout throughout, with Hebrew as a first-class locale alongside English.
Resizable text, pinch-zoom is not blocked on mobile; layout adapts when browser zoom is increased.
No reliance on color alone, every place where color carries meaning, an accompanying sign, icon, or label is present too.
Motion follows your device: with "reduce motion" turned on, figures and charts appear without animating.
Automated checks before every release keep each accessibility fix in place (see "How we test").

Known limitations + remediation timeline

We're being transparent about what's still being improved. If you encounter an accessibility issue that isn't listed here, please tell us, your report directly shapes our remediation queue.

Modal dialogs since August 2026, keyboard focus stays inside an open dialog, ESC closes it and focus returns to where it was. If you meet a dialog that misses any of this, please tell us.
Color-only meaning audit income/expense entries use a +/− sign prefix alongside red/green coding; we are auditing every additional surface (charts, tooltips, badges) to confirm a non-color cue is always present. Target: before the public beta.
Mixed-direction text in Hebrew screen-reader output some surfaces have English brand names embedded in Hebrew sentences; screen readers may stumble on the language switch. Under review.
Some legacy form patterns a small number of older form components still rely on placeholder text instead of programmatic labels. Migration in progress.

How we test

Automated checks run before every release. They pin what our accessibility reviews fixed (form labels, text alternatives for charts, color contrast on key screens, zoom not blocked, reduced motion), so a later change cannot quietly undo it. They do not replace a full audit.
Manual keyboard-only walkthroughs and checks of what a screen reader reads. The latest full pass (September 2026) covered Life, Business and the Business Suite: keyboard only, the screen-reader tree, 320px width, 200% zoom and Hebrew.
Reports every accessibility report we receive is checked against the code, and once fixed it gets an automated check of its own.

Hebrew availability

This statement is available in English and Hebrew via the language toggle in the top navigation. Both versions are intended to be equivalent.

How to contact us about accessibility

If you encounter an accessibility barrier, please tell us. We will respond within 7 business days with an acknowledgement and a plan.

In your report, please include:

The page or feature where you encountered the issue (a URL helps).
What you were trying to do.
What happened instead.
Your assistive technology, if relevant (screen-reader name, magnifier, etc.).

Accessibility reports are treated as priority and go directly to our small core team.