Issue metadata
Sign in to add a comment
|
Accessibility issue: List items have a default_action = click
Reported by
james.sc...@atsid.com,
Nov 16 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. Create a page with a simple UL list with an LI 2. Use Jaws to read the page What is the expected behavior? JAWS should read the list and not announce the item as clickable What went wrong? The item is announced as clickable. Inspecting the Accessibility Tree, verified the default_action = 'click'. Did this work before? Yes Can only confirm it worked in 43 Does this work in other browsers? Yes Chrome version: 52.0.2743.116 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0 This is similar to issue 662254 (https://bugs.chromium.org/p/chromium/issues/detail?id=662254), except that in this case, there are no mouse handlers involved. Seems as Chrome perceives ALL lists as intractable. According to the aria spec, a list is non-interactive; a role of listbox would make it interactive.
,
Nov 16 2016
,
Nov 30 2016
Could you please provide us with a sample test cases/sample html file of the issue which would help us to triage the issue further. Thanks in Advance.
,
Dec 2 2016
This must have been fixed. I am unable to reproduce in latest Chrome Dev. I remember this bug occurring a while ago, but it doesn't any more. Tested with Jaws 18 and latest NVDA. Also, verified that accessibility tree doesn't include any action for list items.
,
Dec 2 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by james.sc...@atsid.com
, Nov 16 2016