Re: [orca-list] VoiceOver vs. Orca - An ignorant question



Not a stupid question at all. Depending on the desktop you can set a shortcut to restart Orca. On my (admittedly custom) setup that's super+shift and O, so if speech dies I just hit Super shift O and Orca restarts immediately, but as far as I know, that's something you need to set yourself, but only set once in most* distro. I can't think of any aside from Accessible Coconut that come with the shortcut to restart Orca set by default.

It's as simple as making a new shortcut, putting orca --replace in then binding it to a key of your choice, and yes I've found that on certainDE (Mate for me) Orca seems more prone to giving up and keeling over than others, whereas on my Ratpoison setup I've never had that happen despite using the same browser and hardware however, but I'm running a customized Arch system that I'm tweaking to fit what I want, vs an Ubuntu or Mint system.

I don't feel like lawsuits are involved, no. It's more a case of Voiceover and Narrator having more folks to work on them vs Linux as a whole not being (as) popular with different camps, if you will, with their own ideas on how things should be done and to what degree. Orca isn't as bad as people on the interwebs claim and the attitude some people have of oh Linux is unuseable is false. After all if it was unuseable we wouldn't be using it, right?

Reece O'Bryan via orca-list wrote:
I tried to think of the nicest way to ask this without offending anyone on this list, but I can’t think of a way to ask my questions without either being unclear or slightly offensive, so here goes...

Why is it that VoiceOver seems to work so much better than orca? I ask from a position of pure ignorance… is it as simple as Apple having $1 T and not wanting an ADA lawsuit while Orca is a free project done by amazing volunteers? Is VoiceOver somehow integrated into Mac OS and Orca is working with further distance from the Linux kernel?

My biggest problem with orca is that I somehow repeatedly make my system kill speech by doing very small things. If this happened with Mac OS and voiceover, then I can simply tell Siri to turn voiceover off and back on. With orca it seems as if when you kill speech, then you literally have killed it and it takes dramatic steps such as a restore or reinstall  to fix it. Wouldn’t it be easier to have a secondary, potentially even optional, process running in the background that only checks to see that speech is working with Orca and Wood restart Orca if it crashes?

Maybe this is incorrect thinking. Is the problem that orca is running at or like software on the operating system instead of being a part of it like with macOS? Meaning an OS process should perform the check and fix of speech.

Thank you,

-Reece O’Bryan
C: (502)-827-3724
1645 Parkway, Sevierville, TN 37862




_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]