Media Requirements - 3.6 Requirements on making properties available to the accessibility interface.

Requirements on making properties available to the accessibility interface
(8 comments) 
http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Requirements#Requir
ements_on_making_properties_available_to_the_accessibility_interface
http://www.w3.org/2002/09/wbs/44061/20080526_media-requirements/results#xq
16 

Explanatory Text: Recommendation is to re-word to the following:
"For players running on platforms that support an accessibility API any
media controls need to be connected to that API."

To: 
"For User Agents supporting accessibility APIs implemented for a platform,
any media controls need to be connected to that API."


(API-1) - Support to expose the alternative content tracks for a media
resource to the user, i.e. to the browser.

Recommendation to reword as follows:
"The existence of Alternative Content tracks for a media resource must be
exposed to the User Agent."

(API-4) External control devices, such as remote controls, need to be
enabled to access alternative content tracks, too. 

Recommendation is to remove from Requirements Document as this is a User
Agent Device Requirement, while recognizing that this is an important
requirement, the HTML5 specification should be device agnostic.

John Foliot / Eric Carlson

Received on Friday, 2 July 2010 02:07:30 UTC