Accessibility Statement

Conformance status

We build Galaxy Grails against Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.

Galaxy Grails is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the product meets the standard, and some parts of it do not yet. We have not commissioned a third-party audit, so this is our own assessment rather than a certified one. We will say so here when that changes.

Last reviewed October 2026.

What works

• Every interactive control is reachable and operable with a keyboard, and the focus indicator is never suppressed.
• Text meets or exceeds the 4.5:1 contrast ratio against every surface it is used on.
• A skip link on each layout jumps past the navigation to the page content.
• Every page has one top-level heading, and headings descend in order.
• Buttons and form fields carry names that a screen reader can announce, including the ones that show only an icon.
• Touch targets on buttons are at least 44 by 44 pixels.
• Form fields, checkboxes and switches have a visible boundary that meets the 3:1 contrast ratio, so a control is identifiable as a control rather than as an unmarked area of the page.
• Pages reflow into a 320 pixel wide column and stay usable at 200 percent zoom, with no second scroll direction in either case.
• The navigation drawer on a phone can be dismissed with a key, with its own close button, or by tapping outside it, and closing it returns you to where you were.
• Ambient motion, including the galaxy background and the card reveals, honors your operating system's reduce-motion setting. Reveals that are part of gameplay still animate, because the animation is the information.
• Color is never the only way we tell you something. Status chips carry text, and amounts carry a sign as well as a color.

Known limitations

These are the parts we know fall short. We would rather list them than let you discover them.

• Live streams have no captions. Show audio is not captioned in real time, so a viewer who is deaf or hard of hearing gets no text alternative for what a host says during a break. Chat is fully readable, and every pull is recorded in your account history as text, but neither is a substitute. We do not have a date for this.
• Some failure notices are announced once and then fade. Every form shows its error under the field as well as in a notification, including buying back a card during a show. A notice that something failed in the background, such as a section that could not load, is read out once by a screen reader and then fades.
• Third-party screens are outside our control. Payment and identity verification are handled by Stripe on Stripe's own pages. We chose those flows partly for their accessibility, but we cannot fix them ourselves.

Tell us about a barrier

If something on Galaxy Grails blocks you, we want to hear about it, including the parts already listed above. Tell us what you were trying to do, what page you were on, and what assistive technology you use if any. It helps, but you do not need any of that to write to us.

Contact support is the fastest route and reaches the same people who read this page. We aim to reply within two business days.

If we cannot resolve it, you can escalate to the enforcement body in your country. In the European Union that is the national market surveillance authority for the Accessibility Act.