New issue
Advanced search Search tips

Issue 917398 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Bug-Regression
Team-Accessibility



Sign in to add a comment

Accessibility - links with display:table property not identified as link to JAWS and NVDA

Reported by a...@accessible360.com, Dec 21

Issue description

<b>Chrome Version       : <Copy from: 'about:version'></b>
URLs (if applicable) : https://jsbin.com/hificis/1/edit?html,css,output
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox: OK
       Edge:

What steps will reproduce the problem?
(1)Navigate to JSBin we created with NVDA or JAWS
(2)Read links with and without display:table property (will be obvious, noted as such)
(3)

What is the expected result? We would normally expect both links to be read as links to screen reader users.  


What happens instead? The link with the display:table property is being announced as "clickable", which is not sufficient. 


Please provide any additional information below. Attach a screenshot if
possible. We have come across this issue consistently in Chrome, but when using Firefox the links both announce properly. 

 
Labels: Needs-Milestone
Cc: swarnasree.mukkala@chromium.org
Labels: Needs-Bisect Triaged-ET
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on latest stable #71.0.3578.98 and latest chrome #73.0.3667.0 using Windows 10 by following steps as per comment#0 and issue is not seen on chrome version #60.0.3112.113. Working on bisect info, will update the other OS behaviour and bisect info soon. Hence marking this issue as Untriaged and adding Needs-Bisect label to it.

Thanks!
Components: UI>Accessibility>Compatibility
Labels: -Type-Bug -Pri-3 -Needs-Bisect RegressedIn-69 Target-71 Target-72 Target-73 M-73 FoundIn-71 FoundIn-73 FoundIn-72 hasbisect OS-Windows Pri-1 Type-Bug-Regression
Owner: dmazz...@chromium.org
Status: Assigned (was: Untriaged)
Able to reproduce the issue on latest stable #71.0.3578.98 and latest chrome #73.0.3667.0 using Windows 10 as per comment#0. The following is the bisect information.
Note: Issue is not seen using voice over in Mac.

Bisect Information:
===================
Good Build: 69.0.3456.0
Bad Build: 69.0.3457.0

You are probably looking for a change made after 566616 (known good), but no later than 566626 (first known bad).
CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/41ad01b919750c352db2269878708650cfad0d1e..ab93e8e3bec0a06fa4e5a2561fdf4a4db646364a
Suspect On: https://chromium.googlesource.com/chromium/src/+/6589a857b53023b5c12f85194583f13da2466264
Reviewed-on: https://chromium-review.googlesource.com/1083854

@Dominic Mazzoni: please help us in reassigning the issue if it is not related to your change.
Thanks.!


Sounds like a legit bug, but display:table on a link seems bizarre to me.

Components: -UI>Accessibility>Compatibility Blink>Accessibility
Labels: -Pri-1 -hasbisect -Needs-Milestone -Triaged-ET -RegressedIn-69 -Target-71 -M-73 -Target-72 -Target-73 -FoundIn-71 -FoundIn-72 -FoundIn-73 OS-Android OS-Chrome OS-Linux OS-Mac Pri-2
Owner: ----
Status: Available (was: Assigned)
Not a P1 bug unless this is affecting a very high-profile site.

Sign in to add a comment