13440 2011-07-28 22:11:01 +0000 Editorial changes to Track element (3 of 3) 2011-08-15 05:44:00 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Windows XP RESOLVED FIXED http://www.w3.org/TR/2011/WD-html5-20110525/the-iframe-element.html#the-track-element a11y, a11ytf P2 normal --- 1 jfoliot ian ian laura.lee.carlson mike philipj public-html-a11y public-html-admin public-html-wg-issue-tracking silviapfeiffer1 public-html-bugzilla oldest_to_newest 51707 0 jfoliot 2011-07-28 22:11:01 +0000 current text:(from the @kind table) keyword: descriptions "Textual descriptions of the video component of the media resource, intended for audio synthesis when the visual component is unavailable (e.g. because the user is interacting with the application without a screen while driving, or because the user is blind). Synthesized as separate audio track." recommended change: "Textual descriptions of the video component of the media resource, intended for audio synthesis when the visual component cannot be perceived (e.g. because the user is blind or visually impaired) or the visual component is unavailable (e.g. because the user is interacting with the application eyes-off or without a screen). Synthesized to audio by a screen reader or other audio synthesis system." filed on behalf of the a11yTF 52545 1 mike 2011-08-04 05:02:28 +0000 mass-moved component to LC1 54529 2 ian 2011-08-10 01:19:38 +0000 Can you clarify what problem this is solving? (Just proposing new text makes it impossible for me to determine if the problem is endemic (requiring more changes than you realise), or whether what I think of as mistakes in the new proposed text are intentional or not (and should be fixed or not), or whether stylistic differences are intentional or not, etc.) 54534 3 silviapfeiffer1 2011-08-10 01:28:54 +0000 (In reply to comment #2) > Can you clarify what problem this is solving? (Just proposing new text makes it > impossible for me to determine if the problem is endemic (requiring more > changes than you realise), or whether what I think of as mistakes in the new > proposed text are intentional or not (and should be fixed or not), or whether > stylistic differences are intentional or not, etc.) So, to give you some context: the editorial changes that John registered were all feedback on the spec text from a person in the a11y industry. Some of these changes are just about getting the text politically right, so they include the right people and don't offend anyone. This proposed change is just that: telling a blind person that their visual component is unavailable is just not the right thing to do. Further, the change to the last sentence is about making sure it is understood that textual descriptions don't result in a multitrack resource (with a separate audio resource), but rather that the synthesized audio comes from another system. 55046 4 ian 2011-08-15 05:42:35 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: see comment 3. 55047 5 contributor 2011-08-15 05:44:00 +0000 Checked in as WHATWG revision r6459. Check-in comment: improved precision in wording http://html5.org/tools/web-apps-tracker?from=6458&to=6459