Repository navigation
Proposal: AAC‑Native Replacement of the TeamTalk User Interface and UI Architecture #3478
Replies: 14 comments
|
Summary
StatePanel
|
|
What AAC Is
|
|
We look forward to a pull request where we can try out this new user interface. |
|
Thanks, Bjorn — that sounds great. Before opening a PR, I’d like to propose a small, self‑contained prototype as the first step. This would introduce the new UI architecture in an isolated folder without touching the existing UI. The goal is to give maintainers something concrete to try out while keeping the current interface fully intact. If that approach works for you, I can prepare a minimal initial PR containing:
This keeps the scope reviewable and lets us iterate together. Let me know if that structure aligns with your expectations. |
|
@trancer1994 hi. |
|
Hi,
Yes, I did say remove QTreeViews, modal dialogs, and similar elements. Since this is a full AAC‑native UI replacement, hierarchical navigation doesn’t work well for the user base I’m building for. Tree views require several steps to reach options that could be activated with one. In my UI, channels will appear on a flat screen where each channel is a single button. Press Enter to join, Escape to leave. This keeps navigation simple and predictable.
The current interface is quite complex for many blind users, especially older users or those with limited technical experience. There are many panes, settings, and nested controls, and it can be overwhelming. That’s why I’m simplifying everything as much as possible in the AAC‑native UI.
There are also practical issues with the existing tree view. For example, if you expand a channel with the right arrow and scroll through the user list, then move between channels with the up/down arrows, screen readers stop announcing channel names until other widgets are collapsed again. This makes navigation frustrating. While tree views and dialogs are common in desktop and blind UX, AAC UX is different. AAC users need single‑step actions and flat navigation because hierarchical structures increase cognitive load.
If you want, I can point you to apps that use the kind of simplified UI approach I’m aligning with.
Regards,
Jamie
…________________________________
From: Amir ***@***.***>
Sent: Tuesday, July 21, 2026 14:31
To: BearWare/TeamTalk5 ***@***.***>
Cc: trancer1994 ***@***.***>; Mention ***@***.***>
Subject: Re: [BearWare/TeamTalk5] Proposal: AAC‑Native Replacement of the TeamTalk User Interface and UI Architecture (Issue #3077)
[https://avatars.githubusercontent.com/u/69115921?s=20&v=4]amirmahdifard left a comment (BearWare/TeamTalk5#3077)<#3077 (comment)>
@trancer1994<https://github.com/trancer1994> hi.
Reading the description of this pr, dispite it's being very long and it's likely written by AI?
It has some things, that I onnistly Don't understand. You are the first person that requesting such a thing in a project.
You said remove qTree view, modal dialogs etc, That's not good.
Tree views and these dialogs are used everywhere, even in Screen readers them selves. Teamtalk's channels are desighned to fit inside tree views. Channels are the items, subchannels and users are childrens of it. I don't think this is useful in any way and something anyone wants to look at. I never saw such an implementation in any app or anywhere.
—
Reply to this email directly, view it on GitHub<#3077?email_source=notifications&email_token=AMV3XJUF2YHJFLNAW75N6735F5WDNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBTGQ3DMNZYGAZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5034667803>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMV3XJVEDODK3Y4D5V2VWO35F5WDNAVCNFSNUABEKJSXA33TNF2G64TZHMZDCNZQGY2DKMZ3JFZXG5LFHMZTONZZGU3TONJRG2QXMAQ>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AMV3XJXIE324P7OTAV5HNMD5F5WDNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBTGQ3DMNZYGAZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/AMV3XJRH6PVUO7EI6S45Y3T5F5WDNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBTGQ3DMNZYGAZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today!
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
@trancer1994 This cannot be fit with teamtalk. Channels system is built to be look this way BTW, You can join a channel by pressing enter, and leaving channels by pressing enter again. What you are saying here does not have any point or usage. Even the moste standard windows dialogs and even nvda looks like this. About not announcing channel items after collapsing channels, it is a qt bug, I've reported it to Qt, And waiting for a fix. |
|
@trancer1994 I don't know what is your define of accessibility, but accessibility means if there is a button or item, it is labled, and it is reachable. The controles are properly usable by keyboard and screen readers. This means accessibility for blind users. And we have another accessibility, for paralel users. The users that can't use their hands correctly, or they only have one hand, windows has a feature for them, called stikky keys. If they turned on this feature, it is then possible for them to press multiple kee presses for them. They can lock the keys with one hand and other keys, so they can press the locked keys together. This means accessibility for all groupe of users and this is the meaning of accessibility and what you are saying here is not something related to accessibility. |
|
@hwangsihu You can also close this as well. It has no point in it. We've talked over everything and no point is remaning anymore here. |
|
@bear101 what do you think? and amir, the sticky keys you are talking about are not a feature of TeamTalk, they are a feature of the Windows OS itself. So even if users with one hand or one hand not working correctly or whatever were to be able to use it, it would only be as part of using Windows, and not as part of TeamTalk. Sticky keys works on TeamTalk, there's just no equivalent built-in. |
|
@trancer1994 stikki keys is feature of windows, and it can be used in any app if activated, inclooding teamtalk. And, i'm saying this again. Teamtalk is, accessible. Anyone, with any type of disability support, can use teamtalk. With keyboard, touch, screen readers and stikky keys feature. Teamtalk's dialogs are accessible like windows itself. For example, in file explorer, it has tree views, lists, tab controles, everything. We'll just close this issue because i see nowhere point in it and what it even wants. |
|
The misunderstanding here is that AAC accessibility is not the same as blind accessibility or motor‑impairment accessibility.
TeamTalk is accessible for blind users — labelled controls, keyboard reachability, and screen reader support are all good. Sticky keys also help users who need multi‑key shortcuts.
AAC accessibility, however — which is what this issue is about — is a completely different domain with different constraints. Blind users can use keyboards, screen readers, hierarchical trees, dynamic lists, and multi‑pane dialogs as long as they are labelled and reachable. Sticky keys can also help users who need assistance with modifier keys.
AAC users, by contrast, often cannot use hierarchical trees, dynamic lists where items move, multi‑pane layouts, controls that require spatial memory, multi‑step activation patterns, multi‑key shortcuts or standard Windows dialogs, and instead require stable, fixed‑position grids, predictable focus order, no dynamic reordering of UI elements, no hierarchical structures, single‑action activation, low cognitive load and flat interfaces
These constraints described above come from established AAC UI design principles that are used in dedicated AAC communication systems such as Proloquo, Tobii Dynavox Snap/Core First, PRC‑Saltillo LAMP Words for Life, Grid, and similar apps.
These apps are not “accessibility features” like sticky keys or screen readers. They are full communication systems used by people who cannot rely on speech, typing, or standard computer interfaces. They are medically‑prescribed assistive communication tools, and not just UI preferences.
AAC users often cannot type, cannot use multi‑key shortcuts, cannot operate tree views, cannot navigate dynamic lists, and cannot use multi‑pane Windows dialogs. Sticky keys and keyboard accessibility may address the needs of blind users, but they do not address the needs of AAC users.
So the issue is not about blind accessibility or sticky keys. It is about AAC accessibility, which is a separate discipline with different requirements.
…________________________________
From: Amir ***@***.***>
Sent: Friday, July 31, 2026 16:28
To: BearWare/TeamTalk5 ***@***.***>
Cc: trancer1994 ***@***.***>; Mention ***@***.***>
Subject: Re: [BearWare/TeamTalk5] Proposal: AAC‑Native Replacement of the TeamTalk User Interface and UI Architecture (Issue #3077)
[https://avatars.githubusercontent.com/u/69115921?s=20&v=4]amirmahdifard left a comment (BearWare/TeamTalk5#3077)<#3077 (comment)>
@trancer1994<https://github.com/trancer1994> stikki keys is feature of windows, and it can be used in any app if activated, inclooding teamtalk. And, i'm saying this again. Teamtalk is, accessible. Anyone, with any type of disability support, can use teamtalk. With keyboard, touch, screen readers and stikky keys feature. Teamtalk's dialogs are accessible like windows itself. For example, in file explorer, it has tree views, lists, tab controles, everything. We'll just close this issue because i see nowhere point in it and what it even wants.
—
Reply to this email directly, view it on GitHub<#3077?email_source=notifications&email_token=AMV3XJV4HNJZHUEZUZ6SQOT5HS3KJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJUGQ2TQMZVGE22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5144583515>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMV3XJXLMFTOUU2Y24EUGAL5HS3KJAVCNFSNUABEKJSXA33TNF2G64TZHMZDCNZQGY2DKMZ3JFZXG5LFHMZTONZZGU3TONJRG2QXMAQ>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AMV3XJXKA6RIUFBF7JRQ47T5HS3KJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJUGQ2TQMZVGE22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/AMV3XJVNC6ZYMFU3HSSBZ735HS3KJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJUGQ2TQMZVGE22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today!
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
@trancer1994 Can we see anything like this in any of standard windows dialogs? |
|
You asked whether any of the AAC UI principles I described can be seen in standard Windows dialogs.
The answer is no, and that's exactly the point.
Standard Windows dialogs are not designed for AAC users. They are designed for sighted keyboard users, blind screen‑reader users, and general‑purpose interaction. AAC users cannot operate standard Windows dialogs, hierarchical trees, dynamic lists, or multi‑pane layouts.
That is why dedicated AAC communication systems exist, to cater for those users. Systems like Proloquo, Tobii Dynavox Snap/Core First, PRC‑Saltillo LAMP Words for Life, Grid, etc, are medically‑prescribed communication tools for people who cannot rely on speech, typing, or standard computer interfaces.
Their interfaces look nothing like Windows dialogs because AAC users need stable, fixed‑position grids, predictable focus order, no dynamic reordering of UI elements, no hierarchical structures, single‑action activation, low cognitive load and flat interfaces, none of which Windows has or can cater for out-of-the-box. Dedicated AAC systems are not “accessibility features” like sticky keys or screen readers. They are full communication systems built for users who cannot type, cannot use multi‑key shortcuts, cannot navigate tree views, and cannot operate standard Windows UI patterns.
So when you ask “why don’t Windows dialogs look like AAC interfaces?”, the answer is that windows dialogs are simply not designed for AAC users, as a matter of principle and design. But AAC interfaces are.
That is the entire reason I'm building an AAC-native replacement for TeamTalk's UI, because I'm trying to fill that gap and fulfill a need, and because AAC users cannot operate the standard interface.
…________________________________
From: Amir ***@***.***>
Sent: Friday, July 31, 2026 18:53
To: BearWare/TeamTalk5 ***@***.***>
Cc: trancer1994 ***@***.***>; Mention ***@***.***>
Subject: Re: [BearWare/TeamTalk5] Proposal: AAC‑Native Replacement of the TeamTalk User Interface and UI Architecture (Issue #3077)
[https://avatars.githubusercontent.com/u/69115921?s=20&v=4]amirmahdifard left a comment (BearWare/TeamTalk5#3077)<#3077 (comment)>
@trancer1994<https://github.com/trancer1994> Can we see anything like this in any of standard windows dialogs?
Idk. I'll just stop here because I don't know what are you trying to reach. But I think that this issue is also like the other one where you suggested the removal of push to talk feature which would not make anyone happy🤣
—
Reply to this email directly, view it on GitHub<#3077?email_source=notifications&email_token=AMV3XJQYXFS354HUBCOCCZL5HTMLBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJUGU4TCNRXG4Z2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5145916773>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMV3XJTSYF4GYMXMVGKE56L5HTMLBAVCNFSNUABEKJSXA33TNF2G64TZHMZDCNZQGY2DKMZ3JFZXG5LFHMZTONZZGU3TONJRG2QXMAQ>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AMV3XJXDLF5LPPJ7G5RUX4T5HTMLBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJUGU4TCNRXG4Z2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/AMV3XJXLBCZNBHTAVNKYWGT5HTMLBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMJUGU4TCNRXG4Z2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today!
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
TL;DR
TeamTalk’s current UI architecture (modal dialogs, hierarchical tree navigation, implicit boolean state, UI‑driven backend calls, scattered rendering logic) cannot be adapted to meet modern accessibility requirements — especially for AAC users and blind users.
This proposal introduces a replacement UI subsystem built on:
•
a UI‑agnostic state machine
•
non‑modal, panel‑based layout
•
flat navigation
•
explicit state signalling
•
asynchronous event model
•
a single rendering entry point
This is not a redesign.
It is a replacement UI that corrects structural limitations in the current architecture.
What is AAC?
AAC (Augmentative and Alternative Communication) refers to communication systems used by people with speech, motor, or cognitive impairments.
AAC‑native UI design requires:
•
predictable layouts
•
non‑modal flows
•
single‑action interactions
•
explicit state signalling
•
symbol‑first controls
•
minimal navigation depth
These requirements have direct architectural implications for UI design.
The current TeamTalk UI is fundamentally incompatible with AAC‑native interaction patterns.
The core issues are structural:
•
modal dialogs block interaction
•
hierarchical tree navigation requires multi‑step exploration
•
implicit state cannot support explicit AAC signalling
•
UI and backend are tightly coupled
•
rendering logic is scattered across widgets
•
workflows are synchronous and blocking
•
accessibility is bolted on, not designed in
A replacement UI is required.
2.1 Modal dialogs cannot be adapted
Modal dialogs block the event loop, interrupt workflows, and break spatial continuity.
AAC‑native design requires persistent, non‑modal panels.
2.2 Tree navigation cannot be adapted
The hierarchical QTreeView is incompatible with AAC scanning and screen‑reader predictability.
AAC‑native design requires flat navigation.
2.3 Implicit boolean state cannot support explicit signalling
AAC workflows require explicit named states, transitional states, and error states.
The current UI uses implicit booleans.
2.4 UI‑driven backend calls prevent accessibility guarantees
AAC‑native design requires an event‑driven architecture mediated by a state machine.
2.5 Scattered rendering logic cannot be centralized
AAC‑native design requires a single rendering entry point.
Below are linear, screen‑reader‑safe diagrams describing the current UI architecture.
3.1 Current Component Architecture
TeamTalk UI Layer
→ MainWindow
→ QTreeView (channels)
→ QDialog (connection, configuration, errors)
→ menu bar
→ tool bar
→ QAction handlers
Backend Logic
→ Client
→ Channel model
→ User model
→ Audio engine
Network Layer
→ TCP and UDP sockets
→ protocol handlers
Key characteristics
→ UI directly manipulates backend
→ modal dialogs block the event loop
→ state is implicit
→ hierarchical navigation is embedded in widgets
3.2 Current Connection Flow
User triggers Connect
→ MainWindow opens modal ConnectDialog
→ ConnectDialog blocks event loop
→ ConnectDialog calls Client::connect
→ backend updates state
→ UI updates via Qt signals
3.3 Current Channel Navigation
User navigates hierarchical tree
→ expand server
→ expand root channel
→ expand subchannels
→ activate leaf node
→ UI calls Client::joinChannel
→ icons update
3.4 Current State Model
connected (boolean)
transmitting (boolean)
muted (boolean)
currentChannel (object)
No explicit transitional states.
No error states.
No unified state machine.
4.1 Component Architecture
AACUserInterface
→ StatePanel
→ ActionPanel
→ FlatChannelList
→ AccessibilityLayer
→ AACUserInterface::render
→ AACUserInterface::onAction
UIStateMachine
→ ConnectionState
→ ChannelState
→ TransmitState
→ MuteState
→ ErrorState
→ UIStateMachine::update
→ UIStateMachine::subscribe
Backend
→ Client::connectAsync
→ Client::joinChannelAsync
4.2 Replacement Connection Flow
User activates Connect
→ AACUserInterface sends CONNECT
→ UIStateMachine enters Connecting
→ UIStateMachine calls Client::connectAsync
→ backend reports success or failure
→ UIStateMachine updates state
→ AACUserInterface::render updates UI
4.3 Replacement Channel Navigation
User selects channel in FlatChannelList
→ AACUserInterface sends JOIN_CHANNEL
→ UIStateMachine enters Joining
→ UIStateMachine calls Client::joinChannelAsync
→ backend reports result
→ UIStateMachine updates state
→ AACUserInterface::render updates UI
4.4 Replacement State Model
Disconnected
→ Connecting
→ Connected
→ Joining
→ Joined
→ Error
Transitions are explicit and deterministic.
The replacement UI uses three persistent, non‑moving panels:
5.1 Layout Diagram
AACUserInterface
→ StatePanel (top)
→ ActionPanel (middle)
→ FlatChannelList (bottom)
Panels never move.
Only content changes.
5.2 StatePanel
Displays:
→ connection state
→ channel state
→ transmit state
→ mute state
→ error state
5.3 ActionPanel
Displays context‑aware actions:
→ Connect
→ Join Channel
→ Speak
→ Mute
→ Leave Channel
→ Retry
All actions are single‑tap.
5.4 FlatChannelList
Flat list of channels:
→ “General Chat, 12 users”
→ “Music Room, 4 users”
→ “AFK, 1 user”
No hierarchy.
No expand/collapse.
No icon‑only information.
The replacement UI:
•
removes modal dialogs
•
removes hierarchical navigation
•
removes implicit state
•
removes UI‑driven backend calls
•
removes scattered rendering logic
And replaces them with:
•
non‑modal panels
•
flat navigation
•
explicit state machine
•
event‑driven backend interaction
•
single rendering entry point
Phase 1 — Introduce UIStateMachine
No UI changes yet.
Phase 2 — Implement AACUserInterface
Behind a feature flag.
Phase 3 — Parallel Operation
Old UI and new UI run side‑by‑side.
Phase 4 — Deprecate Old UI
Remove modal dialogs and QTreeView.
Phase 5 — Remove Old UI
Replacement UI becomes default.
•
Maintainers may resist large changes
→ mitigated by feature flags and parallel operation
•
Backend assumptions may depend on old UI
→ mitigated by UIStateMachine mediation
•
Accessibility requirements may increase complexity
→ mitigated by centralized AccessibilityLayer
•
Simplicity may be misinterpreted as lack of power
→ advanced features can be added as panels
What is AAC?
AAC stands for Augmentative and Alternative Communication.
It refers to communication systems used by people with speech, motor, or cognitive impairments.
Why does AAC matter for UI architecture?
AAC users rely on:
→ predictable layouts
→ minimal navigation depth
→ non‑modal flows
→ single‑action interactions
→ explicit state signalling
→ symbol‑first controls
These requirements cannot be met by the current UI architecture.
Why does the current interface break accessibility?
Because it uses:
→ modal dialogs
→ hierarchical tree navigation
→ icon‑based state signalling
→ implicit boolean state
→ scattered rendering logic
These patterns break:
→ AAC scanning
→ screen‑reader predictability
→ motor‑limited workflows
→ cognitive accessibility
Why can’t we just patch the existing UI?
Because the issues are architectural, not cosmetic.
Does this remove features?
No.
All existing functionality remains available.
Does this change the backend?
No.
Only the UI and event model change.
Is this a redesign?
No.
This is a replacement UI subsystem.
AAC‑native design is not a theme or a visual style.
It is a structural requirement that affects:
•
navigation
•
state management
•
event flow
•
rendering
•
error handling
•
layout stability
AAC users rely on:
Panels must never move.
Modal dialogs break this.
AAC scanning cannot handle modal interruptions.
Hierarchical trees require multi‑step navigation.
Implicit booleans cannot express transitional or error states.
Scattered rendering logic produces inconsistent output.
UI‑driven backend calls create unpredictable state transitions.
Because these requirements are structural, they cannot be retrofitted into the existing UI.
They require a replacement UI architecture.
Implement UIStateMachine
2.
Implement AACUserInterface
3.
Integrate AccessibilityLayer
4.
Run both UIs in parallel
5.
Deprecate old UI
6.
Remove old UI
7.
Finalize replacement UI
12. Closing Statement
This proposal replaces the existing TeamTalk UI with a modern, state‑driven, AAC‑native interface that is:
•
accessible
•
maintainable
•
predictable
•
future‑proof
•
architecturally sound
It positions TeamTalk for the next decade of inclusive communication.
All reactions