New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 679435 link

Starred by 2 users
Status: Fixed
Owner:
█ nek...@chromium.org
Last visit > 30 days ago
Closed: Dec 2017
Cc:
lpalmaro@chromium.org
█ kkaja@google.com
dmochak@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

"clickable" reported 3x

Project Member Reported by chaok@google.com, Jan 9 2017 
Chrome version: 57.0.2976.0 canary (64-bit).
OS: Win10
Screen reader: NVDA 2016.4

What steps will reproduce the problem?
(1) Using above combo
(2) Go to Gmail. Open a thread. Z
(3) Go to Gmail. Open a thread. Switch to browse mode and press H to go to next heading. 

What is the expected result?
Chrome to not report clickable (similar to what happens when turning this off in NVDA > Preferences > Document formatting > Clickable) 

What happens instead?
NVDA reads at least 3 "clickable" before reading the heading text. Probably there are far too many onclick events but it gets real annoying.

NVDA logs:
IO - inputCore.InputManager.executeGesture (11:24:02):
Input: kb(laptop):h
IO - speech.speak (11:24:02):
Speaking [LangChangeCommand ('en'), u'clickable', u'clickable', u'clickable', u'Kiran Kaja', u'heading  clickable  level 3']
DEBUGWARNING - synthDriverHandler.SynthDriver.speak (11:24:02):

Comment 1 by chaok@google.com, Jan 13 2017

Cc: dmochak@google.com
Per Drew:
"I'm still hearing a lot of "clickable" links/text that isn't actually clickable, as well as the inverse: clickable text not marked as clickable (and thus not actionable."

Comment 2 by dmazz...@chromium.org, Mar 27 2017

Labels: NewComponent-Accessibility NewComponent-Accessibility-Compatibility

Comment 3 by dmazz...@chromium.org, Apr 21 2017

Components: UI>Accessibility>Compatibility

Comment 4 by dmazz...@chromium.org, Apr 21 2017

Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility

Comment 5 by dmazz...@chromium.org, Aug 4 2017

Labels: triage-dougt

Comment 7 by aleventhal@chromium.org, Aug 7 2017

Labels: -Pri-2 -triage-dougt Pri-1
Status: Assigned (was: Untriaged)

Comment 8 by nek...@chromium.org, Dec 10 2017

Status: Fixed (was: Assigned)
We modified our accessibility API to report "clickable" only when  there is a click handler on the current element without taking into consideration its ancestors in the DOM. I believe we did everything we could from Chrome's side and it's up to the screen reader to decide how and when to report the provided information.

Comment 9 by leberly@chromium.org, Jan 17 2018

Labels: win-a11y
►

Sign in to add a comment