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

Issue 730953 link

Starred by 5 users

Issue metadata

Status: Verified
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

Add extension confirmation dialog contains inappropriate inner dialog

Project Member Reported by ja...@nvaccess.org, Jun 8 2017

Issue description

Chrome Version: 61.0.3122.0 (Official Build) canary(64-bit)
OS: Windows 10 Version 1703 (OS Build 16199.1000) 64-bit

What steps will reproduce the problem?

(1) Start Chrome and the NVDA screen reader.
(2) Open the Chrome store page for some extension you do not have installed; e.g. https://chrome.google.com/webstore/detail/violentmonkey/jinjaccalgkegednnccohejagnlnfdag?hl=en-GB
(3) Press the "Add to Chrome" button.
(4) A confirmation dialog will appear. Press NVDA+space to force browse mode for the dialog.
(5) Use the down and up arrow keys to read through the text.

What is the expected result?
The prompt "Add "Violentmonkey"?", followed by the permissions the extension will have, should be reported.

What happens instead?
That text is not reported. Only the buttons are reported.

This occurs because the prompt/permission text is contained within an inner dialog which can never get focus. That inner container should not have a role of dialog, since it isn't focusable and we're already inside a dialog.

Impact: This makes it difficult for most Chrome + NVDA users to review this confirmation prompt, which could be a security concern for those users.
Originally reported in NVDA issue: https://github.com/nvaccess/nvda/issues/6766
 
Components: Platform>Extensions
Status: Assigned (was: Untriaged)
Untriaged w/ owner -> Assigned.

@jamie, Is this extension specific or does this apply to all similar chrome dialogs?

Comment 3 by ja...@nvaccess.org, Jun 25 2017

It's not specific to a particular extension; this same dialog appears when you add an extension that isn't already added. I've also seen this same problem in other Chrome dialogs, but I don't recall which dialogs they were.
Labels: triage-nektar
Labels: triage-aaron
Cc: nek...@chromium.org
Labels: -triage-aaron -triage-nektar
Owner: ----
Status: Available (was: Assigned)
Components: -UI>Accessibility
Labels: Watchlist-Accessibility
Status: Untriaged (was: Available)
Cc: rdevlin....@chromium.org
Components: UI>Accessibility
Labels: -Pri-3 Pri-2
Owner: dmazz...@chromium.org
Status: Assigned (was: Untriaged)
assigning to dmazzoni@ for triage, since this is very similar to  issue 781255 
Labels: win-a11y
Labels: -Pri-2 Pri-1
Labels: dialogs
 Issue 689218  has been merged into this issue.
 Issue 781255  has been merged into this issue.
Owner: aleventhal@chromium.org
Maybe a good candidate for the Views accessibility audit?

Status: Verified (was: Assigned)
Chrome: 67.0.3394.0 (Official Build) canary (64-bit) (cohort: Clang-64)
This is fixed. There are some remaining issues in the order of the text described in issue 823010.

Sign in to add a comment