[Commentor] LC-2637 Doug Schepers (archived comment) [Comment] == Video and Audio == http://www.w3.org/TR/2012/WD-html-media-capture-20120712/#attributes The 'camcorder' keyword value may conflate video and audio; I can credibly see a use-case for video-only capture, and user expectation may be ambiguous if that's not called out explicitly when they are selecting their input (e.g. they may be unpleasantly surprised when they accept a video source and their audio is also captured). The user may also wish to select a different microphone input than is bundled with the videocamera. I suggest that the value of @capture should be a list of strings, not just a single value, i.e. This may result in a pair of source selections, sequentially selecting first the videocamera input, then the microphone input (or, depending on the UA and device, might have both in the same dialog... either way, it should be explicit). [Commentor reply] yes [Working Group decision] 
No change needed: The accept attribute takes precedence over the capture attribute as per the spec. This means camcorder+audio would be the same as no capture attribute is present if the implementation's video camera control is unable to capture audio only. If the implementation's video camera control is able to capture audio only (in addition to video), then camcorder+audio and microphone+audio would yield similar results i.e. an audio file. http://lists.w3.org/Archives/Public/public-device-apis/2012Aug/0101.html