13731 2011-08-10 03:28:00 +0000 need simple visual alternatives to indicate that audio is playing to let a deaf user know 2016-04-07 14:55:49 +0000 1 1 1 Unclassified HTML WG HTML a11y Task Force unspecified PC All RESOLVED INVALID http://www.w3.org/mid/B6CB855C5769484F862F4FB2CCFA50F402D545A7@VHAISHMSGJ2.vha.med.va.gov a11y, media P2 normal --- 13590 1 mike contributor bugs chaals ian jackalmage laura.lee.carlson lwatson mike public-html-a11y public-html-admin public-html-wg-issue-tracking silviapfeiffer1 dave.null oldest_to_newest 54568 0 mike 2011-08-10 03:28:00 +0000 http://www.w3.org/mid/B6CB855C5769484F862F4FB2CCFA50F402D545A7@VHAISHMSGJ2.vha.med.va.gov The Audio Element No provision appears to be made for simple visual alternatives to indicate that audio is playing to let a deaf user know. This is not the same as a caption or a transcript, but would be the ability to provide a quick indicator of important sound effects, or even just to let the user know that there is a piece of music looping in the background. Without a way to provide this kind of information, users with hearing impairment could miss vital audio cues, or could inadvertently annoy people nearby because the machine they are using has its speakers blaring a midi loop of "Mary Had A Little Lamb". [split out from bug 13590] 54602 1 jackalmage 2011-08-10 15:11:52 +0000 This appears to be entirely a user-agent issue. (And it would be a good idea even for full-hearing people, since no one wants to madly hunt through all their tabs looking for which site decided to start blaring music.) 60838 2 ian 2011-12-02 20:36:29 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: UI issue. 108373 3 lwatson 2014-06-26 11:29:16 +0000 Moved to HTML A11y TF component. 125751 4 chaals 2016-04-07 14:54:27 +0000 User agent issue - some browsers implement this already. 125752 5 bugs 2016-04-07 14:55:49 +0000 Most browsers have implemented this: Chrome, Firefox, and Safari at least.