[orca-list] reading docs and accessibility (was orca-list] GUI Redesign or clearup and modernization)

[Al Sten-Clanton <albert e sten_clanton verizon net>]

An advantage of some Linux distros now is being able to bring up Orca 
with alt-super-s.  (Maybe we should try to create a keystroke like that 
for Speakup.) I believe Mac accessibility must be set up by the folks at 
the Apple store, or, presumably, a sighted person who knows or can 
figure out how to do it.


Al

On 9/3/2015 5:26 AM, Tony Baechler wrote:
> On 9/2/2015 5:00 AM, Christopher Chaltain wrote:
> > I haven't been following this thread, but the post below either
> > confuses me
> > or I just don't agree. I can't think of a single screen reader where you
> > don't need to know at least one key stroke before starting, such as
> > how to
> > bring up the preferences. You either have to know that key stroke or be
> > familiar enough with the operating system to know how to get into the
> > preferences for an application, which I think is what the post below is
> > disagreeing with.
>
> In general, I agree with you.  Once you have basic familiarity with the
> environment, what you say is valid.  Like you, I have yet to find a
> screen reader that doesn't require you to know a keystroke to access the
> prefs. However, if I can make a comparison to Windows for a moment,
> there is at least one Windows screen reader which runs a getting started
> wizard when it's launched for the first time.  It's very basic, but does
> allow you to set the pitch and rate.  It also pops up a tip of the day
> with helpful information, such as how to access the prefs.
>
> > Either way, it's an overly simplistic attitude to say that expecting
> > someone
> > to read some information about an application before using it is the
> > reason
> > so many people are put off by Linux.
>
> Yes, well, simplistic or not, it's an unfortunate reality.  I can't tell
> you how many people I've come across who were put off because they
> complained that they had to read lots of docs before even getting
> started.  I'm sorry, but we have to deal with reality whether we like it
> or not.  I myself don't have that attitude and I don't mind reading
> docs, but I'm the exception. How many times do you hear sayings like,
> "If all else fails, read the instructions."  How many beginners actually
> take the time to read the manual?  I'm sorry, but simplistic or not,
> that's the way it usually is. This is even more so when you have the Mac
> which includes accessibility automatically when the machine is first
> configured.
>
> Also, let me mention here that when most blind people get a computer
> with Windows on it, there is already a screen reader installed.  I know
> that rehab agencies purchase screen readers for their clients and I know
> of a computer donation program which installs NVDA on donated machines.
> Since it's still impossible for the blind to install Windows without
> sighted help and since the two screen readers I've used have talking
> installers, Linux has a strike against it from the point of view of a
> Windows user before they even get started.  Expecting them to read a set
> of docs on a foreign desktop environment with a foreign screen reader is
> too much to ask, I think.  FYI, I didn't have a donated machine and I
> didn't have rehab purchase a screen reader for me, so I'm more used to
> figuring things out on my own.  The attitude above is not my opinion,
> but reflects reality for most people that I've encountered.
> _______________________________________________
> 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
> Log bugs and feature requests at http://bugzilla.gnome.org