Accessibility

Accessibility statement

We want everyone in a family to be able to use Kinfara — including people who use a screen reader, a keyboard instead of a mouse, screen magnification or larger text.

Our goal

We aim for kinfara.com to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the standard published by the World Wide Web Consortium (W3C).

Where we are today

We have not yet completed a full manual review or an independent audit, so we do not claim that kinfara.com fully meets WCAG 2.2 AA. Our most recent automated check, on October 31, 2026, covered every page of kinfara.com and found no WCAG 2.2 AA issues after the fixes we made that day.

That check covers, on every page: text alternatives for images and map illustrations, a label on every form field, the page language, readable text contrast, and a name on every link and button. We also check pages at phone width; a few wide diagrams, such as the encryption diagram on our privacy page, scroll sideways inside their own box.

How we check

We test every page of kinfara.com with the axe accessibility engine, at desktop and phone widths, and fix what it finds. Accessibility is a continuous process: automated tools find only part of the barriers a person can meet, so we also rely on what you tell us.

What this statement covers

This statement covers the kinfara.com website. Payments are made on Stripe’s own pages, and the sign-in security check is provided by Cloudflare; the accessibility of those parts is managed by those companies. If you need help with the Kinfara app on your phone, write to us as below.

Tell us about a barrier

If something on kinfara.com is hard to use, if you need information in another format, or to request an accommodation, email support@kinfara.com. Please tell us the page address and what happened. A person at Kinfara reads every message; we aim to answer within one business day.

Last updated: October 31, 2026.