<Audio> element format support 
This table documents the current support for audio codecs by the
|Browser||Operating system||Formats supported by different web browsers|
|Ogg Vorbis||WAV PCM||MP3||AAC||WebM Vorbis||Ogg Opus|
|Google Chrome||All supported||9||Yes||Yes||Yes||Yes||25|
|Mozilla Firefox||All supported||3.5||3.5||21.0, Windows only||21.0, Windows only||4.0||15.0|
The adoption of HTML5 audio, as with HTML5 video, has become polarized between proponents of free and patented formats. In 2007, the recommendation to use Vorbis was retracted from the specification by the W3C together with that to use Ogg Theora, citing the lack of a format accepted by all the major browser vendors.
Apple and Microsoft, which between them account for around 39% of the browser market, support the ISO/IEC-defined formats AAC and the older MP3. They  [ambiguous] and the risk of a submarine patent attack from formats which are believed, but not guaranteed, to be “free”.
Mozilla and Opera, controlling 24% of the market, support the free and open, royalty-free Vorbis codec in Ogg and WebM containers, and criticize the patent-encumbered nature of MP3 and AAC, which are guaranteed to be “non-free”.
Google, controlling 27% of the market, has so far provided support for all common formats.
The result is that for a website to guarantee HTML5 audio for all the above browsers, it has to make two formats available: Vorbis, and either MP3 or AAC.
Web Audio APIs 
The W3C Audio Working Group is also considering the MediaStream Processing API specification developed by Mozilla. In addition to audio mixing and processing, it covers more general media streaming, including synchronization with HTML elements, capture of audio and video streams, and peer-to-peer routing of such media streams.
Speech API 
The Speech API aims to provide an alternative input method for web applications (without using a keyboard). With this API, developers can give web apps the ability to transcribe your voice to text, from your computer's microphone. The recorded audio is sent to speech servers for transcription, after which the text is typed out for you. The API itself is agnostic of the underlying speech recognition implementation and can support both server based as well as embedded recognizers.  The HTML Speech Incubator group has proposed the implementation of audio-speech technology in browsers in the form of uniform, cross-platform APIs. The API contains both:
- Speech Input API
- Text to Speech API
Google integrated this feature into Google Chrome on March 2011. Letting its users search the web with their voice with code like:
See also 
- Chris Rogers (2012-03-15). "Web Audio API". W3C. Archived from the original on 2012-03-15. Retrieved 2012-07-04.
- Scott Gilbertson (2011-09-19). "Chrome 14 Adds Better Audio, ‘Native Client’ Support". Webmonkey. Wired. Retrieved 2012-07-04.
- "Audio Data API".
- "Introducing the Audio API extension". Mozilla Developer Network. Mozilla. 2012-03-05. Archived from the original on 2012-03-05. Retrieved 2012-07-04.
- "Audio Processing API". W3C. 2011-12-15. Archived from the original on 2011-12-15. Retrieved 2012-07-04.
- Robert O'Callahan (2012-05-31). "MediaStream Processing API". W3C. Retrieved 2012-07-04.
- "API draft". Retrieved January 28, 2012.
- "HTML5 Speech API". Retrieved January 28, 2012.
- "Talking to your computer". Retrieved January 28, 2012.