KeepahBack to Keepah
Accessibility

Accessibility statement.

We want Keepah to be usable by everyone, including people who use a screen reader, larger text, or reduced motion. This statement says honestly where we are, including the things we have not checked yet.

Last reviewed 8 August 2026.

The standard we work to

We target the Web Content Accessibility Guidelines, WCAG 2.2, at Level AA, for both the Keepah app and keepah.com.

What we have done

Labelled controls

The app labels interactive controls for assistive technology using the platform accessibility APIs, with more than 200 explicit labels and roles in place today.

Reduced motion

The app respects the system Reduce Motion setting in its loading placeholders and in the sign-in code animation.

Touch targets

Generous touch areas are applied to small controls throughout the app, so a control is easier to hit than it looks.

Site structure

keepah.com declares its language, uses a single top level heading with a correct heading order beneath it, and provides alternative text on every image.

What we have not yet done, stated plainly

As of 8 August 2026 Keepah has not completed a full WCAG 2.2 AA audit. Specifically:

  1. No screen reader walkthrough of the core app flows has been performed with VoiceOver or TalkBack.
  2. Colour contrast has not been measured against the 4.5:1 minimum on either the app or the website.
  3. Labelling is incomplete. Roughly one in six interactive controls carries an explicit label. Many others are named automatically by their visible text, but buttons that show only an icon are likely to be announced without a useful name. This is the gap we consider most serious.
  4. Text scaling has not been tested. The app has not been checked at large Dynamic Type settings, so some screens may truncate or overlap at those sizes.
  5. Keyboard only operation of keepah.com has not been tested, including the Keebot chat widget.
  6. Form labels and focus order have not been systematically audited on either surface.
  7. Contextual hints for controls that are not self explanatory are almost entirely absent.

We would rather publish that list than claim a level of accessibility we have not demonstrated.

What we are doing about it

  • Naming every icon-only button in the app.
  • Measuring the colour palette against the 4.5:1 minimum and fixing what fails.
  • Running a VoiceOver pass over onboarding, profiles, journal, games, subscription, and settings.
  • Running a keyboard only and screen reader pass over keepah.com.
  • Checking every core screen at the largest Dynamic Type setting.

This work is in progress now. We will update this statement as each item lands, and we re-review the whole statement at every major release.

If you hit a barrier, tell us

We want to hear about it, and we will help you get to what you needed.

hello@keepah.com

You can also write to us at 7VN Intelligence LLC, 30 N Gould St, Ste N, Sheridan, WY 82801, USA.

We aim to acknowledge accessibility reports within 2 business days and to tell you what we are doing about it within 10 business days. If something blocks you from using a feature you have paid for, we will find another way to get it done for you in the meantime.

Scope and legal framework

This statement covers the Keepah iOS app and keepah.com.

Keepah is operated from the United States by 7VN Intelligence LLC. If Keepah is offered to users in the European Union, the European Accessibility Act, in force since 25 June 2025, applies and assigns obligations by role. Our role under that Act, and the conformity documentation it requires, have not yet been assessed. We will complete that assessment with counsel before any EU facing launch.