Our commitment
Accessibility isn't a feature we bolt on at the end. We aim for both this website and the boopr app to meet the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA as a working target. We're a small team and we won't claim perfect conformance, but we treat accessibility defects as real bugs and fix them.
What we've built in
- Keyboard and screen readers. This site uses semantic HTML and labelled controls so it can be navigated by keyboard and read by VoiceOver, TalkBack, NVDA, and JAWS.
- Reduced motion. If your device requests reduced motion, our fade and scroll animations are switched off automatically.
- Contrast and text. Body and interface text is chosen to meet AA contrast against our dark background, and the layout reflows down to small screens and up to large text sizes.
- In the app. boopr supports the system text-size and Dynamic Type settings, respects reduce-motion, and is built to work with VoiceOver and TalkBack. Our screenshot-protection on private screens is implemented to avoid breaking screen-reader output.
Known limitations
We'd rather be honest than aspirational. A few areas we're still working on:
- Some decorative animations and the ambient hero glow are visual only; they convey no information, but we're continuing to test them with assistive tech.
- Photos and videos posted by other people may not always carry descriptive alt text, since that content comes from users, not us.
- The app is iOS and Android only. There is no web version, partly because boopr depends on hardware-backed key storage that browsers can't provide.
Tell us when something doesn't work
If any part of boopr.com or the app is hard to use with assistive technology, we want to hear about it. It helps us fix the right things. Email support@boopr.com or use our contact page. Tell us the page or screen, the device and assistive tech you're using, and what went wrong. We aim to respond within a few business days.