Skip to content
Thor
Back to Thor

Accessibility Statement

Last updated

Thor Exchange is committed to making its website at thorexchange.xyz (the “Interface”) usable by as many people as possible, including people who rely on assistive technologies such as screen readers, keyboard navigation, and magnification.

Conformance target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, the standard recommended by the W3C for public-facing services and broadly aligned with the European Accessibility Act and Section 508. We consider our current conformance status to be “partially conformant”, meaning that most of the Interface meets the standard but some parts do not yet fully conform. We are actively working to close the remaining gaps.

What we have implemented

  • Keyboard navigation — interactive elements are reachable and operable with a keyboard alone (Tab, Enter, Space, and arrow keys where appropriate).
  • Visible focus indicators — focus outlines are preserved and focus order follows the visual reading order.
  • Skip link — a “skip to content” link lets keyboard and screen-reader users bypass repeated navigation.
  • Reduced-motion support — animations respect the prefers-reduced-motion setting.
  • AA color contrast — our design tokens target the AA contrast ratios (4.5:1 for body text, 3:1 for large text and interactive controls) against the theme background.
  • Semantic structure and ARIA — proper heading hierarchy, landmarks, and list and table semantics, with aria-label and related attributes on controls, icons, and dialogs where a visible label is not sufficient.
  • Labeled forms — inputs have associated labels or accessible names.
  • Resizable content — content reflows and remains usable at up to 200% browser zoom.

Known limitations

We are honest about where work remains. Known limitations include:

  • Complex data visualizations, such as the liquidity-density and bonding-curve charts, are provided with text or tabular alternatives where feasible, but not every chart yet has a complete non-visual equivalent.
  • Some dynamic status and error messages may not yet be announced through aria-live regions in every flow.
  • Certain third-party components (for example, wallet-connection dialogs) are outside our direct control and may not fully meet AA.

How we verify

  • Keyboard-only walkthroughs of primary flows before public releases.
  • Automated accessibility checks (including Lighthouse) in our workflow.
  • Screen-reader smoke tests (for example, VoiceOver and NVDA) on major navigation changes.

Feedback

If you encounter an accessibility barrier on the Interface, or need content in an alternative format, please tell us. We welcome your feedback and will make reasonable efforts to respond promptly and to resolve the issue. Contact the team via Telegram (link available on our official channels).

Changes

We review this statement after meaningful changes to the Interface. The “Last updated” date above reflects the most recent review.