Accessibility

Updated November 5, 2026

Hamhop is built by a UX designer and accessibility specialist with over 20 years of practice. It was part of the plan from the first screen. We aim for WCAG 2.2 AA in the app and on this site.

In the app

• VoiceOver: every control has a name. Callsigns are read letter by letter. "On the air" and "off the air" are announced.
• Talk your way: hold to talk, or tap to start and tap to stop. With VoiceOver on, the button always toggles, and a two-finger double tap keys and unkeys from anywhere.
• Haptics confirm when you key and unkey.
• Large text: all text follows your Dynamic Type size.
• Touch targets are at least 44 by 44 points.
• Color is never the only signal. Status always has words too.
• Reduce Motion is respected, and Hamhop avoids see-through Liquid Glass behind text.
• Plain errors that say what happened and what to do next.

On this site

• A skip link, landmarks and a sensible heading order.
• Same-page links move focus to the section heading, so screen readers announce where you landed.
• No pop-up menus or dialogs, so keyboard focus can never get stuck.
• App screens are drawn as images with a full text description.
• Text contrast of at least 4.5 to 1, in light and dark mode.

Known gaps

Hamhop is in beta. We're still testing with Voice Control and Switch Control on every screen.

Tell us

If something gets in your way, email support@hamhop.app. Tell us what you were trying to do and what assistive tech you use. We read every message.