New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 875704 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

hterm: The beep sound effect may be too high pitch for hearing impaired people

Project Member Reported by raymes@chromium.org, Aug 20

Issue description

This was feedback from dsexton. We may want to consider using a different beep. 
 
can we quantify this before trying to blindly (no pun-ish intended) change the sound with no quantifiable improvement ?  what frequency range exactly should we be aiming for ?
The only thing I could find re standards for alert frequencies is a military document that recommends 200-5000 HZ, ideally 500-3000 HZ

I also found this re hearing loss:
high-frequency hearing loss is a hearing loss where you are unable to hear sounds that occur in the higher end of frequencies, which are frequencies of 2,000 Hz or higher.

the main audio parts are in the 4k range already.  there are def higher frequencies sounds, but i don't think they're critical to hearing the bell.  there's nothing in the 2k range.  see attached spectrum analyzer.

to clarify, i don't think the requirement is "there may be no high frequencies", but "there needs to be audio in specific frequencies".  i.e. if having the higher frequencies improves fidelity for people who can hear it, then imo we should do it rather than only have a low frequency muddled sound.

i'll leave this bug to someone on the UX/accessibility team though to come up with something.
bell-range.png
135 KB View Download

Sign in to add a comment