Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Voice aliases #4433

Closed
nvaccessAuto opened this issue Sep 1, 2014 · 12 comments
Closed

Voice aliases #4433

nvaccessAuto opened this issue Sep 1, 2014 · 12 comments

Comments

@nvaccessAuto
Copy link

Reported by td.dinakar on 2014-09-01 06:54
While reading text line by line or by using say all command, NVDA reports the elements information such as heading, link,, etc. It is quite annoying to hear the words "link" and "Heading level 1", etc., each and every time. If we disable reporting of these elements in the settings, we may not be able to know whether a particular text is a link or heading.

In JAWS, we have a good feature called "Speech Aliases", which help us to set different voices for different elements. When this feature is enabled, the screen reader reads only the text of the heading or the link, but with a different voice, so that we can identify the element of the text.

Since the default eSpeak synthesizer used in NVDA has several voice variants, it will be very useful if voice aliases are also made available in NVDA for reading the web elements.

Blocked by #4877
Blocking #5461

@nvaccessAuto
Copy link
Author

Comment 1 by briang1 on 2014-09-01 08:04
A couple of comments. How does altering a voice make it less annoying? Maybe define some config profiles with the options on and off for what you need?
I've not actually tried this myself but at least that could be one solution if you want to go through the info, such as on Wikipedia, withoug all the clutter.
Maybe if this sort of voice change is needed, another special case part of configuration setting could be included like the say all one which switches voices on different information, against pure content.

@nvaccessAuto
Copy link
Author

Comment 2 by td.dinakar (in reply to comment 1) on 2014-09-01 14:35
I'm sorry, I'm unable to explain it. You'll be able to appreciate this feature only if you use it.

You can imagine how fantastic it would be, if NVDA reads the headings, links, block quotes, messages, etc., in different voices, instead of

informing the element type each time we land on an element. This should be available when using say all command or while using

arrow keys.

For example, if we take this web page, eSpeak should read the headings "4433", "Voice aliases" and "Description" using voice variants

such as John, Mr. Serious, Sam, etc., instead of reading as "4433 link heading level 2", "Voice aliases heading level 1" and "Description

heading level 3". Similarly, the links "td.dinakar", ", "minor" and "speech" should be read using variants such as female 5, Linda, etc.,

instead of reading them as "link td.dinakar", "link minor" and "link speech".

This would not only be useful in web sites like Wikipedia, but in all web pages containing various elements.

Replying to briang1:

A couple of comments. How does altering a voice make it less annoying? Maybe define some config profiles with the options on and off for what you need?

I've not actually tried this myself but at least that could be one solution if you want to go through the info, such as on Wikipedia, withoug all the clutter.

Maybe if this sort of voice change is needed, another special case part of configuration setting could be included like the say all one which switches voices on different information, against pure content.

@nvaccessAuto
Copy link
Author

Comment 3 by blindbhavya on 2014-09-05 04:19
Hi.
This suggestion is very interesting.
However, would the user be able to that efficiently and quickly distinguish between the variants? Would the user be able to remember which variant is for which element?
Can you in detail explain where this feature is in JAWS? I want to see how I find it.
Thanks.

@nvaccessAuto
Copy link
Author

Comment 5 by td.dinakar on 2015-05-02 05:42
Is anybody taking effort on this ticket? What is the present status?

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2015-05-02 08:51
I think this should be done with configuration profiles. It cannot be done until #4877 is implemented.

@nvaccessAuto
Copy link
Author

Comment 7 by camlorn on 2015-05-18 19:39
It is also worth noting that this can be done through audio, i.e. Unspoken. This is my personal preference, especially since audio notifications can remain the same between different synths. I think that we should at some point discuss this some: I doubt that both will go into core. Given our wide variety of synth drivers, audio might work better if only because it would work with everything, even single-voice synths.

@zahra21
Copy link

zahra21 commented Apr 16, 2017

hi.
i have question.
i dont want to use different voice for different elements.
but i only wish that only use say all with no informations about elements and use arrow keys and quick navigation keys with elements.
for example: when i want to use say all command, i only wish that read my document or book without such informations,
but when i use navigation quick keys or arrow keys, i wish that hear these informations!
i asked in mailing list for users and suggested me configuration profile and trigggers.
but it is not my desire and wantedd suggestion, because in this case i cant realize for example even links using navigation quick and arrow keys!
what should i do to achieve my Goal?
thanks extremely for your help and God bless you all.

@Brian1Gaff
Copy link

Brian1Gaff commented Apr 17, 2017 via email

@cary-rowen
Copy link
Contributor

I think this is a useful feature. After such a long time in the past, I still hope that this issue gets attention and I hope to increase its priority.

@Adriani90
Copy link
Collaborator

very related to #4086.

@Adriani90
Copy link
Collaborator

This is a use case for the framework inmplemented in #7599.

@Adriani90
Copy link
Collaborator

Closing as duplicate of #4086.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants