Sender: |
|
Date: |
Thu, 9 Oct 2014 21:00:46 -0700 |
Reply-To: |
|
Message-ID: |
|
Subject: |
|
MIME-Version: |
1.0 |
Content-Transfer-Encoding: |
7bit |
In-Reply-To: |
|
Content-Type: |
text/plain; charset=ISO-8859-1; format=flowed |
From: |
|
Parts/Attachments: |
|
|
Chrome has come a long way. You can now use it with or without
ChromeVox. Firefox is my primary browser, but when it's not quite
working for me, I try Chrome and Internet Explorer, usually Chrome
first, not because I have anything against Microsoft, but because Chrome
gets the job done.
About ChromVox, it's come a long way too. The last time I checked, which
was over the summer, the documentation was still out of date, so the
ChromeVox accelerator keys are shift+alt. You can hit insert twice
quickly to toggle sticky mode, so you don't have to use shift+alt all
the time. Once I got used to ChromeVox I really liked it.
The only thing I find less elegant is that there's an extra step when
you're using ChromeVox to jump to the next or previous element: Instead
of just pressing H or shift+H for the next or previous heading, you need
to press shift+alt+n (for next) or shift+alt+P (for previous) followed
by H. You get used to it, but it's two keystrokes instead of one.
I sometimes encounter buttons that ChromVox calls images, but Jaws and
NVDA call something else, so ChromeVox isn't always reading the labels
or alt text. But this doesn't happen too often.
I think Chrome and ChromeVox are good things for us to learn to use so
we can access the web on computers that don't have screen readers.
VICUG-L is the Visually Impaired Computer User Group List.
Archived on the World Wide Web at
http://listserv.icors.org/archives/vicug-l.html
Signoff: [log in to unmask]
Subscribe: [log in to unmask]
|
|
|