Issue metadata
Sign in to add a comment
|
Add the ability to use sounds instead of element names, especially on the web
Reported by
ni...@jaberspace.com,
Oct 3 2016
|
||||||||||||||||||||||||
Issue descriptionMode: force_next Version: 55.0.2878.0 Reproduction Steps: When navigating on the web, it would be fantastic to have the ability to filter out announcements such as heading, link, button, and even bullet in password fields. At the same time, it would increase efficiency if a user could be alerted to these elements via sound scapes.
,
Oct 3 2016
,
Oct 4 2016
It's the first option in the options page: enable verbose descriptions.
,
Oct 4 2016
,
Oct 4 2016
I believe I have that option checked, but I will play more with that when I get home... either way, I believe that this setting ought to be made available as part of the earcons option as was suggested above. If not, then the verbose option should be changed to provide more of a description of what it actually does. When I think of verbosity, I think of controlling whether attributes are automatically read out in documents or in dialog controls. I don't immediately think of whether links, buttons, checkboxes, lists and tables are or are not announced on the web. Thanks.
,
Oct 4 2016
Thanks for the feedback. I'll respond to each option in turn: 1. earcon+TTS (default/current) n/a 2. Earcon-only Not all roles and states have earcons 3. TTS-only This is equivalent to turning earcons off Verbosity is wording historically used by ChromeVox. It not only omits speaking roles, but it also skips some contextual announcements. I'm open to suggestions for making this setting clearer.
,
Oct 4 2016
I guess I would wish for a way to have a mode to have only earcons enabled with the exception of those roles that do not have earcons, and for those to possibly get earcons later. It seems to me to be too verbose to hear the element type and the earcon all at the same time, but from what you are saying, setting verbosity option to unchecked should eliminate this? If I don't have the option checked already, I will check it and provide feedback if needed.
,
Oct 4 2016
That's right. The option is labelled "enable verbose descriptions" Verbose descriptions are on i.e. checked, by default. Not all states have a natural mapping in terms of earcons. We try to strike a balance between more earcons and practicality. In most situations, the arcon set covers the most common controls and states are read. To go to either extreme would require someone take a while to learn.
,
Oct 4 2016
Thank you. I thought I had the option set properly, however it must have gotten checked in all of my reflashing. This is great. I do think that an even less verbose mode where headings and heading levels are heard with different pitched clicks or something would be great, bit this is pretty good as is. Thank you for prompting me to unchecked that option again. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by chaok@google.com
, Oct 3 2016