A usable product is an inclusive product.

What we commit to

• — All interactive elements reachable and operable with a keyboard alone, with visible focus indicators.
• — Text contrast at or above WCAG AA thresholds in both dark and light themes (4.5:1 body, 3:1 large text).
• — Semantic HTML landmarks, heading hierarchies, and ARIA only where native semantics fall short.
• — Respect for the user’s prefers-reduced-motion setting — animations collapse to cross-fades or are disabled.
• — Form fields with visible labels, descriptive errors, autocomplete attributes, and correct input types.
• — Skip-to-content link at the top of every page.
• — Works without JavaScript on informational pages (landing, legal, faq, press, accessibility, changelog).

Known limitations

We’re honest about where we haven’t finished. These are on the roadmap and will be closed out in coming releases:

• — The contract signing ritual is animation-heavy; a reduced-motion fallback exists but the screen-reader narrative of the same flow is still being tuned.
• — Some mocked charts on the demo dashboard use colour alone to distinguish “you” from “opponent.” Shapes are being added as a second channel.
• — PDF contracts are tagged but not yet fully structured — we’re targeting PDF/UA-compliant output for the 1.0 release.

Assistive tech we test with

• — VoiceOver on macOS / iOS (Safari)
• — NVDA on Windows (Chromium + Firefox)
• — TalkBack on Android (Chromium)
• — Keyboard-only navigation on all of the above
• — 200% browser zoom + 400% text-only zoom

Found a barrier?

Tell us. Describe what you were trying to do, what went wrong, and which assistive technology you were using. We aim to respond within two business days and to ship a fix (or a timeline) within ten.