# #020

#### January 16, 2026***:-*** Accessibility Enhancements & Developer API Alpha

### Purpose

To increase platform inclusivity through accessibility compliance, and begin exposing Tapzi’s core logic through an early-stage developer API for future third-party integrations.

***

### Key Highlights

**♿ Accessibility Review & Implementation**

* Accessibility audit completed focus on color contrast, screen reader compatibility, and keyboard navigation.
* Tab and arrow-key navigation paths now fully operational for match setup and gameplay.

**🧩 Developer API (Alpha) Drafted**

* RESTful endpoint suite for match creation, querying, and result polling documented.
* Initial SDK blueprint includes wallet verification stubs and event hook examples.
* Rate limiting and key-based access control system planned for broader rollout.

**📜 Hall of Fame & Stats Draft**

* Static Hall of Fame page launched for MVP tournament winners and leaderboard top ranks.
* Data pulled via new API layer; backfilled manually while live dynamic hook is being developed.

***

### Why It Matters

* Accessibility upgrades bring Tapzi in line with inclusive gaming standards, especially for keyboard-first and vision-impaired users.
* Developer API marks the start of an open ecosystem—enabling third-party tools, game proposals, and analytics services.
* Hall of Fame provides visible, permanent recognition of high performers, enhancing competitive culture.

***

### Open Issues

* Dynamic labels (e.g., board state updates) occasionally lag during rapid game changes.
* Developer docs missing authentication and rate-limiting sections—currently internal-only access.
* Some mobile browsers ignore timezone flags, reverting to UTC in rare cases.

***

### Fixed

* Bug-report form now provides confirmation ID and stores submissions in audit log.
* Keyboard focus now reliably loops through modal content (no focus traps).
* Region detection now updates if user logs in from a new device in a different locale.

***

### Next Steps

* Add OAuth2-based key management for developer API access.
* Expand accessibility review to helpdesk, modals, and interactive charts.
* Begin alpha testing of third-party leaderboard bots and match aggregators.
* Add support for localized match alerts (SMS/email experiments).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tapzi.io/tapzi-dev-release/020.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.