Hecho para todos
quienes aman a una mascota.

Caring for a pet doesn't pause for a migraine, a tremor, or a screen reader. Maskotis aims to meet WCAG 2.2 level AA across the app and this website, and to push past it where the spec is too quiet.

We treat accessibility bugs the same way we treat security bugs: tracked openly, fixed with priority, and never closed as “works as designed.”

• Screen readers: tested weekly with VoiceOver (iOS, macOS), TalkBack (Android), and NVDA (Windows). Every interactive element has a name, role, and state.
• Keyboard: the entire app is reachable without a mouse. Focus is always visible, and we never trap it inside a modal.
• Contrast: body text meets 4.5:1, large headings and UI components meet 3:1, and our colour tokens are checked at build time.
• Motion: animations respect prefers-reduced-motion. Nothing flashes faster than three times per second.
• Text: the app reflows down to 320 px and up to 200% zoom without losing content or function.
• Forms:every input has a visible label, errors are announced, and we never ask for a CAPTCHA you can't hear.

We keep an honest list of known issues rather than pretending they aren't there:

• The pet-photo cropper relies on drag gestures; a keyboard fallback is in review and ships in the next release.
• A handful of older journal posts have images without alt text. We're working through them.

If something blocks you that isn't on this list, write to us and we'll add it before end of day.

Accessibility isn't a final-pass review on the way to ship — it rides with each pull request:

• Static checks on every commit: ESLint jsx-a11y, axe-core in component tests, and contrast checks against our design tokens.
• Manual review for any new interactive component, with a written keyboard and screen-reader trace before merge.
• External audit twice a year by a third-party agency that includes disabled testers. The latest report is linked below.

The fastest way to reach us is email. Tell us what you were trying to do, the device and assistive tech you were using, and what happened. Screenshots and screen-recording captions help, but they aren't required.

• Acknowledgement within 1 working day.
• Triage and a fix plan within 5 working days.
• For show-stoppers we ship a workaround the same week, even if the full fix lands later.

Prefer a phone or video call? We can do that too — just tell us which and a time that works.

We measure ourselves against WCAG 2.2 level AA, which covers most of the obligations under the EU Accessibility Act, the UK Equality Act, Section 508 in the US, and the ADA. Where a regional rule asks for more, the regional rule wins.

We refresh this page every quarter, and immediately after any audit or material change.