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

Issue 907151 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression
Team-Accessibility



Sign in to add a comment

NVDA does not read the Accessibility menu options in Google Docs

Project Member Reported by shrijap@google.com, Nov 20

Issue description

NVDA Version 2018.3.2
Operating System : Windows 10 Enterprise version 10.0.1.16299 
Chrome Version: 72.0.3590.0 (Official Build) dev (64-bit) (cohort: Dev)
Steps to Repro:
# With NVDA ON, open a google docs 
# Press Alt + A to access the accessibility menu
# Using up and down arrow keys try to linear navigate to the manu options under Accessibility
Expected: Should be ab;e to navigate across the A11y menu
Actual: Not able to linear navigate across the menu options

 
Retested in Chrome OS:
72.0.3590.0 (Official Build) dev (64-bit) (cohort: Dev)
Firmware Version: Google_Cave.7820.384.0
Not able to recreate the above issue, ChromeVox works fine.
I did notice that while linear navigation using up and down arrow key to traverse through the various options in accessibility 
for ex: Accessibility>Comments>Speak Comments
The screen reader reads aloud the options however the menu options get white when you press down arrow key.

Workaround for the white to go is when you press the up arrow key.
Labels: -Type-Bug Docs-specific Type-Bug-Regression
Cc: aleventhal@chromium.org
Labels: -Docs-specific G-Suite-Specific
This also repros with Jaws 2019.
Here is the output from Bisect:
You are probably looking for a change made after 607148 (known good), but no later than 607153 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/ee337661804945f198019e9a627f5957f0f0221d..43e45d3b87ee87ce9d10518d5f3a5ec0884d07b5

Status: Available (was: Untriaged)
Cc: aboxhall@chromium.org
Owner: aboxhall@chromium.org
My change looks like the most likely culprit here. Taking a look.
I suspect this is around aria-activedescendant update notifications. Digging into that...
Hi aboxhall@, I just wanted to let you know I saw some more odd behavior with the a11y menu options, this time things visually not appearing when they should. I don't think it's related to this bug specifically, but I figured I'd let you know just in case. Please see b/120684385 thanks! 
Thanks Laura!

I'm also curious whether the behaviour in this bug still reproduces now that I've reverted the change we thought was the most likely culprit.
Version 72.0.3626.7 (Official Build) dev (64-bit)
Looks like this no longer repros. Thanks aboxhall@!

Status: Verified (was: Available)

Sign in to add a comment