- From: Paul Cotton <Paul.Cotton@microsoft.com>
- Date: Thu, 10 Jul 2014 15:52:06 +0000
- To: Janina Sajka <janina@rednote.net>, Judy Brewer <jbrewer@w3.org>
- CC: "public-html-a11y@w3.org" <public-html-a11y@w3.org>
- Message-ID: <2e32c3d0b2204a32b66f27bcf6735688@BL2PR03MB418.namprd03.prod.outlook.com>
On today's A11Y TF call we briefly discussed the processing of the "Media Accessibility User Requirements" document: https://rawgit.com/w3c/pfwg/master/media-accessibility-reqs/index.html Here are some minor editorial comments. 1. Editorial comment: The Abstract states: "This document is most explicitly not a collection of baseline user agent or authoring tool requirements. It is important to recognize that not all user agents (nor all authoring tools) will support all the features discussed in this document. Rather, this document attempts to supply a comprehensive collection of user requirements needed to support media accessibility in the context of HTML5. As such, it should be expected that this document will continue to evolve for some time." which seems to contradict the following text in the SOTD: "This document is reasonably stable, and represents a consensus within the Working Group. The Working Group is looking for feedback prior to publication as a Note." 2. Editorial comment: "Such illustrations must be programatically discoverable by users" Change "programatically" to "programmactically" and make this change globally. 3. Editorial comment "[T-2] Support the provisioning of both scrolling and static display of a full text transcript with the media resource, e.g., in a area next to the video or underneath the video, which is also AT accessible." Change "in a area" to "in an area". 4. Editorial comment "[IC-3] All functionality available to native controls must also be available to scripted controls. The author would be able to choose any/all of the controls, skin them and position them." Should "skin" be changed to "skip"? 5. Editorial comment "[IC-5] The scripted and native controls must go through the same platform-level accessibility framework (where it exists), so that a user presented with the scripted version is not excluded from participting in or experiencing some expected behaviour." Change "participting" to "participating". 6. Editorial comment "This could be enabled through encouraging publishers to use @autoplay, encouraging UAs to implement accessibility settings that allow to turn off all autoplay, and encouraging AT to implement a shortcut key to stop all autoplay on a web page." Change "that allow to turn off" to "allow turning off". 7. Editorial comment "[VP-5] Captions and subtitles traditionally occupy the lower third of the video, where controls are also usually rendered. The user agent must avoiding overlapping of overlay content and controls on media resources. This must also happen if, for example, the controls are only visible on demand." Change "must avoiding" to "must avoid". /paulc Paul Cotton, Microsoft Canada 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 Tel: (425) 705-9596 Fax: (425) 936-7329
Received on Thursday, 10 July 2014 15:52:47 UTC