[FWD:] ChromeVox Next
2 views
Skip to first unread message
B. Henry
Apr 3, 2016, 7:31:53 PM4/3/16
to open-sourc...@googlegroups.com
I asked on the original list when we will be able to use this with chrome on Linux, Windows, OSX.
I'll post a response when there is one.
The fundamental changes sound very good, and like what they should have been doing all along.
Even so, chromevox is working quite well now, ironic that not that long after chromevox becomes a viable option they are going to completely overhaul
it, but again, the changes sound like a very good thing.
--
B.H.
Registerd Linux User 521886
----- Forwarded message from Kevin Chao <kevin...@gmail.com> -----
Date: Sun, 03 Apr 2016 22:46:06 +0000
From: Kevin Chao <kevin...@gmail.com>
To: axs-chrome-discuss <axs-chrom...@googlegroups.com>
Subject: ChromeVox Next
[1]http://www.chromevox.com/next.html
ChromeVox Next Screen Reader for Chrome OS (beta)
A new version of the ChromeVox screen reader on Chrome OS, currently known
as “ChromeVox Next,” is available for beta testing. We’ve made big changes
from top to bottom, based on important feedback from our ChromeVox users
and other lessons learned over the years.
There’s nothing to install. You can switch to ChromeVox Next by pressing a
few keys, and back to the old version (if you really want to) just as
easily. We encourage you to try it out and send us your feedback. Later
this year ChromeVox Next will be the default option, and soon after that,
we'll retire the old version (which we’re calling "ChromeVox Classic" or
just "Classic" for short).
What’s different in ChromeVox Next
If you’ve used ChromeVox before, you’ll notice some big changes.
• The ChromeVox key combo is now only one key. Instead of holding down
the Shift + Search key combo as the ChromeVox modifier keys, just use
the Search key.
• Easier jump commands. In ChromeVox Next, just press Search+H to jump
to the next heading or Shift+Search+H to move backwards.
• Sticky keys work everywhere. In ChromeVox Next, sticky keys work
across the entire user interface, including the shelf and status tray.
• Other commands also work everywhere. Jump commands, and commands like
‘find in page’ also work all across the user interface.
• New caption panel. This panel can display speech and Braille output at
the top of the screen.
• New command menus. Press Search + Period to open menus that list all
the ChromeVox Next keyboard commands.
• New sounds. New navigational sounds, also called ‘earcons’, identify
key parts of the interface, page load progress, and more.
Switch to ChromeVox Next
On a Chromebook, you can start ChromeVox by pressing Ctrl+Alt+Z. When you
start ChromeVox, it will start in the classic version for now.
To enable the ChromeVox Next beta, press Shift+Search+Q, then Q. After you
switch, you’ll hear the word "Next", then ChromeVox Next will announce
whatever currently has focus. You may also be able to tell you're using
ChromeVox Next because the earcons (sound effects) are different.
To switch back, you can press Search + Q, or you can turn off ChromeVox by
pressing Ctrl+Alt+Z to turn it off and to turn it back on. When you
re-enable ChromeVox, it will open in the older version.
[2]Click here for a complete list of ChromeVox Next keyboard shortcuts
Behind the scenes
The previous version of ChromeVox worked in part by running inside every
web page you visit. This made it very easy for ChromeVox to interact with
web pages and faithfully convert the full web experience into speech and
braille. However, this design also had many challenges: it had trouble
moving between frames and accessing certain native controls like pop-up
menus and time/date controls. In addition, ChromeVox didn't work the same
when you weren't inside a web page, for example, in the location bar,
browser toolbar, or status tray.
ChromeVox Next doesn't run inside web pages anymore. It runs separately
and interacts with Chrome by exploring the accessibility tree that spans
the entire screen, including all windows, menus, dialogs, and web page
frames. This allows ChromeVox to deliver a consistent, fast experience no
matter what you're doing.
The accessibility tree that ChromeVox Next explores is identical to the
one used by screen readers and assistive technology on other platforms.
That means that as Chrome improves its support for ARIA or other web
standards, users get the same accessibility experience on all platforms
whether using ChromeVox Next or any other tool.
--
You received this message because you are subscribed to the Google Groups
"axs-chrome-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [3]axs-chrome-disc...@googlegroups.com.
For more options, visit [4]https://groups.google.com/d/optout.
References
Visible links
1. http://www.chromevox.com/next.html
2. http://www.chromevox.com/next_keyboard_shortcuts.html
3. mailto:axs-chrome-disc...@googlegroups.com
4. https://groups.google.com/d/optout
----- End forwarded message -----
I'll post a response when there is one.
The fundamental changes sound very good, and like what they should have been doing all along.
Even so, chromevox is working quite well now, ironic that not that long after chromevox becomes a viable option they are going to completely overhaul
it, but again, the changes sound like a very good thing.
--
B.H.
Registerd Linux User 521886
----- Forwarded message from Kevin Chao <kevin...@gmail.com> -----
Date: Sun, 03 Apr 2016 22:46:06 +0000
From: Kevin Chao <kevin...@gmail.com>
To: axs-chrome-discuss <axs-chrom...@googlegroups.com>
Subject: ChromeVox Next
[1]http://www.chromevox.com/next.html
ChromeVox Next Screen Reader for Chrome OS (beta)
A new version of the ChromeVox screen reader on Chrome OS, currently known
as “ChromeVox Next,” is available for beta testing. We’ve made big changes
from top to bottom, based on important feedback from our ChromeVox users
and other lessons learned over the years.
There’s nothing to install. You can switch to ChromeVox Next by pressing a
few keys, and back to the old version (if you really want to) just as
easily. We encourage you to try it out and send us your feedback. Later
this year ChromeVox Next will be the default option, and soon after that,
we'll retire the old version (which we’re calling "ChromeVox Classic" or
just "Classic" for short).
What’s different in ChromeVox Next
If you’ve used ChromeVox before, you’ll notice some big changes.
• The ChromeVox key combo is now only one key. Instead of holding down
the Shift + Search key combo as the ChromeVox modifier keys, just use
the Search key.
• Easier jump commands. In ChromeVox Next, just press Search+H to jump
to the next heading or Shift+Search+H to move backwards.
• Sticky keys work everywhere. In ChromeVox Next, sticky keys work
across the entire user interface, including the shelf and status tray.
• Other commands also work everywhere. Jump commands, and commands like
‘find in page’ also work all across the user interface.
• New caption panel. This panel can display speech and Braille output at
the top of the screen.
• New command menus. Press Search + Period to open menus that list all
the ChromeVox Next keyboard commands.
• New sounds. New navigational sounds, also called ‘earcons’, identify
key parts of the interface, page load progress, and more.
Switch to ChromeVox Next
On a Chromebook, you can start ChromeVox by pressing Ctrl+Alt+Z. When you
start ChromeVox, it will start in the classic version for now.
To enable the ChromeVox Next beta, press Shift+Search+Q, then Q. After you
switch, you’ll hear the word "Next", then ChromeVox Next will announce
whatever currently has focus. You may also be able to tell you're using
ChromeVox Next because the earcons (sound effects) are different.
To switch back, you can press Search + Q, or you can turn off ChromeVox by
pressing Ctrl+Alt+Z to turn it off and to turn it back on. When you
re-enable ChromeVox, it will open in the older version.
[2]Click here for a complete list of ChromeVox Next keyboard shortcuts
Behind the scenes
The previous version of ChromeVox worked in part by running inside every
web page you visit. This made it very easy for ChromeVox to interact with
web pages and faithfully convert the full web experience into speech and
braille. However, this design also had many challenges: it had trouble
moving between frames and accessing certain native controls like pop-up
menus and time/date controls. In addition, ChromeVox didn't work the same
when you weren't inside a web page, for example, in the location bar,
browser toolbar, or status tray.
ChromeVox Next doesn't run inside web pages anymore. It runs separately
and interacts with Chrome by exploring the accessibility tree that spans
the entire screen, including all windows, menus, dialogs, and web page
frames. This allows ChromeVox to deliver a consistent, fast experience no
matter what you're doing.
The accessibility tree that ChromeVox Next explores is identical to the
one used by screen readers and assistive technology on other platforms.
That means that as Chrome improves its support for ARIA or other web
standards, users get the same accessibility experience on all platforms
whether using ChromeVox Next or any other tool.
--
You received this message because you are subscribed to the Google Groups
"axs-chrome-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [3]axs-chrome-disc...@googlegroups.com.
For more options, visit [4]https://groups.google.com/d/optout.
References
Visible links
1. http://www.chromevox.com/next.html
2. http://www.chromevox.com/next_keyboard_shortcuts.html
3. mailto:axs-chrome-disc...@googlegroups.com
4. https://groups.google.com/d/optout
----- End forwarded message -----
Reply all
Reply to author
Forward
0 new messages