Issue metadata
Sign in to add a comment
|
Chromevox or Google TTS ought to provide the ability to control how numbers are spoken
Reported by
nimerjaber1@gmail.com,
Jun 29 2016
|
||||||||||||||||||||||
Issue descriptionMode: force_next Version: 53.0.2773.0 Reproduction Steps: 1. This is a feature request that is found in other screen reading solutions on Windows and Mac platforms. 2. This feature would allow for the control of how numbers are announced. For example, the number 12345 could be announced as 1,2,3,4,5 or twelve thousand, three hundred and forty-five. 3. This seetting is important as it would allow users to choose how numbers are announced. I might want numbers to be read out individually or in pairs while editing formulas in Sheets. Or, I might want numbers to be spoken out in words while performing a read from cursor to end of text.
,
Jun 29 2016
I don't know What is or isn't useful to others, however this feature for me is a useful addition. Depending on which content I'm reading, I want numbers to be read out differently. In Docs, having a long string of numbers read out is pointless. I would, instead, prefer for the number to be read out in words as a whole number. In sheets, I would like the numbers to be read out individually. This is a setting I adjust in all screen readers per application, and sometimes, per session. Still, I am cognizant of the fact that not all feature requests can be considered, and if it is determined that this is a feature that users don't care about, it should be left out. I don't like to see pages and pages of settings either.
,
Jun 29 2016
From a user perspective and an instructor perspective, I hate seeing settings upon settings. But I do like having the options available, even if they are hidden from most users behind an advanced wall or some other implementation. I hate too many settings, but I hate constraints even more.
,
Jun 29 2016
Thanks for all the feedback. Our mission is to serve our users, so what users ask for they should usually get.
,
Jul 15 2016
,
Dec 5 2016
,
Dec 5 2016
,
Mar 6 2017
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 2
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nek...@chromium.org
, Jun 29 2016