Accessibility
An app that lets two people understand each other has to be understandable too.
We design metcha to be usable by as many people as possible, including people who rely on assistive technology. This page describes our approach, the standards we target, and how to tell us when we get it wrong.
Standard
We aim to meet WCAG 2.1 Level AA across the metcha iOS app and the metcha.io marketing site. We also follow Apple's Human Interface Guidelines for accessibility for the iOS app, including support for VoiceOver, Dynamic Type, and Reduce Motion.
What we've built so far
The iOS app
- VoiceOver labels on every interactive control, including the language picker, conversation start/stop, and transcript replay.
- Dynamic Type support on all primary copy; the live transcript scales with the system text size.
- Visual transcript that mirrors the audio output, so a user who can't hear part of a turn can still follow the conversation.
- Reduce Motion-aware animations: any non-essential motion is removed when the system preference is set.
- Color choices tested for WCAG AA contrast in both light and dark mode against the saffron and sage accent colors used throughout the app.
The marketing site
- Semantic landmarks (
header,nav,main,footer) and a visible skip-to-content link. - Keyboard-navigable menus, including the mobile drawer.
- Focus styles that meet AA contrast and don't rely on color alone.
- Reduced-motion fallbacks for the scroll-driven hero animation.
- AA-tuned color tokens for both light and dark themes.
- Form fields with persistent labels (no placeholder-only labels).
Where we know we still have work
We try to be honest about gaps:
- We have not yet completed a third-party accessibility audit of the iOS app. We plan to do so before our first major update post-launch.
- Some embedded SVGs on the marketing site use motif imagery without long-form descriptions. We're adding richer alternative text for those over time.
- Right-to-left language layouts in the conversation UI are actively being tested; report anything that looks off and we'll prioritize a fix.
Report a barrier
If something on the metcha app or website is hard to use with assistive technology, we want to know. Please email hello@metcha.io with the subject line Accessibility and a brief description of the issue, the device or assistive technology you're using, and the page or screen where you ran into it. We respond within five business days.
Compatibility
metcha for iOS supports the assistive technologies built into iOS. The marketing site is tested with the latest two versions of Safari, Chrome, Edge, and Firefox, with VoiceOver on macOS and iOS, and with NVDA on Windows.