Hello everyone,
I've developed a native TeamTalk client for macOS that's fully accessible with VoiceOver. As you know, the official TeamTalk version on Mac is completely inaccessible, so I built an alternative from scratch.
What's included:
- Full keyboard navigation β Cmd+1/2/3/4 for UI areas, F5 for nickname, F6 for status, etc.
- VoiceOver announcements for all events (users joining/leaving, private messages, file transfers)
- Native macOS interface (no ugly web wrapper)
- Saved server management with quick access
- Browse and join channels with optional password protection
- Private messaging with full conversation history
- File sharing with visual progress indicators
- User administration (for server admins)
- Advanced microphone settings:
- Enable/disable audio processing
- Noise suppression (Noise Gate) or Expander with fine-tuned controls over threshold, attack, hold, and release
- Peak limiter with auto or manual mode
- Multiple presets for different use cases
- Professional-grade tools to eliminate feedback and control voice peaks
Current state:
The app is functional and ready to use. The interface is clean, accessible and looks good β because using VoiceOver doesn't mean the UI has to be ugly.
Important:
The app is unsigned (no budget for Apple Developer Program yet). You'll need to authorize it in macOS security settings.
Interested?
If anyone wants to test, I can set up a beta distribution system. Your feedback on features, keyboard shortcuts, or missing functionality is welcome!
Comments
Teamtalk is accessible.
Last I tried it... Which was a good year ago I admit, teamtalk worked perfectly fine , if a bit convolutedly, what does your client offer that the official client does not?
very interested to give it a shot
Hi, I think having a 100% native mac client for teamtalk isn't at all a bad thing. Sure the qt app does exist, but I've been told by several mac users that unless you own a macbook with a screen, then you'll have big problems with it glitching severely, for example on the mac mini.
I do not have my mac yet, but I've ordered one and I'm most definitely interested in testing this client.
Edit: Would you consider also making it available on iOS? There is a native iOS app but frankly it's looking more and more like it's not being worked on, for one thing... Still stuck on 5.19, and ever since iOS 26 came out, it's broken so badly for me that it's unusable. My microphone simply stopped working and will never work, not even 1 or 2 seconds despite showing as if it does in both the status bar and in teamtalk itself. Also the dev doesn't really seem to know what he's talking about, as he claims that apple does not let you access the files app to retrieve .tt files from, so you can't even just use a .tt file unless you send it via email. Meh.
Definitely will try this
As said above, the QT MacOS client suffers from issues for years now that have not been solved: conversation history has some caevats when browsing (either when using lists or plain text view), audio input produces saturation at high volume, and TTS announcements is also sometimes sluggish.
I'll definitely try this pure swift version when it will come out, as native apps are often better for accessibility, and lighter to use.
Re: Accessibility, macOS support and future iOS plans
Hey everyone, thanks so much for the interest and feedback! Really appreciate it.
@jim pickens β You're right that the Qt app technically works, but honestly it's pretty rough for accessibility. Navigating between channels and users is basically a nightmare with VoiceOver, context menus don't respond properly, and there's that annoying audio crackling that I managed to eliminate in my version. So yeah, it "works" but it's not really usable if you rely on screen readers. This native macOS client is built VoiceOver-first, so the experience should be night and day.
@Casey Reeves β Totally feel you on the Mac mini issues. And yeah, iOS would be amazing! But here's the reality: I need to get an Apple Developer subscription first to sign the macOS app (costs money), and then building an iOS version would require the same. Down the road though, if I do make an iOS version, it would be way better than the official one β full
.ttfile support and iCloud sync between Mac and iOS so your servers stay in sync across devices. One step at a time though! Can't wait to hear what you think once your Mac arrives.@kaillewaille β Exactly! Those Qt issues are exactly what I was trying to fix. The navigation between channels/users for accessibility is broken, context menus don't work with VoiceOver, and yeah, that audio crackling is gone in my version. The audio pipeline is custom using Apple's AudioQueue, so no more distortion or saturation problems. And all the TTS is direct VoiceOver calls, so way more responsive. Looking forward to your feedback!
Let me know if you have any other questions. Excited to get this in people's hands!
definitely interested
I am definitely interested.
The native app is barely usable, and I'd be very happy to finally have a natively accessible and fully functional macos client.
TTAccessible Beta 1
Hi everyone, thanks for the great feedback on my earlier post! I'm happy to share the first public beta.
Download
ttaccessible-1.0.0-beta.1-1.zip (16 MB)
Important: Unsigned App
This app is not signed with an Apple Developer certificate (no budget for the $99/year program yet). macOS will block it by default. Here's how to open it with VoiceOver:
ttaccessible.appto your/Applicationsfolder (Finder, Cmd+Shift+A to open Applications, then paste)You only need to do this once. After that, the app opens normally.
Importing your servers from the official TeamTalk client
If you already use TeamTalk on your Mac, you can import all your saved servers:
TeamTalk5.inifileTeamTalk5.iniin the file list, select it, then press Enter (or activate the Import button)All your servers, nicknames, and credentials will be imported. Duplicates are automatically skipped.
What's in this beta
Keyboard shortcuts (quick reference)
Known limitations
Feedback
I'd love to hear your feedback! Let me know: - Anything that doesn't work as expected - VoiceOver issues or confusing navigation - Features you'd like to see - Keyboard shortcuts that feel wrong
Looking forward to hearing from you all!
Re: Accessibility, macOS support and future iOS plans
No worries, I understand. I just thought that mentioning iOS couldn't hurt given the state of things over there as well.
The good news is, I've just received confirmation that my mac will arrive tomorrow, so, unless there are many issues with setting it up, I should be all good to go to try this out in a matter of days, maybe weeks. I'm a very fast learner indeed, which will come in very handy for my initial switch to a mac.
Giving this a try, but one thing already.
This looks great, but one thing if possible is the ability to import TT files.
thank you for developing this app!
TTAccessible Beta 2
Hi everyone,
Here is beta 2 of TTAccessible.
First, thank you again for all the feedback on beta 1. It helped a lot, and this release includes quite a few improvements based directly on testing and user reports.
Download
ttaccessible-20260319-beta2.zip
Important: Unsigned App
This app is still not signed with an Apple Developer certificate, so macOS may block it the first time you try to open it.
If you already opened beta 1 using Open Anyway, beta 2 should normally be easier to launch, but if macOS blocks it again, use the same process as before in System Settings > Privacy & Security.
Whatβs new in beta 2
.ttfilesA few notes
TTAccessible is still designed with the same goals as before:
What Iβd especially like feedback on in this beta
.ttfilesKnown limitations
Thanks again to everyone testing this. Your feedback is genuinely helping shape the app.
first impressions
Okay, serious, this is an absolutely awesome app. I couldn't find one option I'd definitely require but maybe I just missed it? Echo cancelation and all that fancy stuff to avoid feedback when on speakers and accidentally spamming everyone with VO. But other than that? Just wow. This app is really amazing.
Sadly unable to test, but
I'm sadly unable to test this, as I don't have a mac with an m-series chip. If I get one, however, and once this app is out of beta, I'll be giving it a look for sure. The QT teamtalk client for mac makes me rather sad. I despise being sad.
This is really, really good so far
This is really, really good so far. The QT client had been pretty good, but i've noticed in later versions of it, since version 5.19 of it maybe, , that it's extremely tricky if not impossible to get keyboard focus into lists, such as the channels list on a server your list of saved servers, etc, so you can do anything with it, such as select a server to connect to etc, and context menus never worked properly either, so that was always frustrating in the QT client. So it's really good that this accessible alternative is being developed now. One thing I noticed, when adding a user account, on the rights tab, I'm getting the list of rights, in French, and I'm using Mac OS in English here. I could understand it however, being in Canada, and knowing French as well, but for those that don't, that may be confusing. This app is really awesome so far, and so nice, to not to have to battle with the inaccessibilities that the QT app has. Looking forward to further betas, and improvements.
devices problems
Just wanted to drop in a quick note here and feedback: it is currently impossible for me at least to switfch from my airpods or any connected wired headphones in the client, even if I select the button to refresh devices. They simply do not show up in the list. I have to completely restart the client.
So I guess that might be a little bug?
Beta feedback: echo cancellation, localization, and dev
Thanks again everyone for the testing and the feedback, it really helps.
@Casey Reeves β For echo cancellation, I did try the built-in macOS solution, but Iβm not really satisfied with it. Because of that, Iβll probably move back to TeamTalkβs own echo cancellation, which I think will work better for this app.
About the AirPods and other external devices: I hadnβt properly tested that case yet, so that one is on me, sorry. Iβll fix it, and a new beta should be out soon.
@Dan Eickmeier β Thanks for pointing out the French text in the rights list. Iβm French myself, so I probably forgot a translation there. Iβll clean that up in the next beta.
Also, an updater is planned, but not for immediately. I still need to sign the app first before I can do that properly.
Thanks again to all of you for trying this out and taking the time to post feedback.
yes!!!
Count me in. Let's do this! Super excited!
TeamTalk accessible app...
Funnyly I just started building an alternitive to team talk that offers lots of features built-in I've seen people hack together through team TALK servers, but am so happy someone is doing an accessible app. I just got my appple dev account in early March so can and am happy to help with the intel SUPPORT AND SIGNING if you like. This mac is INTEL...... :( Oh i wish I had a Neo or Pro macbook m5!
API CAUST
HOW MUCH DOES THE DEV CHARGE FOR API SUPPORT? LAST I SAW IT WAS LIKE A GRAND OR TWO... I WANTED FULL SUPPORT WHEN I LOOKED AS I WANTED TO UPSCALE LATER IF NEEDED RIGHT AWAY VS. STOPPING AT SOME LEVEL THEN HAVING TO UPGRADE LATER, ITS LIKE 100 SOMETHING FOR CLIENT SUPPORT RIGHT? SO COOL DUDE. GRATE!
Small development update: TTAccessible is temporarily p
Hi everyone,
Just a quick update to let you know that development of TTAccessible is temporarily on pause.
I had put my iMac up for sale a while ago, without really expecting it to sell this soon, but it finally did. Since that was the machine I was using to develop the app, I do not currently have my usual setup anymore.
I still have my MacBook Air, but it is not really enough for this kind of work, especially because of disk space, and to some extent performance as well. So for the moment, continuing development properly is a bit difficult.
The good news is that I have ordered a new, more powerful Mac, and I should receive it sometime in mid-April. As soon as it arrives, Iβll get everything set up again and resume work on the app.
Sorry for the interruption, and thank you for your patience. Iβll be back with more news soon.
Re: TeamTalk licensing and other o
Hi Dominique,
Thanks for your messages, and also for the offer to help with signing and possible Intel support β I really appreciate it.
I checked the TeamTalk SDK licensing more closely, and if that paid SDK license is really required to distribute an app like this, then I probably wonβt continue with TeamTalk.
Itβs simply too expensive for me for a project like this.
What threw me off is that I was able to compile the dylib directly from the public GitHub source and get it working, so I didnβt immediately realize there might still be separate licensing terms for distributing an end-user app. That part is still a bit unclear to me.
If that license really is required, Iβd rather move on and build something around a different server or platform instead, if thereβs enough interest.
But thank you again for the clarification and for your offer to help.
TT
As far as I know, TT is partially open-source. The client is, but the server isn't, which makes absolutely no sense. The developer is charging for the Pro Server and SDK, though as far as I know, the license isn't actually enforced, and I wouldn't pay for it anyway. I run a TT Pro server for free because you can grab it from the website and go, though I'm planning on ditching the entire system and moving to Discord by October. I'm not sure how good the encryption really is, and it still saves all server settings including user account data in a plain text xml file.
The developer doesn't seem to care about the project which is really sad, because it has a lot of interesting features.
I'd recommend putting your effort into something else like Mumble which is as far as I know completely open-source. You could enhance it by adding stereo audio support, a web client, making the QT clients more accessible and/or developing more accessible clients in general, etc.
Re: tt
Hi Chris,
Thanks for the reply.
Yes, to be honest, the licensing situation really puts me off, but so does the general direction of the project and the developerβs attitude around it.
Right now TeamTalk is still the only thing I personally use in this space, so thatβs why I started working on this in the first place. But if there is something better to build on, or a better direction to move toward, Iβd absolutely rather go elsewhere.
Mumble or another more open platform may well make more sense in the long run.
For now the project is paused anyway until I get my setup back, but Iβm definitely thinking about all of this more seriously now.
Thanks again for the suggestion.
sdk and license
Yeah I agree with y'all this guy is clearly abusive in pricing. 990 euros for a standard license is just stealing.
I'm really going to be disapointed if TTAccessible ends up not continuing because mumble and other similar platforms also have such shortcomings, and teamtalk is much easier to configure, I'll give them at least that. I don't even think other servers let you use stereo sound or play media files.
Forget teamspeak
I tried the ts 3 client on windows, it's very bad. And the ts6 is slightly less worse but it's electron (whyyy!?) and unlike discord is not accessible at all. So mumble is the only thing left it seems.
Yeah, tt is not taken seriously at all and I think it's more of an abnormal thing of why random blind people are sticking to it til this day...
I say continue with this if you can
I am using it right now, and yes I'm really liking it, I mean it's like TeamTalk Classic but for Mac.
sdk and license
I just also realized that would not be the first time someone goes against the license. The very first thing you see when you launch TTMediaBot is teamtalk sdk in trial mode. Just saying.
I'm not a lawyer by any means of course, but if you make it stupidly and deliberately easy to not have to buy an overpriced license and use it indefinitely, who am I to argue?
Please keep going
Please keep going if possible. If help is needed I'm sure we can figure something out! Are you on Github with your repository for contributers?
just downloaded it
Wow! This is fantastic so far. Currently on a server now as we speak. One thing that should be fixed is labeling for the sliders in the channel.
question regarding sound packs
Does the app support custom sound packs?
500 internal server error
Hi How are yall doing? i tried to download this cliant and i got an internal server error.
500 internal server error
Hi How are yall doing? i tried to download this cliant and i got an internal server error.
And applevis
didn't like this 500 so much it reposted it twice lol.
TTAccessible Beta 3 coming soon β Development update
Hi everyone,
Sorry for the silence β I'm back! Quick update on where things stand.
First, about the download issue some of you ran into: the 500 error was a temporary problem on pCloud's side, not on ours. The beta 2 download link should be working again now. If it's still giving you trouble, let me know and I'll re-upload it.
As I mentioned in my last post, I had sold my iMac and was waiting for a replacement. Good news: my new Mac arrived and I've been back to work on TTAccessible for a little while now. A beta 3 is on the way with some significant improvements.
What's new in the upcoming beta 3
Answers to questions I missed
@Matthew Whitaker β Custom sound packs are not supported yet, but it's on my list. About the slider labels in the channel view, they should already have VoiceOver labels (input gain, output gain, volume). If something specific is still unlabeled, let me know exactly which control and I'll fix it.
@ericwhittencool β The 500 error should be resolved now. Try the link again and let me know if it works.
Thanks again to everyone testing and giving feedback. It really makes a difference. Beta 3 should be out very soon β stay tuned!
TTAccessible Beta 3
Hi everyone,
Beta 3 is here! Thanks again for all the feedback β it keeps making the app better.
Download ttaccessible-1.0.0-beta.3-1.zip (17 MB)
What's new in beta 3
Installation reminder
Same as before β the app is still unsigned. If you already opened a previous beta using "Open Anyway", beta 3 should launch without issues. If macOS blocks it, use the same process in System Settings > Privacy & Security.
Feedback welcome
Let me know how echo cancellation works for you, especially if you use speakers with VoiceOver. And as always, any bugs, VoiceOver issues, or feature requests are welcome.
Thanks everyone!
Some things
A few suggestions on what to add if you don't mind.
Can you make it so cmd shift m mutes and unmutes the user locally, just like how it is on the qt client, as well as cmd m to mute/unmute master volume.
And can you make the dialog where you adjust a user's specific volume to change it in real time as you adjust it, and add a hotkey to that, cmd u perhaps?
Thanks for the work on this app.
Some things
A few suggestions on what to add if you don't mind.
Can you make it so cmd shift m mutes and unmutes the user locally, just like how it is on the qt client, as well as cmd m to mute/unmute master volume.
And can you make the dialog where you adjust a user's specific volume to change it in real time as you adjust it, and add a hotkey to that, cmd u perhaps?
Thanks for the work on this app.
One other thing.
Unless I'm missing something, I don't think there is a way on here to move put someone on your left or right like you can in the Original TeamtTalk. Great App!
Re: One other thing. Bookmark
If that is to be implemented, I think it should also go in the user adjust volume dialog, 2 checkboxes to mute left or right channel of the user.
TTAccessible Beta 4
Hi everyone,
Beta 4 is here! This one is packed with new features, many of them directly based on your feedback. Thank you all for testing and reporting.
Download: ttaccessible-1.0.0-beta.4-1.zip (17 MB)
What's new in beta 4
User audio controls
Recording
Channel operator
Hear myself
Kick from server
Custom sound packs
Per-event sound toggle
Preferences reorganization
Bug fixes and stability
New keyboard shortcuts (quick reference)
Installation reminder: Same as before, the app is still unsigned. If macOS blocks it, use System Settings > Privacy & Security > Open Anyway.
Feedback welcome: Let me know how the new features work for you, especially recording and the sound packs. And as always, any bugs, VoiceOver issues, or feature requests are welcome.
Thanks everyone!
This is quickly becoming my main TT client on Mac
Hey, I have another suggestion to make.
Can you make it so server events announced by Mac OS TTS here in my case, are customizable, right now they're all grouped into "TeamTalk history". I want to be able to for example, only announce people logging in and out and joining the channel I'm in, and maybe read channel messages.
user accounts and passwords
Say if someone wants to know their password to their user account., How would you go about finding that?
Specifying whether a channel is stereo or not?
I noticed when creating a channel, at this time, that you can't specify whether the channel is stereo, or not? So I'm assuming that when a channel is created, that it is mono? Or is it a stereo channel?
Re: Beta 4 feedback β all three points addressed in next beta
Hi everyone, thanks for the continued feedback!
@Johann β You're right, event announcements are currently grouped together which doesn't give you enough control. In the next beta, I'll add per-event customization so you can choose exactly which events get announced (logins/logouts, channel joins/leaves, messages, etc.) separately. That way you can keep what matters to you and silence the rest.
@ericwhittencool β Good question. Right now the app doesn't show account passwords when viewing user accounts, but it should β the server does provide them to admins. I'll fix that in the next beta so passwords are visible in the user accounts list and edit form, just like in the original TeamTalk client.
@Dan Eickmeier β Currently when you create a channel, the audio codec settings (including stereo/mono) are inherited from the parent channel automatically, and there's no UI to change them. I'll add codec configuration to the channel creation and editing dialogs in the next beta, so you'll be able to choose between mono and stereo, and adjust other codec settings like bitrate and sample rate.
Stay tuned for beta 5!
File/messages windows keep randomly openning.
I have noticed this a lot after for example, downloading a file or sending a pm, when closing the pm window with command w, it just opens the window again for no reason, I haven't received any new pm. Same with the files window.
Also, when recording, can you make it so it remembers recording state, just like in the qt client where if you had it set to record it'll automatically start when you enter a channel.
still issues with audio, somehow
Hi!
First, let me say that beta 3 and 4 were simply amazing work. They work really, really well.
However there are still a couple of issues that I can find with audio. For one thing, the echo cancellation stuff does not seem to be very effective. VoiceOver is still perfectly audible for others, and others still hear themselves, even if a bit less loudly.
Second thing I noticed is that the audio devices stuff still seems to have rough edges. Even if I use the button to refresh devices and see if it can detect new devices, it does not. I can't switch to my airpods pro 2 at all without restarting the client. On top of that, refreshing devices somehow cause the audio input to simply stop working, or so it appears. Noone can hear me until I restart the app.
HTH
Bug fixes, recording auto-restart, and echo cancellation
Hi everyone, quick update.
@Johann β Both issues you reported are fixed. The PM and Files windows will no longer reopen after you close them with Cmd+W. For recording, I've added an option in Preferences > Recording: "Automatically restart recording when joining a channel". When enabled, if you had recording active, it will automatically restart when you join or change channels, even after reconnecting. It's off by default so you can choose whether you want that behavior.
@Casey β Thanks for the detailed feedback on audio.
For the device switching issue (AirPods not detected, audio input stopping after refresh), that will be fixed in the next beta.
About echo cancellation: I have a question for you. On macOS, is VoiceOver actually attenuated when using the Qt TeamTalk client? On iOS VoiceOver is ducked automatically, but on macOS it works differently. I tried implementing Apple's native echo cancellation (Voice Processing IO), but it didn't attenuate anything, and on top of that it behaved like FaceTime β lowering the volume of all other apps. So I switched to WebRTC AEC3, which is the same engine used in Chrome and most VoIP apps. I don't think the Qt client on macOS actually attenuates VoiceOver either, so I'd like to understand what you're comparing against. Can you check whether VoiceOver is truly suppressed in the Qt client, or if it's audible there too?
TTAccessible Beta 5
Hi everyone, beta 5 is here! Lots of new features and bug fixes, many directly from your feedback. Thank you all.
Download: ttaccessible-1.0.0-beta.5-1.zip (17 MB)
What's new in beta 5
Per-event announcement customization
You can now choose exactly which events get announced. Go to Preferences > Announcements and expand "Announce system history" β you'll find individual toggles grouped by category: Connection, User Presence, Moderation, Status, Subscriptions, and Files. Enable All / Disable All buttons are included. This affects both foreground VoiceOver and background TTS/notifications. (Requested by Johann)
Channel audio codec configuration
When creating or editing a channel (F7 / Shift+F7), you can now configure the Opus codec: mono or stereo, sample rate, bitrate (kbps), and application mode (VoIP or Music). On create, defaults are inherited from the parent channel. On edit, non-exposed settings (complexity, FEC, etc.) are preserved. (Requested by Dan)
User account passwords visible
Admins can now see user account passwords in the accounts list (new Password column) and in the edit form (plain text field, matching the Qt client). The TeamTalk server provides passwords to admins β the app was previously ignoring them. (Requested by ericwhittencool)
Clickable links in chat
URLs in channel and private messages are now automatically detected and displayed as clickable links. Click to open in your default browser. Plain text clicks still select the row normally.
Copy message
Right-click on any message in channel or private chat to copy its content.
Relative timestamps
New option in Preferences > General: "Use relative timestamps". When enabled, chat messages show "2 min ago" instead of "14:32".
Bug fixes
Recording auto-restart
New option in Preferences > Recording: "Automatically restart recording when joining a channel". When enabled, if recording was active, it will restart automatically when you join a new channel, reconnect, or relaunch the app. Off by default. (Requested by Johann)
Installation reminder
Same as before β the app is still unsigned. If macOS blocks it, use System Settings > Privacy & Security > Open Anyway.
Feedback welcome
Let me know how the new features work for you. And as always, any bugs, VoiceOver issues, or feature requests are welcome. Thanks everyone!
re: TT
Yeah pro is basically free at this point because licenses are not forced. I tried this a while back on my servers and they work perfectly. Not running pro because well, no point. Plus passwords is still stored in plain text and the dev is being a lazy ass and not giving a fuck. It's 2026 and in no point should shit like that be in plain texts. I don't care if people have access to your box or not because anyone can get info if they're admin of said server, one bad actor on said admin account and your server might as well be fucked! I've lost a lot of respect for TT and the dev as a whole because there is a lot of things that still have yet be made into reality. Coming from an IT guy, this is the main issue I have. IOS hasn't been worked on in months, and you still cannot share files nor create accounts, leaving third party devs having to do all the work when they shouldn't have to. It's disgusting! There's honestly way better more secure communication platforms out there but I will agree. The only, one and only thing that TT has going is their stereo high quality channels. That's it. Everything else is irrelevant!
With discord becoming impopular now
I hope soon / one day teamspeak can start taking accessibility seriously.
PS: the message above me is very true.
re: With discord becoming impopular now
Bro TS and their security is so secure it's not even funny and it makes TT security like true dog shit. Oh, wait, I mean, unsecure. I don't know if you know this about TS but the way that someone becomes an admin is through a generated encrypted privilege key and an existing admin has to generate that either from the account I think or through the server. Oh and the first time you setup the server, first admin gets a key too and if ya lose that privilege key, good luck getting it back. I've had that happen to me once and I think I had to generate myself a new one either that or I just didn't care. It's been so long sense I hosted a TS server
Woww
Well only mumble left then?
I've only tried it once and the qt inaccessibility was terrible on windows back in 2016 ish I think.
But I am surprized, I thought surely ts have an entire business model behind so it must be decent? At least security wise.