I am just testing @Jami with a #screenreader on both linux desktop and android for #accessibility.
Initial setup is accessible on both the platforms.
Listing conversations I can't really say as I only have single contact.
Audio calling is working fine. I am impressed that the call setup took just a moment. On android controls like microphone toggle, speaker / earpiece toggle and hangup button are working fine.
I am unable to find out in call controls with the keyboard on linux.
On both desktop and android I can write messages.
On android I can read messages, find and execute additional actions in the popup menu.
On the desktop I can't read incoming and outgoing messages with a screen reader. I haven't discovered on how to copy them.
In conclusion comparing this to the tox chat the Jami is more accessible with a screen reader. Perhaps I will be able to figure out how to handle the calls with a keyboard shortcuts however the fact message text is not readable with a screen reader on desktop linux and perhaps other platforms sounds dissapointing. The idea and decentralized nature of this communication app sounds really amazing.
reshared this
Peter Vágner
in reply to Peter Vágner • •The desktop app uses QT6 for the UI. Apart of some ounlabelled buttons such as Accept / Reject incoming call and some tab controls on the main window most of the UI elements are clearly labelled and accessible from the keyboard.
The desktop app has a keyboard shortcuts button on the main screen which opens a tabbed dialog with accessible lists of keyboard shortcuts. I haven't yet discovered if these can be tweaked but the default ones are working well for me. For calls it's ctrl+y for accepting and ctrl+d for rejecting / hanging up. Letter m alone can be used for muting / unmuting the microphone.
I need to find out if there is a way to create global shortcuts or do some actions using commandline switches. If either of this turned out to be possible it would perfectly integrate with the desktop.
Sending and receiving files is something I'm going to try next.