Legal

Accessibility Statement

Read tsumo's accessibility statement, current support options, design goals, and reporting path for barriers that affect Mahjong play or learning content.

Accessibility Statement preview image

What this page covers

  • Read tsumo's accessibility statement, current support options, design goals, and reporting path for barriers that affect Mahjong play or learning content.
  • Read the guide, practice one focused skill, and then apply it in the game client while the examples are still fresh.
  • The live app experience on tsumo follows the same route structure, ruleset labels, and practice surfaces linked below.

Best next step

  • Read the summary here, then open the linked tutorial or puzzle so the concept becomes a decision, not just a definition.
  • If a route compares variants, pick one mode and stay with it long enough to notice recurring mistakes.
  • Use bot games for repetition and puzzles for isolated pattern training before joining online tables.

Accessibility Statement

We are working toward WCAG 2.2 AA accessibility for our website and gameplay interfaces.

1. Accessibility Goal and Standard

Our objective is to provide an inclusive experience aligned with WCAG 2.2 Level AA across key user journeys such as navigation, authentication, and gameplay. We use WCAG 2.2 AA as our product baseline for design, development, and testing.

2. Conformance Status

The Service is partially conformant with WCAG 2.2 AA. Partially conformant means that some parts of the website or gameplay interface may not fully conform yet. We do not present this statement as a guarantee of compliance with any specific law; it documents our current product target and support process.

3. Assessment Method

We assess accessibility through code review, keyboard checks, responsive layout review, automated accessibility checks where available, and manual review of key journeys such as learning pages, legal pages, authentication, puzzles, and game controls.

4. Current Measures

We use semantic HTML, keyboard-accessible controls, visible focus states, color contrast checks, and responsive layouts. We continue improving assistive technology compatibility.

5. Compatibility Scope

We target current versions of major desktop and mobile browsers and common platform assistive technologies. Some older browsers, unsupported browser extensions, or custom input tools may behave differently.

6. Known Limitations

Some advanced game interactions may still require additional labeling, screen reader optimization, alternate input refinement, and clearer announcements for rapidly changing game state. We prioritize fixes based on severity, reach, and user impact.

7. Feedback and Support

If you encounter an accessibility barrier, contact support@tsumo.io or use the Contact Us page with the page URL, device, browser, and assistive technology details so we can reproduce and address the issue. We aim to acknowledge accessibility reports within 5 business days and provide a meaningful update or workaround as soon as reasonably possible.

If a feature is not accessible to you, ask for an alternative way to access the same information or support path while we investigate.

Related Links

Report an Accessibility Barrier