mastodon - Link to source
:boosts_ok_gay:​Help with Linux Screenreaders

For better accessibility testing of the software I build, I've started testing more with screen readers.

On Android, enabling and using TalkBack is relatively straightforward, but for testing on my desktop, Orca is completely unusable.

I have a brand new Debian VM with GNOME, and Orca enabled, but actually using it in firefox just barely works. TalkBack has a nice workflow with highlighted elements that you move between as you read the page, but Orca seems delegated to using caret browsing and reading whatever your cursor is on? Am I missing shortcuts (which are also a pain, because the modifier can only be caps-lock or insert, not really conveniently placed)

Am I missing something, or is this the state of #Accessibility on #Linux?
Also the tts quality is very poor, which would make this even worse for any prolonged testing, but maybe there are alternative engines?

#Accessibility #linux
in reply to modulux

friendica (DFRN) - Link to source

Peter Vágner

:boosts_ok_gay:​Help with Linux Screenreaders
@modulux @:garfield:‍fuchsiaaaaaaaaaaaaaaaaa When testing web #a11y it's good to know that screen readers do often implement their own navigation paradigm as an addition to standard focus navigation and browser's caret navigation features. It's called browse mode. With orca on linux, you can press orca+a to toggle the browse mode vs focus mode when focus is inside a google chrome / chromium or mozilla firefox web content.
As for the TTS engines there is #RHVoice with some very good voices such as english voice named slt.
#a11y #RHVoice @‍fuchsiaaaaaaaaaaaaaaaaa @modulux
⇧