Hi! I'm Florian (Flarion), developer of the TeamTalk VoiceOver Client — an open-source Python client for TeamTalk 5, built for blind and visually impaired users.
Our Windows accessibility approach
The Windows UI is built with PySide6 (Qt), with careful attention to NVDA compatibility:
- All controls have explicit accessible names, roles, and states
- We use Qt's accessibility interfaces to expose list items, buttons, text fields correctly to NVDA
- Tab order and focus management are designed for keyboard-only navigation
- Tested with NVDA on Windows 10/11
Why I'm reaching out
We're considering whether an NVDA add-on companion could further improve the integration — for example:
- Custom announcement logic for incoming messages and user events
- Braille display formatting tailored to our UI
- Possibly intercepting TeamTalk-specific events at a lower level than the app can provide
Before investing time in this direction, I'd love guidance from people deep in the NVDA add-on ecosystem:
- Is a companion add-on a reasonable approach for a standalone Python/Qt app, or is good accessible naming in the app itself usually sufficient?
- Are there patterns or existing add-ons we should study as references?
- Is there a community forum or chat where we could connect with add-on developers?
The DevGuide seems like the right place to start this conversation. Happy to share more about our implementation if useful.
Links
Thanks for maintaining this resource!
— Florian / Flarion
Hi! I'm Florian (Flarion), developer of the TeamTalk VoiceOver Client — an open-source Python client for TeamTalk 5, built for blind and visually impaired users.
Our Windows accessibility approach
The Windows UI is built with PySide6 (Qt), with careful attention to NVDA compatibility:
Why I'm reaching out
We're considering whether an NVDA add-on companion could further improve the integration — for example:
Before investing time in this direction, I'd love guidance from people deep in the NVDA add-on ecosystem:
The DevGuide seems like the right place to start this conversation. Happy to share more about our implementation if useful.
Links
Thanks for maintaining this resource!
— Florian / Flarion