Accessibility Statement

What we do to keep the interface usable with a keyboard, a screen reader and large text — and an honest note on what has not been formally audited.

Last updated: September 20, 2026

This page is written in plain language for general information. It has not been reviewed or approved by a lawyer, and it is not legal, tax or financial advice.

01Our commitment

Financial information should be readable by everyone. We aim to make the interface usable with a keyboard, with a screen reader, at large text sizes and without relying on colour alone.

We use the Web Content Accessibility Guidelines as our reference. We have not completed a formal audit and we do not claim certification or a conformance level.

02What is in place today

The interface is built with the following practices.

  • Semantic headings, landmarks and labelled form controls.
  • Visible focus styles and keyboard operation for buttons, links, sliders and selectable cards.
  • State conveyed in text as well as colour — for example position health and connection status.
  • Status messages announced to assistive technology where they change without a page reload.
  • Responsive layouts that reflow down to small phone widths and tolerate browser zoom.

03Known limitations

Some parts of the experience come from third-party components, including the sign-in and wallet interface, and we do not control their markup or behaviour.

Dense numeric tables, sliders and animated elements may still be awkward for some users. If you reduce motion at the system level, the browser respects that for the animations we control.

04Feedback

If something is hard or impossible to use, please tell us through the Support page and describe the page, what you were trying to do, and the assistive technology or settings you use. Reports like these are the main way this improves.

A formal production support channel will be published before launch; until then feedback is handled through the guidance on the Support page.