Accessibility

Our target

This website targets WCAG 2.2 level AA, with body text aiming for AAA contrast (7:1 or better). Accessibility is treated as a requirement in the design system — every component is built against it, not retrofitted.

What we have built

• Keyboard: every page is fully operable by keyboard, with a visible high-contrast focus indicator (3px outline) and a skip-to-content link on every page.
• Screen readers: semantic landmarks (header, nav, main, footer), a logical heading hierarchy on every page, labelled navigation regions, and descriptive link text throughout.
• Contrast: headings ~14:1, body text ~9:1, and interactive elements at 4.5:1 or better. The palette is documented with a contrast table in our design system.
• Text: 17px base size, line length capped near 72 characters, and layouts that reflow without horizontal scrolling at 400% zoom (data tables scroll within their own region).
• Motion: animation is minimal; with prefers-reduced-motion enabled, it is disabled entirely.
• No JavaScript required: all content works with scripts disabled. The only scripted behaviour is the mobile menu toggle; expandable FAQ items use the native details element.
• Images: every informative image (including the phone-screen illustrations) has a full-sentence text alternative; decorative graphics are hidden from assistive technology.
• Language: plain English first — technical concepts get a plain sentence before any jargon, and jargon is explained on first use.

The wallet app

The reference wallet app is built to work with TalkBack (Android) and VoiceOver (iOS), with spoken guidance for document framing and liveness challenges. If a liveness challenge is not possible for you, alternative checks are supported — see accessibility support in the help centre.

Known limitations — stated honestly

• Data tables scroll horizontally on narrow screens. Headers remain associated for screen readers, but horizontal scrolling is required at small sizes.
• The phone-screen illustrations convey their content through text alternatives, which summarise rather than reproduce every visual detail.
• The wallet capture flow inherently requires a camera. Camera-free verification paths are a recognised gap in the current reference implementation.
• This statement has not yet been backed by an independent third-party accessibility audit. Self-assessment is rigorous but is not the same thing, and we won't pretend otherwise.