Legal
Accessibility
Effective August 9, 2026 · version 2026-08-09
We want MuffinBiter to work for every dog owner, including those using a screen reader, a keyboard, or a phone with the text size cranked all the way up.
What we're aiming for
WCAG 2.2 Level AA. That's the target for both this public site and the app itself. We're not claiming full conformance — claiming it without a formal third-party audit would be dishonest — but it's the standard we build and review against.
What's in place today
- Semantic HTML throughout, with a single logical heading order per page and real landmarks (
header,nav,main,footer). - Keyboard operable end to end, with a visible focus ring on every interactive element and a “skip to content” link.
- Colour contrast at AA for body text and interactive elements, in both light and dark themes.
- Colour is never the only signal — state carries an icon, a label or a shape as well.
- Tap targets of at least 44×44px, with generous spacing between them.
- Text scales to 200% without loss of content or function; the layout is fluid rather than fixed.
- Reduced motion respected —
prefers-reduced-motiondisables animation and smooth scrolling. - Dark mode on these public pages follows your system setting rather than forcing a theme on you.
- The public site needs no JavaScript. Every page here — parks, guides, policies — renders fully on the server.
- Form fields are properly labelled, with errors described in text rather than by colour alone.
- Inputs use a 16px base size so iOS doesn't zoom when you focus them.
Known gaps
Written down honestly, because a statement that lists only strengths is marketing:
- Dog photos are uploaded by members and don't yet have a field for descriptive alt text. They currently fall back to the dog's name.
- The “Park Pulse” busy-hours chart conveys its shape visually; the underlying numbers are available in text, but the chart itself isn't yet fully described.
- The signed-in app is light-theme only. These public pages honour your system dark mode; the app doesn't yet.
- We have not commissioned an independent accessibility audit. Our own automated checks cover contrast, target size, heading structure and layout overflow on every public page, in both themes, on every change — but automated checks are not an audit.
Tell us where it breaks
If something is hard or impossible to use, email hello@muffinbiter.com with what you were trying to do and what assistive technology you're using. We treat accessibility bugs as bugs — they go in the same queue as everything else, near the top. We aim to respond within five business days.
If you need information from the app in a different format while we fix something, ask and we'll get it to you directly.
Other policies: Terms · Privacy · Cookies · Your privacy choices · Community guidelines · Accessibility