AAC: Complete End‑to‑End Accessibility Pipeline (Prediction, Dwell, Scanning, Symbols, Categories, In‑Channel Integration)

[trancer1994]

Summary
This PR integrates the full AAC prediction and accessibility stack into the application.
Key Features
•
Fully wired AACMainScreen (prediction, dwell, reinforcement, ignore penalties)
•
Confidence‑coloured prediction bar
•
AACSymbolGridScreen + AACCategoryScreen
•
InChannelScreen AAC integration (speech + TeamTalk send)
•
MainWindow freeze/unfreeze for prediction stability
•
Symbol→text and category→symbol flows
•
Dwell reinforcement support
•
Scanning + large target support via AACScreenAdapter

Much more is coming.

[amirmahdifard]

@trancer1994 can you please explane whatts the point of this implimentation? accessibility of qt teamtalk is very fine already.

[trancer1994]

Thanks for the question — to clarify, this implementation isn’t intended to modify or improve the accessibility of the existing Qt TeamTalk client. The current Qt UI is indeed accessible for users who can operate a traditional widget‑based, higherarichal interface. But this PR is part of a complete AAC‑native replacement client, which does not use the Qt UI at all, instead replacing the entire existing user interface with an AAC‑specific one designed not only for normal TeamTalk users but also for those users who cannot type, cannot navigate hierarchical widgets, nested menues or trees, and cannot operate the standard interface at all even if it is fully screen‑reader accessible. And because this replacement is fully AAC‑native (see my proposal issue for an explanation of that), it requires its own communication pipeline inside TeamTalk to support AAC workflows (symbol grids, dwell selection, switch scanning, large static targets, etc.), and this PR provides the backend support that the AAC‑native client depends on. It does not affect the behaviour of the existing Qt client. Happy to clarify any architectural details if needed.

…

________________________________ From: Amir ***@***.***> Sent: Sunday, April 19, 2026 09:50 To: BearWare/TeamTalk5 ***@***.***> Cc: trancer1994 ***@***.***>; Mention ***@***.***> Subject: Re: [BearWare/TeamTalk5] AAC: Complete End‑to‑End Accessibility Pipeline (Prediction, Dwell, Scanning, Symbols, Categories, In‑Channel Integration) (PR #3111) [https://avatars.githubusercontent.com/u/69115921?s=20&v=4]amirmahdifard left a comment (BearWare/TeamTalk5#3111)<#3111?email_source=notifications&email_token=AMV3XJWARSUBG3S5ZE7FTVL4WSHNZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRXGU2TIMZWHEZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4275543692> @trancer1994<https://github.com/trancer1994> can you please explane whatts the point of this implimentation? accessibility of qt teamtalk is very fine already. — Reply to this email directly, view it on GitHub<#3111?email_source=notifications&email_token=AMV3XJWARSUBG3S5ZE7FTVL4WSHNZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMRXGU2TIMZWHEZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJNLQOJPWG33NNVSW45C7N5YGK3S7MNWGSY3L#issuecomment-4275543692>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMV3XJWMJPRKIZPOVVB5LRT4WSHNZAVCNFSM6AAAAACSYY4MGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENZVGU2DGNRZGI>. You are receiving this because you were mentioned.Message ID: ***@***.***>