Accessibility statement
Mini Brief is built to be usable by everyone, including people who rely on a screen reader, a keyboard, a switch, magnification, or reduced motion. This page says what we aim for, how we check it, and how to tell us when something falls short.
What we aim for
The web app at app.minibrief.app targets the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. In practice that means, among other things: every control can be reached and operated with a keyboard and shows where focus is; text and controls keep at least a 4.5:1 contrast against their background in all three colour themes; every field has a label and every icon-only button a name; pages are laid out in landmarks a screen reader can jump between; nothing depends on colour alone; the page zooms freely; and animation is turned off for anyone who has asked their device for less motion.
How we check
Every page of the web app is run through an automated accessibility engine (axe-core, WCAG 2.2 AA rules) on a phone-sized and a desktop-sized viewport, in each colour theme, and the sign-in, settings, billing and mail flows are walked by hand with a keyboard and with VoiceOver. We re-run those checks before each release.
Known limitations
- The full inbox at /mail is a large single-page application running inside the page. It is keyboard-operable and labelled, and its text contrast is corrected for the web; a few of its controls are smaller than the finger-sized targets the rest of the app uses. We are working through it.
- Email content itself is shown as the sender wrote it; we cannot correct the accessibility of someone else's message.
- Payments run on Stripe's hosted pages, whose accessibility is Stripe's.
Tell us
If any part of Mini Brief is hard to use, write to support@minibrief.app with the page and what happened. We answer within five business days, and a barrier that stops you using the product is treated as a bug of the highest priority.
Last reviewed 6 September 2026.