New issue
Advanced search Search tips

Issue 820350 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

a11y: Button labels in various dialogs read twice by screen reader

Project Member Reported by leberly@chromium.org, Mar 9 2018

Issue description

Google Chrome 66.0.3349.0 (Official Build) canary (64-bit) (cohort: 64-Bit) compared to Google Chrome 64.0.3282.167 (Official Build) (64-bit) (cohort: Stable)
Windows 10 Enterprise Version 1607
NVDA 2017.4 

Note that there is a change in UI in Chrome 66 and this affects both UIs. These bugs were found while doing a testing sweep of the new UI dialogs. Please feel free to break into individual bugs if needed.  

Button labels are read twice in the following areas/repro steps with NVDA in browse mode:

App Info Dialog: Go to chrome://apps, right click app, click on App info

Ask Google for Suggestions: In an edit area, right click text, go to Spellcheck, click on "Ask Google for Suggestions"

Request for site to use camera: Go to https://permission.site/, click on camera

Request for site to use flash: Go to https://permission.site/, click on flash

Firefox Import Error: Attempt to import bookmarks from Firefox, with Firefox still running

Translate Dialog: Visit a page in another language, like yahoo.co.jp, click the translate icon in the Omnibar


 
Owner: aleventhal@chromium.org
Status: Assigned (was: Available)
catq 
Project Member

Comment 2 by bugdroid1@chromium.org, Apr 27 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3466d3c60cb98e21386cc59b5114e5a7123947d3

commit 3466d3c60cb98e21386cc59b5114e5a7123947d3
Author: Aaron Leventhal <aleventhal@chromium.org>
Date: Fri Apr 27 04:12:55 2018

Fix double speaking of buttons by stripping name from ignored items

When the accessibility object for a View is ignored, it is not getting
ignored by NVDA's virtual buffer. It is not enough to give it a role
of client and make it invisible -- it also need to be nameless.

Bug: 820350
Change-Id: I388b19ae65f1f5bf02ed6135936f0b75e2a153f8
Reviewed-on: https://chromium-review.googlesource.com/1031130
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#554297}
[modify] https://crrev.com/3466d3c60cb98e21386cc59b5114e5a7123947d3/ui/accessibility/platform/ax_platform_node_win.cc

Labels: -a11y-Dialogs
Labels: -dialogs a11y-Dialogs
Labels: --a11y-Dialogs

Sign in to add a comment