ChromeVox reads FAQ as /fæk/ on Goobuntu |
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36 Steps to reproduce the problem: 1. Enable ChromeVox. 2. Go to https://en.wikipedia.org/wiki/FAQ. 3. Hear /fæk/ followed by /ˌwɪkɪˈpiːdɪə/. What is the expected behavior? FAQ should always be read as /ɛf.eɪ.kjuː/. What went wrong? Pronunciation of FAQ as /fæk/ is undesired. Did this work before? N/A Chrome version: 54.0.2840.100 Channel: stable OS Version: Flash Version: Shockwave Flash 23.0 r0 On Mac OS machines available for this test, ChromeVox pronounces FAQ as /ɛf.eɪ.kjuː/.
,
Nov 24 2016
Thanks for the report. Able to reproduce the issue on Win 7, Ubuntu 14.04 using Chrome Canary #57.0.2929.3, Stable version#54.0.2840.99.Issue not seen on Mac 10.11.4. This is non-regression issue, issue existing from M45 build, #45.0.2454.101. Chromevox not reading the text on windows <45 builds. Hence marking it as untriaged.
,
Dec 2 2016
Likely not an issue in extensions platform itself, but rather chromevox. +cc some acessibility folks who are more familiar with chromevox for further triage
,
Dec 5 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by manoranj...@chromium.org
, Nov 16 2016