New issue
Advanced search Search tips

Issue 773385 link

Starred by 1 user
Status: Verified
Owner:
aleventhal@chromium.org
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

a11y: button not able to be invoked on dialog with document + separate button

Project Member Reported by leberly@chromium.org, Oct 10 2017 
Chrome 63.0.3236.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 Enterprise Version 10.0.14393 Build 14393.1715
NVDA 2017.3
JAWS 2018.1710.1 Public Beta 2
Firefox 56.0 (64-bit)

I can reproduce this bug on Windows with JAWS 2018 Public Beta 2 and NVDA 2017.3 on my Windows 10 machine using Chrome Canary 63.0.3236.0. Here's what I did:

# Started JAWS and Chrome 
# Signed in with a test account at the Google store https://store.google.com/us/config/pixel_2?hl=en-US  
# Pressed Buy and selected option such as color, carrier, etc.
# Navigated to Preferred Care, pressed Enter to invoke. Popup appears
# Noted that when navigating to the Add to Order button, JAWS says "Open notification panel Button" instead of Add to Order Button. 
# Pressed enter on the button to try to invoke, nothing happens

# Closed JAWS, opened NVDA with Chrome Canary
# The button is read properly as "Add to Order Button" 
# Pressing Enter does nothing 

# Opened JAWS and Firefox, followed steps above 
# Preferred Care works without issue, button label is read as "Add to Order Button" and pressing Enter invokes the button and returns you to the webpage.

Comment 1 by dmazz...@chromium.org, Oct 10 2017 

I can repro the issue that pressing Space or Enter doesn't click the button, but force-clicking does.

I'm on my Mac now and I can repro with VoiceOver: Ctrl+Option+Space works, but Enter and Space do not.

With JAWS, Insert+Enter or Shift+Enter may do the same thing? Please try it and see if those work.

It looks like this is at least partially a bug in the web site, not *just* in Chrome. I believe the app has a click handler for the button but *not* a handler for the enter or space key, which is a bug.

What's unclear now is why there's a difference between Firefox and Chrome. We should look into fixing that.

Comment 2 by leberly@chromium.org, Oct 10 2017

Owner: leberly@chromium.org

Comment 3 by leberly@chromium.org, Oct 10 2017

Status: Verified (was: Available)
When I tried again just now, it worked without issue and I can no longer reproduce the bug. I am resolving it as Verified since I can no longer repro.  

For what it's worth, here's what I did: 

# Launch JAWS and the target website https://store.google.com/us/config/pixel_2?hl=en-US
# Navigated to Preferred Care, pressed Enter to invoke. Popup appears.
# Navigated to the Add to Order button.
# Pressed Enter: no problems 
# Navigated back to button
# Used Insert+Enter: nothing happened
# Navigated back to button
# Used Shift+Enter: nothing happened 

Thanks,

Laura

Comment 4 by leberly@chromium.org, Oct 11 2017

Owner: ----
Status: Available (was: Verified)
Actually reopening since there are still problems in Chrome stable: 
Google Chrome	61.0.3163.100 (Official Build) (64-bit) (cohort: Stable)

When the dialog opens, I can't focus on it at all with JAWS.

Comment 5 by leberly@chromium.org, Oct 11 2017

Status: Verified (was: Available)
Google Chrome	63.0.3236.0 (Official Build) dev (64-bit) (cohort: Dev)

Tested again on Dev one more time today since it picked up the same version that Canary was yesterday. 

I can no longer reproduce this issue, I can invoke the button without issue. Therefore, I will consider it an authoring problem/issue with Chrome that has been fixed.

Comment 6 by nek...@chromium.org, Oct 18 2017 

Jaws simulates a click event when a user presses enter on a link. I don't know if the same is true for a button. However, if Jaws or NVDA asks Chrome to activate a button, we should be simulating a click ourselves.

Comment 7 by nek...@chromium.org, Oct 18 2017

Owner: aleventhal@chromium.org
Status: Assigned (was: Verified)

Comment 8 Deleted

Comment 9 by aleventhal@chromium.org, Oct 18 2017

Status: Assigned (was: WontFix)

Comment 10 by aleventhal@chromium.org, Oct 18 2017

Status: Verified (was: Assigned)
If user is in forms mode / virtual cursor off, a poorly coded button would exhibit this behavior. Specifically, a button with a mousedown handler but no key handler.
►

Sign in to add a comment