New issue
Advanced search Search tips

Issue 899755 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

A11Y: "ChromeVox reads "Reading" but it sounds like "Running"

Project Member Reported by ballar@google.com, Oct 29

Issue description


URLs (if applicable) : https://www.coursera.org/learn/technical-support-fundamentals/lecture/F3fZT/program-introduction

Browser: Chrome 69


What steps will reproduce the problem?
"ChromeVox reads "Reading" but it sounds like "Running"
I tested in a doc too and it reads "Reading" as "Running"


What is the expected result? 
It should say the word "Reading" little bit more clearer."

Video link: https://drive.google.com/file/d/1oxnF5zyNysePGicPCx_1Ci2eYuDUs7As/view

What happens instead?
ChromeVox reads "Reading" as "Running"


 
Labels: Needs-Feedback
I am not able to reproduce this issue.

I typed "reading" into a doc and ChromeVox reads as "reading"

I could not find the word reading on the page linked or in the video on that page.

The attached video spoke many things, but I did not hear it say "reading" or "running"
@dsexton
Please navigate to https://www.coursera.org/learn/technical-support-fundamentals/lecture/F3fZT/program-introduction
and press tab to navigate within the left panel as shown in the screenshot
https://screenshot.googleplex.com/fzV5MGv4A4P

I also tested searching for "Reading" in google.com and chromevox says sometimes "Reading" and most of the times as "Running"

Check the video 
https://drive.google.com/file/d/1lteRjmKFzrZumRRqOHeXazsbqPW0qszc/view
Project Member

Comment 3 by sheriffbot@chromium.org, Nov 8

Cc: dsexton@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Owner: ----
Cc: -dsexton@chromium.org
Components: -UI>Accessibility>Compatibility UI>Accessibility>ChromeVox
Status: Available (was: Unconfirmed)
Confirmed on ChromeOS Version 72.0.3626.49. ChromeVox says "Reading" about half of the time, and "Redding" the other half. It should always say "Reading". I suspect this issue results from what ever method is used to tell the synthesizer when to pronounce read as "reed" vs. "red" (past vs future tense), but it needs to treat "reading" differently. 

The video submitted in the comments illustrates this problem on an older version. But it's still doing the same thing. 

Steps to Reproduce:
(1) Turn on Chromevox
(2) Do a google search for the word "reading"
(3) Tab through the results and listen to the varied treatment of the word. 

Sign in to add a comment