New issue
Advanced search Search tips

Issue 624231 link

Starred by 4 users

Issue metadata

Status: ExternalDependency
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature
tts
Team-Accessibility



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 description

Mode: 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.


 

Comment 1 by nek...@chromium.org, Jun 29 2016

This could be a useful feature for some, but how often is it used? Having a long list of settings that are never touched is something that often bothers me.
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.
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.

Comment 4 by nek...@chromium.org, Jun 29 2016

Cc: dts...@hcromium.org
Status: Available (was: Unconfirmed)
Thanks for all the feedback. Our mission is to serve our users, so what users ask for they should usually get.
Labels: -Type-Bug phase4 Type-Feature

Comment 6 by chaok@google.com, Dec 5 2016

Labels: tts

Comment 7 by chaok@google.com, Dec 5 2016

Status: ExternalDependency (was: Available)
Labels: NewComponent-Accessibility-ChromeVox
Labels: NewComponent-Accessibility
Components: UI>Accessibility>ChromeVox
Labels: -newcomponent-accessibility -newcomponent-accessibility-chromevox
Components: -UI>Accessibility
Cc: -dts...@hcromium.org dtseng@chromium.org

Sign in to add a comment