Mac OS X Lion VoiceOver with Google Chrome Canary

35 views
Skip to first unread message

Kevin Chao

unread,
Aug 16, 2011, 7:52:14 PM8/16/11
to Chromium Accessibility
• with multiple tabs open, switching tab, VO reads message "next/
previous tab", but does not read title of tab that gains focus.
• creating multiple windows, VO reads "new tab (should be window",
cycling windwos read title of window, which should be done with tabs.
• typing into address bar, VO is very verbose, reads suggestion/
correction, it should only read only what typing echo is set to.
• in address bar, it should be possible to query suggestion on demand
and scroll through options.
• homepage set to google.com, open Chrome, VO reads empty scroll area,
must VO right, where VO focus should auto-interact and focus edit box
• type into edit box, VO will not provide typing echo and can't
review, must VO away and back, where it will be possible to review
contents
• preferences, must interact, where VO should auto-interact, and place
focus on category.
podbean.com and coursesmart.com, log in and sign in links do not
work. cannot activate with VO-SPACE
• when opening a new page, tab, window, etc. VO should auto-interact
with HTML content, no need for empty scroll area
• VO and Chrome do *NOT* recognize ARIA Live-Regions at all: http://goo.gl/3035J
and W and SHIFT-W do *NOT* work for landmarks.

Chris Guillory

unread,
Aug 16, 2011, 8:37:09 PM8/16/11
to Kevin Chao, Chromium Accessibility, dts...@chromium.org
Kevin,

Thanks so much for trying out Chrome with VO and providing us with the issues you are encountering. We'll have to sift through these to get them on the public bug tracker at http://code.google.com/p/chromium/issues/list.

-Chris

David Tseng

unread,
Aug 16, 2011, 10:21:41 PM8/16/11
to Chris Guillory, Kevin Chao, Chromium Accessibility
Thanks Kevin! We're still working on further improvements to Mac
Chrome a11y, so stay tuned.

- David

Kevin Chao

unread,
Aug 17, 2011, 2:28:45 PM8/17/11
to Chromium Accessibility, dts...@chromium.org
Thanks Chris, David, and all for being very quick to respond,
understanding, and committed to VoiceOver accessibility. One page that
I use a lot, both professionally and academically is CourseSmart.com,
which does not seem to work well with Chrome. I'm wondering if this is
a Chrome or VoiceOver issue as it works fine everywhere else, such as
Safari, WebKit, and Lightning web browsers.

Steps to Reproduce:
Open Chrome, visit CourseSmart.com;
try to TAB or SHIFT-TAB through HTML elements, links, edit boxes, buttons, etc);
Expected: Voiceover to move to and read HTML element(s)
Actual: Nothing
VO-U for web rotor, navigate to sign in link;
activate sign in link with VO-SPACE, SPACE, RETURN, or VO-SHIFT-SPACE;
Expected: sign in link to be activate and to be brought to sign in page
Actual: Nothing

Notes: Works fine with Safari, Webkit, and Lightning.

Thanks,

Kevin

Chris Guillory

unread,
Aug 17, 2011, 3:08:04 PM8/17/11
to Kevin Chao, Chromium Accessibility, dts...@chromium.org
Kevin,

For these problems I've filed crbug.com/93232 on our public bug tracker. We are still sifting through the issues from your original email. Please understand that VoiceOver accessibility is a work in progress. Thanks!

Dominic Mazzoni

unread,
Sep 30, 2011, 10:24:58 AM9/30/11
to Kevin Chao, Chromium Accessibility, dts...@chromium.org
Hi Kevin,

Good news, we fixed the Chrome bug that was making it impossible to work with CourseSmart.com, podbean.com, and other similar sites. You can try it out in the Canary version of Chrome today, once it auto-updates for you.

There are a bunch of other small bug fixes, but this one was the biggest because it made it impossible to even test it out on many sites, so I wanted to announce that!

This bug fix applied to Windows, too, so if anyone on this list wants to try out Chrome with JAWS or NVDA, you'll probably notice some improvements in the Canary version starting today.

Thanks again for trying it out!

- Dominic

On Wed, Aug 17, 2011 at 11:28 AM, Kevin Chao <kevin...@gmail.com> wrote:

Kevin Chao

unread,
Oct 1, 2011, 12:26:27 AM10/1/11
to Dominic Mazzoni, Chromium Accessibility, dts...@chromium.org
Google Chrome is up to date (16.0.896.0) and NVDA Snapshot Main-4707

CourseSmart.com;
NVDA+F7 for elements list;
type "accessibility" and ENTER;
NVDA+T for title and accessibility page is reported;
CTRL+HOME to go to top of page;
H to go through all headings

Expected:
About the Site
The CourseSmart Commitment
CourseSmart Accessibility Strategy
Accessibility Roadmap
CourseSmart Accessibility Status
Need an Accessible eTextbooks or eResource?
CourseSmart Partnership with AccessText Network
Stay in Touch

Actual:
Number 1 in eTextbooks and Digital Course Materials
Try eTextbooks risk-free with a FREE TRIAL
Featured eTextbooks
Featured eResources

