Accessibility, plainly.

Updated October 8, 2026

Our commitment

Homing should work for everyone, including people who use screen readers, keyboard navigation, magnification, or reduced motion. The website and app are designed and built to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA as our working standard.

What that means in practice

• Clear page structure and landmarks so assistive technology can find its way around.
• Color contrast that meets AA ratios, in both light and dark mode.
• Everything works with a keyboard, with a visible focus outline.
• Form fields have proper labels, and errors say what went wrong and how to fix it.
• Wallet addresses are always shown in full, in groups of four, and read out in full to screen readers.
• Your reduced-motion setting is respected, and pinch-to-zoom is never disabled.
• Passkeys let you sign in with Face ID, a fingerprint, a device PIN or a security key, so there's no password to type.

How we check

Before each release, every page and the app's main screens are scanned with an automated WCAG 2.1 AA checker (axe-core) in light and dark mode, on phone and desktop sizes. Critical or serious issues are fixed before release. Automated tools catch most problems but not all, so we also check by hand with a keyboard.

Limits, honestly

Some steps happen outside Homing, such as creating an API key on Kraken's website or using your wallet's app, and we can't control how accessible those are. Browsers and assistive technology also keep changing. We don't claim perfection or legal compliance. We claim a standard, a process, and a fast response when something falls short.

Found a problem?

Email support@gethoming.app with "Accessibility" in the subject. Tell us the page and what got in the way, and we'll fix it or help you another way.