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.

Sign up for GitHub

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

Jump to bottom

Suggestion-NVDA automatically brings the audio levels to the one predefined by the user #3521

Closed
nvaccessAuto opened this issue Sep 12, 2013 · 4 comments
Closed

Suggestion-NVDA automatically brings the audio levels to the one predefined by the user #3521

nvaccessAuto opened this issue Sep 12, 2013 · 4 comments
Labels
close/duplicate enhancement

Comments

@nvaccessAuto
Copy link

Reported by sumandogra on 2013-09-12 09:21
Quite often when a system is shared by able bodied members of a family or at workplace, the sighted person mutes the volume or reduces it to an unusable level.
Suggestion is whenever NVDA starts, it should unmute the audio and sets the level predefined by the user.
It can take care of such situations.

Blocking #4602
@nvaccessAuto
Copy link
Author

Comment 3 by blindbhavya (in reply to comment description) on 2014-11-07 15:10
Replying to sumandogra:

Quite often when a system is shared by able bodied members of a family or at workplace, the sighted person mutes the volume or reduces it to an unusable level.

Yes, faced this situation numerous times.

Suggestion is whenever NVDA starts, it should unmute the audio and sets the level predefined by the user.

Not only when NVDA starts, but also when a computer is woken up from Sleep mode. Sighted people tend to simply turn down the volume to stop NVDA speech, and let it run in the background.

It can take care of such situations.

@nvaccessAuto
Copy link
Author

Comment 4 by driemer.riemer@... on 2014-11-10 01:13
Yep. this happens in shared computer labs,

@nvaccessAuto nvaccessAuto mentioned this issue Nov 10, 2015
Closed
@bhavyashah
Copy link

Similar (enough to be a duplicate?) to #3049

@LeonarddeR
Copy link
Collaborator

Agreed, although slightly different in approach. Closing as duplicate of #3049.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
close/duplicate enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@LeonarddeR @nvaccessAuto @bhavyashah