Notes: When navigating by headings (h), NVDA reports heading twice,
but it does not when navigating by line (DOWN ARROW) or report line
(NVDA+UP ARROW). Actual results are as a result of Chrome not updating
buffers via IA2 in a way that NVAD understands, resulting in title of
page updating, but not content, and requiring a force refresh with
NVDA+F5.

Kevin

Kevin Chao

unread,
Oct 1, 2011, 12:33:39 AM10/1/11
to Dominic Mazzoni, Chromium Accessibility, dts...@chromium.org
Google Chrome is up to date (16.0.896.0) and NVDA Snapshot Main-4707

Omnibar: Podbean;
LEFT ARROW several times, RIGHT ARROW several times;
Expected: NVDA to navigate to and read previous or next character
Actual: silence, Chrome edit fields do not provide any feedback via IA2 to NVDA
Notes: Same occurs when BACKSPACING or DELETING--Chrome does not
provide any feedback to NVDA
CTRL+ENTER;
NVDA+F7, type "log", and ENTER;
e to login edit field;
Expected: three edit fields: search, username, and password
Actual: one edit field: search
Notes: Chrome buffers are not updating invia IA2, allowing NVDA to
report the content of the page correctly

Kevin

Kevin Chao

unread,
Oct 1, 2011, 12:45:31 AM10/1/11
to Dominic Mazzoni, Chromium Accessibility, dts...@chromium.org
Google Chrome is up to date (16.0.896.0) and NVDA Snapshot Main-4707

http://devfiles.myopera.com/articles/735/example.html
CTRL+HOME to top of page;
H to "Favourite Artists";
TAB to "Art Brut"
Expected: Application, Favourite Artists list, Art Brut, draggable,
submenu, not selected, 1 of 6
Actual: Art Brut

SPACEBAR
Expected: dragging, tolerable artist, 1 of 2
Actual: nothing

DOWN ARROW
Expected: rejected artist, 2 of 2
Actual: Babyshambles

Notes: Accessible drag and drop using WAI-ARIA is not
implemented/supported in Chrome with NVDA, but is with ChromeVox
(issues with level of feedback provided) and details of making Chrome
up to par can be found at:
http://dev.opera.com/articles/view/accessible-drag-and-drop/

David Tseng

unread,
Oct 2, 2011, 11:33:31 AM10/2/11
to Kevin Chao, Dominic Mazzoni, Chromium Accessibility
Hi Kevin,

Thanks for the bug reports! Again, feel free to file directly at
crbug.com and I'll make sure to keep an eye out for your email
address. Also, if you happen to test on other browsers, it would be
helpful to include whether you see the issue(s) there as well (i.e.
webkit, Safari).

I've filed:
crbug.com/98814
- chromium - a11y: NVDA heading quick key enumerates through stale
elements on coursesmart.com

crbug.com/98815
- chromium - a11y: NVDAnot echoing text in omnibar

crbug.com/98816
- chromium - a11y: NVDA not picking up on tree changes on podbean -

crbug.com/98817
chromium - a11y: support drag and drop

Kevin Chao

unread,
Oct 2, 2011, 2:48:32 PM10/2/11
to David Tseng, Dominic Mazzoni, Chromium Accessibility
Hi David,

Thanks for filing all these bugs! No, none of these issues occur with
Firefox 10 alpha and NVDA 2011.3 snapshot.

Lack of proper and full combobox support is one I brought up in a
different thread. I'm wondering if this is a known issue or not.

Kevin

Kevin Chao

unread,
Oct 2, 2011, 5:12:02 PM10/2/11
to David Tseng, Dominic Mazzoni, Chromium Accessibility
Hi David,

I filed:
crbug.com/98827
- a11y: NVDA combobox does not expand or speak change while arrowing on eBay.com

and commented on all the bugs you filed.

Can you please add feature-accessibility?

Thanks,

Kevin

Dominic Mazzoni

unread,
Oct 3, 2011, 2:25:10 AM10/3/11
to Kevin Chao, David Tseng, Chromium Accessibility
Lack of proper and full combobox support is one I brought up in a
different thread. I'm wondering if this is a known issue or not.

Yes, combobox support is a known issue and it's next on my list, I hope to finish that in time for Chrome 16. Thanks again for all of these reports!

- Dominic

Kevin Chao

unread,
Oct 3, 2011, 6:25:41 AM10/3/11
to Dominic Mazzoni, David Tseng, Chromium Accessibility
Hi Dominic,

Thanks! This is excellent. Hopefully, when combobox support is fully
implemented, it will work across multiple platforms and screen
readers? For example, Mac OS X VoiceOver and Windows NVDA/JAWS?

it's fantastic that Google accessibility is so open, receptive,
interactive, and addressing bugs so rapidly. Keep up the fantastic
work!

Kevin

David Tseng

unread,
Oct 3, 2011, 11:37:30 AM10/3/11
to Kevin Chao, Dominic Mazzoni, Chromium Accessibility
Actually, combo boxes should work on Mac (and ChromeVox). Let us know
if you see otherwise.
Reply all
Reply to author
Forward
0 new messages