Skip to content
Mindhog

Coming soon for iPhone and Android

Join the waitlist

Accessibility statement

Last updated: October 26, 2026

We want everyone to be able to use mindhog.app: with a keyboard, with a screen reader, zoomed in or with larger text. This page explains how far we’ve got, how we test, and where things don’t work yet.

What this statement covers

This statement covers all pages of the website mindhog.app, in every language they’re available in.

The website introduces the upcoming Mindhog app and lets you join the waitlist. To join, you enter your email address and confirm it with a link we send you, which works for 48 hours. After a short confirmation email, you’ll only hear from us again when Mindhog launches. Every email has a link to unsubscribe.

The app itself isn’t out yet and isn’t covered by this statement.

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. For websites, the European standard EN 301 549, version V4.1.1, builds on the same requirements. Based on our own testing, mindhog.app largely meets these requirements. Where it doesn’t yet, we say so below.

How we test

  • Automatically, before every release. Every change to the website runs through automated tests before it goes live. They include accessibility checks with axe against the WCAG 2.2 AA rules, on the start page in all seven languages, on the legal pages, on the pages about the method and about Mindhog, on this statement and on some of the waitlist pages. If a check fails, the change isn’t published. Automated tests only catch some problems, though.
  • Targeted checks, on October 25 and 26, 2026. Using test scripts, we went through the whole site with only a keyboard, in Chrome and in WebKit, the engine behind Safari. We zoomed to 400 % and narrowed the screen to 320 pixels, tried larger text and wider text spacing, and measured colour contrast. We also checked what a screen reader receives by looking at the browser’s accessibility tree.
  • Not done yet. We haven’t tested with a real screen reader such as VoiceOver or NVDA, on real phones, or with people who use assistive technology every day.

What already works

  • Everything works with a keyboard, in reading order.
  • Text has a contrast of at least 4.5 to 1, large text at least 3 to 1.
  • Nothing moves: no animations, no videos, nothing that plays on its own.
  • At 400 % zoom or 320 pixels wide, nothing needs scrolling sideways and no text gets cut off.
  • Each page has one main heading, a clear heading structure and the right language set.
  • Decorative images are hidden from screen readers.
  • Buttons and form fields are at least 24 by 24 pixels, most of them 44.
  • The waitlist form has a visible label, and its error message tells you how to fix the problem.
  • There’s no cookie banner to get past, because the site sets no cookies.

Known limitations

  • If you send the waitlist form before the page has finished loading, nothing happens and you get no message. This window is usually shorter than a tenth of a second, but on a slow connection it can last a few seconds. What you typed stays in the field, and sending it again works.
  • Without JavaScript, you can’t join the waitlist, confirm your email address or unsubscribe. Instead of the form or the button, you’ll see a note that says so.
  • If you send the form by clicking the button or pressing the space bar on it and the email address isn’t valid, the focus moves into the field. Your screen reader then reads “invalid” and the error message, without a separate announcement. If you’ve turned off hints in your screen reader, you’ll only hear “invalid”.
  • The hidden area that announces errors to screen readers is emptied after 7 seconds. The error message itself stays visible at the field.
  • In the picture of the app, the blue “Plan it” label has white text on blue with a contrast of 3.8 to 1. That’s only enough for large, bold text, so the label is always bold and at least 18.67 pixels. A test makes sure it stays that way.
  • The imprint, the privacy policy, the pages about the method and about Mindhog and this statement are only available in full in English and German. The other languages have a short privacy summary and link to the English versions.
  • We’ve tested with automated tests (axe) and with test scripts in Chrome and WebKit that check the accessibility tree, announcements and focus. We haven’t tested with real screen readers such as VoiceOver, NVDA or JAWS, or on real devices, yet. WebKit, the engine behind Safari, doesn’t run in every automated test.

Feedback and contact

Found a barrier, or something that’s hard to use? Write to hello@mindhog.app.

It helps if you tell us which page it was, what you were trying to do and what you use, for example a screen reader or zoom. We’ll get back to you as soon as we can.

About this statement

We wrote this statement on October 25, 2026 and updated it on October 26, 2026, based on our own testing. The website was last checked on October 26, 2026.