GNOME.org
 

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

Hi,
In my experience pressing Alt+F1 in Unity: when pressing the keys and releasing them too fast you will land into the dash and not in the launcher in Unity. That can be the reason you wil hear panel panel etc. Alt takes you to the Dash. 
Milton

Op 04-09-15 om 02:22 schreef Devin Prater:

Ah, I must be in unity then, because it says “window” and flat reviewing shows “activity” the date, then a 
lot of “panel panel panel” then “type to search”.

On Sep 3, 2015, at 7:19 PM, kendell clark <coffeekingms gmail com> wrote:

hi
Does alt+f1 do anything? In gnome, it does nothing. In unity, it should
take you to the dash. In mate, which is the other desktop included in
vinux, it should open up the applications menu, with categories like
sound, graphics, games, etc. The one caveat is orca is usually silent
when the menu opens, so unless you have some vision, you're probably
going to think nothing happened. I'm hoping when mate finishes
transitioning over to gtk3, which is what both gnome and unity use, that
accessibility will get a lot better. It should fix some of the niggling
problems mate sometimes has, like requiring xterm for applications taht
use a terminal, which we can't use, and orca not being able to read apps
run as root.
Thanks
Kendell clark


On 09/03/2015 07:11 PM, Christopher Chaltain wrote:

I'm not sure how this question fits into this thread, so maybe I'm
missing something, but alt+f1 does take you to the launcher in Vinux 5
assuming you're using the Unity desktop. Alt+f2 will take you to the
dash. Are you sure you started Vinux with the Unity desktop? You can
also choose Gnome or Mate.

On 09/03/2015 08:46 AM, Devin wrote:

Yep. But I'm now using Vinux Trusty, and I'm not even sure on how to get
to the applications menu or anything. Yes, I looked at the Unity page on
the Vinux wiki, but nope, alt+f1 doesn't work. Any tips for this? I'm
running Orca 3.17.91.

On 09/03/2015 07:48 AM, Al Sten-Clanton wrote:

That's good to hear, even if I'm unlikely to use a Mac.

Al

On 9/3/2015 8:44 AM, Vincenzo Rubano wrote:

That’s not true. Pick up a mac, turn it on and then just press “Cmd +
F5”.

Same on iOS: pick up a device and just tell Siri to enable VoiceOver.

Vincenzo.


Il giorno 03 set 2015, alle ore 14:36, Al Sten-Clanton
<albert e sten_clanton verizon net> ha scritto:

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


_______________________________________________
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

_______________________________________________
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

_______________________________________________
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

_______________________________________________
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

_______________________________________________
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
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]