Accessibility

MindGlitch is built to be usable by as many people as possible. This page describes what we do, what we know we could do better, and how to tell us if something is broken.

What we aim for

  • WCAG 2.2 Level AA as the baseline for text contrast, focus states, and keyboard navigation.
  • Semantic HTML — real headings, lists, buttons, landmarks — so screen readers can follow the page without guesswork.
  • Keyboard-first interactions. Every interactive element reachable via Tab, with a visible focus ring.
  • Respects prefers-reduced-motion: animations and card flips fall back to cross-fades.
  • No auto-playing audio; any video on the site is muted and captioned.
  • Readable type at 16px+ minimum; 140%+ line-height for body copy.

Known limitations

  • The 3D view on /biases is hidden from public navigation — it's not keyboard-navigable and may not perform well on low-end devices. Table view is similarly hidden.
  • The printable PDF ebook and cheat sheets are visual artifacts. A plain-text companion export is on the roadmap.
  • Some illustrations rely on color to convey category grouping; category names are always rendered as text alongside.

Tell us if something is broken

If any part of MindGlitch is unusable for you, email hello@mindglitch.app with what you tried, what happened, and your assistive-tech setup if you're using one. Accessibility bugs get prioritized over feature work.