Issue metadata
Sign in to add a comment
|
extension manager is inaccessible to screen reader reliant users
Reported by
m...@proctorio.com,
Aug 27 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.49 Safari/537.36 Steps to reproduce the problem: 1. on any inline install page for chrome extensions 2. click the link to activate the dialog 3. the dialog is inaccessible to screen reader reliant users What is the expected behavior? What went wrong? In a recent audit, it was brought to our attention that the chrome extension manager is inaccessible to screen reader reliant users when adding an extension using an inline install. The evaluation was done using NVDA 2016.4 and Google Chrome 56.0.2924.87 on Windows 10. Did this work before? N/A Chrome version: 56.0.2924.87 Channel: n/a OS Version: 10.0 Flash Version:
,
Aug 29 2017
,
Sep 3 2017
Good call, that was the original Chrome tested when we first noticed this issue. Retested on Chrome 60.3112.101 same issue. Once you activate the inline install the prompt comes up but the screen reader stays silent.
,
Sep 3 2017
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 4 2017
Unable to reproduce this issue on Windows-10 using chrome latest stable #60.3112.113. Able to install the inline extension in chrome as expected. Mile@ Could you please confirm is this issue is a feature? If not, Please provide sample extension to check this issue from chrome-TE end. Thanks!
,
Sep 12 2017
@brajkumar what version of NVDA did you use? clicking the inline install does not trigger any messaging in the screen reader that a prompt is active for the inline install
,
Sep 12 2017
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 8 2017
@mike: Are you still able to reproduce the issue in latest stable #62.0.3202.89? Thanks!!
,
Jan 30 2018
,
Feb 12 2018
Latest stable is now 64 and NVDA 2017.4. I cannot reproduce this issue. Please provide exact steps and name of extension you noticed the issue on.
,
Mar 16 2018
Please re-open this issue if it is still reproducible. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Aug 29 2017Labels: Needs-Milestone