New issue
Advanced search Search tips

Issue 768463 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
dtseng@chromium.org
lpalmaro@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

[ChromeVox] Repeats the same line multiple times, adds "status"

Project Member Reported by pczubak@google.com, Sep 25 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. Start/join a meeting using meet.google.com with Chromevox Enabled
2. Open meeting details panel on the bottom left corner

Actual result:
1. when meeting details UI is focused; when it gets to "More numbers" button it is just announced as "More numbers"
2. following more numbers announcement; it announces "Status" "2" then repeats all of the calling details info
3. it repeates the announcement from #2; multiple times

Expected:
1. announce as: "More numbers button"
2. & 3. don't repeat the calling details announcing after announcing the "More numbers" button

What is the expected behavior?

What went wrong?
Adds unexpected words and reads text multiple times.

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 
Flash Version:

Comment 1 by manoranj...@chromium.org, Sep 25 2017

Components: -UI UI>Accessibility
Labels: Needs-Triage-M61 Hotlist-Google

Comment 2 by ligim...@chromium.org, Sep 26 2017

Components: -UI>Accessibility UI>Accessibility>ChromeVox
Labels: -Needs-Triage-M61
Accessibility team to triage this bug.

Comment 3 by dtseng@chromium.org, Sep 28 2017

Status: wontfix (was: Unconfirmed)
Before filing bugs like this, please run an audit on the html generated by
whatever framework you are using. In addition, try to understand some of the
html attributes that effect the output you are presenting.

It's fine to submit bugs once you have a minimal snippet for which you believe ChromeVox or any other screen reader is mis-behaving with and you have tangible attributes that don't result in the behaviors you believe to be correct.

In your case,
1. not it's not a button. You set the role 'menu' on the menu that gets tabindex=0. This menu contains several children in the DOM, two of which appear to have role set to 'menuitem'.
2. the menu has both aria label and aria describedby set. That's why there's such a long utterance in speech.
►

Sign in to add a comment