New issue
Advanced search Search tips

Issue 885266 link

Starred by 1 user
Status: Untriaged
Owner:
einbinder@chromium.org
Cc:
disability-support-qa@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Task
Team-Accessibility



Sign in to add a comment

Title: A11Y: Google Chrome: Google Inspect: Screen reader does not read any elements under “Computed properties” [Google inspect : “Element” tab> “Accessibility” tab > “Computed Properties”]

Project Member Reported by mohossain@google.com, Sep 18 
Chrome Version 69.0.3497.92

Environment: 
Windows 10.0.16299 // Chrome Version 69.0.3497.92//  JAWS 2018. 1807.8 // NVDA 2018.2.1

Prerequisite: 
Enabled the screen reader (JAWS/NVDA)

Steps to reproduce: 
Open https://www.google.com/ or any web page.
Press Ctrl+Shift+i to open inspect. 
Navigate to “Element” tab> “Accessibility” tab > “Computed Properties”
Expand the  “Computed Properties” links and try to navigate and listen the elements under “Computed Properties”

Expected results: 
Screen reader should read the elements under “Computed properties”

Actual results: 
Screen reader does not read. 

Screen shots: https://screenshot.googleplex.com/hjVVRSMY6eQ

Comment 1 by mohossain@google.com, Sep 18

Owner: ----
Status: (was: Assigned)

Comment 2 by mohossain@google.com, Sep 18

Status: Untriaged

Comment 3 by dmazz...@chromium.org, Sep 21

Components: -UI>Accessibility -Blink>Accessibility Platform>Apps>DevTools>Accessibility
Labels: -OS-Windows -Review-Accessibility -Pri-3 Pri-1
Owner: einbinder@chromium.org
Status: Assigned (was: Untriaged)
I can reproduce on Mac too.

The bug may be elsewhere, as I see stuff in the accessibility tree, but there seems to be an issue with the tree control.

Joel, could you take a look? If the bug is in Blink accessibility, could you create a small standalone repro to make it easier for me to debug?

Comment 4 by einbinder@chromium.org, Sep 21 

This looks like a DevTools bug. The items should be focusable, because they are expandable. But they aren't, which mostly likely confuses the screen readers into not thinking there is any content in the tree.

We are working keyboard navigability for items in the console, and once that is done, fixing this should be easy.
Project Member

Comment 5 by bugdroid1@chromium.org, Sep 25 

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

commit 32ec449328655f6133798b78930634c1ec98e297
Author: Joel Einbinder <einbinder@chromium.org>
Date: Tue Sep 25 00:24:35 2018

DevTools: Make the computed styles section focusable

Bug: 885266
Change-Id: I5201db68f9e5e7f934c3ff270e5b757991ee0bd5
Reviewed-on: https://chromium-review.googlesource.com/1239630
Reviewed-by: Erik Luo <luoe@chromium.org>
Commit-Queue: Joel Einbinder <einbinder@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593769}
[modify] https://crrev.com/32ec449328655f6133798b78930634c1ec98e297/third_party/blink/renderer/devtools/front_end/elements/ComputedStyleWidget.js

Comment 6 by einbinder@chromium.org, Oct 9

Status: Fixed (was: Assigned)

Comment 7 by mohossain@google.com, Nov 2

Status: Untriaged (was: Fixed)
Tested on updated Chrome Version 70.0.3538.77. 
The problem still exists. 
Here is the reference video clip: (1) Test with JAWS : https://drive.google.com/file/d/1vTkPNBBD9wWc1_Krkxhh9wDdmewV8EoK/view?usp=sharing 
(2) Test with NVDA: https://drive.google.com/open?id=11PE4fHlzDXojlj8havjIf9GLVzkaAM
►

Sign in to add a comment