Hi! I'm Florian (Flarion), developer of the TeamTalk VoiceOver Client — an open-source Python client for TeamTalk 5, purpose-built for blind and visually impaired users.
What we build
Our client makes TeamTalk (a low-latency voice/chat platform) fully accessible for:
- macOS: VoiceOver + Braille display (wxPython with custom accessibility patches via PyObjC)
- Windows: NVDA/JAWS (PySide6 with full accessible names, roles, and states)
The project is actively maintained and used in German-speaking and international blind communities.
Why I'm reaching out
Able Player and TeamTalk VoiceOver Client operate in different domains (media playback vs. real-time voice communication), but we share the same user community — blind and visually impaired people who depend on accessible software.
I'm interested in:
- Cross-promotion: Letting our respective users know about each other's tools
- Exchanging accessibility implementation notes: You have deep expertise in accessible HTML5/web; we work in native Python UI accessibility (wxPython/macOS, PySide6/Windows)
- General connection: It's valuable to know other developers who truly understand accessibility from the ground up
Would you be open to a mention in each other's READMEs, or just an informal exchange of notes on what works and what doesn't in screen reader accessibility?
Links
Thanks for the outstanding work on Able Player — it's a model for web accessibility done right.
— Florian / Flarion
Hi! I'm Florian (Flarion), developer of the TeamTalk VoiceOver Client — an open-source Python client for TeamTalk 5, purpose-built for blind and visually impaired users.
What we build
Our client makes TeamTalk (a low-latency voice/chat platform) fully accessible for:
The project is actively maintained and used in German-speaking and international blind communities.
Why I'm reaching out
Able Player and TeamTalk VoiceOver Client operate in different domains (media playback vs. real-time voice communication), but we share the same user community — blind and visually impaired people who depend on accessible software.
I'm interested in:
Would you be open to a mention in each other's READMEs, or just an informal exchange of notes on what works and what doesn't in screen reader accessibility?
Links
Thanks for the outstanding work on Able Player — it's a model for web accessibility done right.
— Florian / Flarion