Built to be used by everyone.

We target WCAG 2.2 Level AA on the public site, the extension store and the developer portal: one heading per page, landmarks, keyboard access to every control, text that meets AA contrast in both light and dark themes, and motion that respects a reduced-motion preference.

The desktop app follows the conventions of the platform it runs on, uses native controls where it can, and is reachable by keyboard.

We treat an accessibility defect as a bug, with the same priority as a functional one — not as a feature request.

• Every public page has a skip link, a single h1 and the usual landmarks.
• Navigation is fully keyboard operable. Focus is always visible, Escape closes the site index, and focus returns to the control that opened it.
• Colour pairs are checked against AA in both themes by an automated test, so a quieter grey cannot quietly fall below the floor again.
• Animations and transitions stop when your system asks for reduced motion.
• Form fields have programmatic labels; icons are hidden from assistive technology unless they carry meaning.
• Images that convey something have alt text; decorative images are hidden from screen readers rather than described.

These are true today. We would rather list them than have you discover them.

• Sign-in, account management, payout onboarding and card payment are hosted by Clerk and Stripe. We choose those providers but cannot change their markup. If one of them blocks you, email us and we will find another route — a manual payout, for example.
• Extension screenshots, logos and descriptions come from the publishers who upload them, and some descriptions are thin. We remove listings that ignore feedback.
• The Team Canvas in the desktop app is a spatial view. It is keyboard operable, but its structure is not yet fully exposed to screen readers.
• Some older marketing pages still use components built before the current design system; they are being converted one at a time.

Email support@minotauris.app with “Accessibility” in the subject. Tell us the page or feature, what you were using (a screen reader, the keyboard, zoom, voice control) and what happened. A screenshot or a recording helps, but do not send anything you would rather not share.

We aim to reply within three business days and to fix the problem, or offer you a working alternative, within thirty days. If the barrier is inside a surface we do not control, we will say so plainly and find a route around it.

You can also read our Terms of Service and Privacy Policy.

This statement is reviewed whenever the site’s design system changes, and at least once every twelve months. The date at the top is the last review, not the last edit.

It describes current practice and the standard we aim at. It is not a certification, and it does not replace testing with the assistive technology you actually use — which is why the address above is a real inbox and not a form.