Kindred · Compass

Accessibility

Last updated: April 2026

KindredCompass is built to be usable by as many people as possible. We take accessibility seriously, and we keep working on it. This page documents what we currently support, where we know we fall short, and how to reach us if something doesn't work for you.

What We Support Today

• VoiceOver — Every screen has been labeled. Cards, buttons, filters, and sheets announce themselves with descriptive labels, values, and hints. Navigation works screen-by-screen without visual focus.
• Dynamic Type — All text scales with the iOS text size setting, from the smallest caption label up through AX3 (Accessibility 3). The layout reflows rather than clipping.
• Reduce Motion — When Reduce Motion is enabled in iOS Settings, card animations, spring transitions, and phase crossfades are replaced with instant or gentle fades.
• Dark mode — The entire app renders in a dark palette with high-contrast text and clear focus states. No bright white flashes.
• Tap target sizing — Every interactive element meets or exceeds Apple's 44×44 point minimum for comfortable tapping, including filter pills and small icon buttons.
• Haptic feedback — Actions that matter (scan, favorite, adventure transitions) use the iOS haptic engine so users who don't rely on sight still feel the confirmation.
• Semantic grouping — Related elements are combined into single accessibility elements so VoiceOver users don't have to swipe through every child view to hear one card's content.

Where We Fall Short

We're honest about gaps because fixing them depends on hearing about them.

• Voice Control has not been systematically tested. Most actions should work, but we can't guarantee coverage of every screen.
• External keyboard navigation on iPad is partial. Core scan and result-browsing flows work; deeper flows like Adventure editing haven't been fully verified.
• Dynamic Type beyond AX3 is best-effort. Above that size, some denser layouts may still wrap awkwardly. We cap at AX3 intentionally so the design stays coherent.
• Switch Control has not been audited. If you use Switch Control and hit a blocker, please tell us; we treat those reports as urgent.
• We do not currently publish a WCAG conformance report. We target WCAG 2.1 AA as a working standard but have not completed a formal audit.

How We Test

Accessibility is part of the release checklist. Before every release we verify VoiceOver labels on new screens, confirm Reduce Motion is respected where we added animation, and run the app at multiple Dynamic Type sizes. We also use Apple's Accessibility Inspector to catch missing labels and contrast issues.

Ongoing Work

Each release we pick one accessibility area to strengthen. Current priorities:

• Voice Control audit across every primary flow
• External keyboard navigation on iPad for Adventure editing
• Better descriptive context for DNA match percentages in VoiceOver
• Offline-mode accessibility (when we ship it) from day one

Report an Issue

If something doesn't work for you, please tell us. Accessibility bug reports are always prioritized over feature requests. You don't need to know the technical name for the issue — a plain description of what you were trying to do is enough.

kindredcompasssupport@gmail.com

Standards Reference

We work against Apple's iOS Accessibility Guidelines and WCAG 2.1 AA as a target standard. KindredCompass is not certified, but our intent is to match or exceed these in every release.