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

Issue 823011 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

a11y: dialog not read by screen reader if focus is on default button

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

Issue description

Google Chrome	67.0.3372.1 (Official Build) canary (64-bit) (cohort: Clang-64)
Windows 10 Enterprise Version 1607
JAWS 2018.1803.38 64-bit English 
NVDA 2018.1 

Quick tips for working with dialogs: if you've previously allowed or denied a dialog type and want to trigger it again, please just go to the security chip and change the permission for each dialog type to be "Ask (default)"
Also, if you want to have JAWS or NVDA repeat the text of the dialog, use Insert + b

Steps to repro:

# Launch AT 
# Navigate to https://permission.site
# Select a permission that launches without a default button such as the Location permission. 
# Note that the focus lands on the entire dialog. This is appropriate because there is no default button and therefore focus shouldn't belong on a specific button
# Select another permission that has a default visual and keyboard focus on a specific button such as the USB permission.
Expected: after contents of the dialog is read, the name of the button is read since it has focus
Actual: 

With JAWS, just the name of the button is read. You can then get the contents of the open dialog using Insert + b but the dialog should be read upon opening. After pressing Insert + b, the title of the dialog is read twice. The middle portion of this dialog is never read even using Insert + b.

With NVDA, the dialog title bar is read as well as the focused button. However, the middle portion of the dialog is never read even when using Insert + b. It just says "graphic table" instead of the contents of the table. (that small portion of this bug might be an authoring error)








 
Components: -UI>Accessibility UI>Accessibility>ChromeVox UI>Accessibility>Compatibility UI>Accessibility>SelectToSpeak
Labels: M67test OS-Chrome
This is also applicable to Select To Speak and ChromeVox on CrOS

Chrome OS with flag enabled: #enable-experimental-accessibility-features (not needed to repro this)
67.0.3383.0 (Official Build) dev (64-bit)
Google_Samus.6300.276.0

Steps to repro:
# Enable STS
# Navigate to https://permission.site/ and select USB to bring up a dialog with a table embedded
# Hold down search key while drawing around the table portion with the mouse
Expected: contents read
Actual: nothing is read, contents ignored

Note that ChromeVox indicates that there is a table but doesn't actually find elements in that table. 


Please see this video for repro steps: https://drive.google.com/file/d/1WVoFotLi78BosAbBQFPi_rqRG59ZG__W/view


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

Sign in to add a comment