You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following implementation of Qt Accessibility Announcement, and after some user tests, it seems notifications send using Qt Accessibility Announcement are real accessibility events, and not really messages without context. So, majority of screen readers ignore those notifications when TT is not in focus.
E.G., with NVDA on Windows or Voice Over on MacOS, enable Qt Accessibility Announcement in preferences, go to your desktop for example and ask someone to login to your server, no message will be read by screen reader. Now, go to TT's window and ask the person to log out, screen reader will read notification.
SO, finally, Qt Accessibility Announcement is not really a good solution for our TTS events.
I'll try to implement direct interactions with Voice Over (via Apple Script) and with Orca (using dBus).
I guess we can keep Qt Accessibility Announcement available as a backup in case it can be useful.
Application
qtTeamTalk
TeamTalkAndroid
iTeamTalk
TeamTalkServer
The text was updated successfully, but these errors were encountered:
yes please, do not remove qt accessibility announcement, I need it. Ad the thing that you want but don't remove qt accessibility announcement, at least on windows
Description
Following implementation of Qt Accessibility Announcement, and after some user tests, it seems notifications send using Qt Accessibility Announcement are real accessibility events, and not really messages without context. So, majority of screen readers ignore those notifications when TT is not in focus.
E.G., with NVDA on Windows or Voice Over on MacOS, enable Qt Accessibility Announcement in preferences, go to your desktop for example and ask someone to login to your server, no message will be read by screen reader. Now, go to TT's window and ask the person to log out, screen reader will read notification.
SO, finally, Qt Accessibility Announcement is not really a good solution for our TTS events.
I'll try to implement direct interactions with Voice Over (via Apple Script) and with Orca (using dBus).
I guess we can keep Qt Accessibility Announcement available as a backup in case it can be useful.
Application
The text was updated successfully, but these errors were encountered: