Feedback on 3 Jan 2012 draft of Media Accessibility User Reqs

Sorry for the delayed response. Most feedback is editorial unless marked SUBSTANTIVE. Hopefully the version is still relevant.

James


2.7 Physical Impairment:
sub "assistive-technology access" with "assistive technology"

2.8 Cognitive and…:
"called learning disabilities in some regions"
"called learning disabilities in other regions"
Why the different uses?

3.2 Text Video Description.
SUBSTANTIVE: If TVD is only a second audio track, the fact that it's TVD must be programmatically determinable. 

3.2 Text Video Description. [TVD-2]
sub "Speech CSS" with "CSS 3 Speech Module"

3.4 Clean audio
I'd expect the same note here as the one in the EVD section, "Note that this is an advanced feature and…"

3.5 Content Navigation.
The paragraph that immediately follows the first bulleted list includes a lot of statements about DOM that seem misplaced. Is the author using this term synonymously with the terms "structural" or "hierarchical"? If so, it'd be better to use one or those terms. If not, the reference to DOM is unclear and this paragraph could be rewritten.

3.6 Captioning [CC-13]
SUBSTANTIVE: "Where a background is used, it is preferable to keep the caption background visible even in times where not text is displayed…" The first half is a subjective statement presented as fact, and the second half is ambiguous: "where captions are *infrequent* (according to whom)" I'd suggest striking any subjective ambiguities unless backed up with document research and references.

3.6 Captioning [CC-20]
sub "l18n" with "localization" or "localisation", but not the abbreviated, geeky term.
sub "pronunciation correct" with "correct pronunciation"

3.6 Captioning [CC-21]
SUBSTANTIVE: Incomplete? This section appears to be missing some bullet points.

3.7 Enhanced captions/subtitles
sub "to accessibility users" with "to users of assistive technology"
sub "term that needs a link for Wikipedia definition" with "term that needs a link for definition" (reference to Wikipedia unnecessary.)

3.7 Enhanced captions/subtitles [ECC-2]
sub "<a> elements and buttons" with "links and buttons"
"One needs to deal here…" sentence obviously unfinished.

3.7 Enhanced captions/subtitles [ECC-4]
Vague: "This could be realised through a hint on the text cue or even the whole track."

3.8 Sign Translation. Para 2.
The reference to "alpha-blending technology" is unnecessary. People understand "picture-in-picture" so I'd stick with that term.

3.8 Sign Translation. [SL-3]
Ditto on the "alpha-blended overlay". 
SUBSTANTIVE: The suggestion to have multiple videos play in sync requires some additional support in HTML5.

4.1 [KA-1] 
Define "unique focus object"

4.1 [KA-3] 
SUBSTANTIVE: I would include that the requirement be that controls must not only be scriptable, but the playback mechanism must be able to react to AT-triggered control of the media track. (Indie UI may apply here.)

4.1 [KA-6] Note
sub "us @autoplay" with "use @autoplay"

4.4 [PP-4]
sub "Web page author" with "web page author" (Web not capitalized when used as adjective; only capitalized when used as proper noun, e.g. "The World Wide Web" or "pages on the Web" but not "web pages.")

4.5 Para 1.
sub "Web mechanism" with "web mechanism"

4.7 [VP-1] Note
sub "Web page" with "web page" (two instances)