- From: Judy Brewer <jbrewer@w3.org>
- Date: Fri, 29 Jun 2007 09:55:01 -0400
- To: EOWG <w3c-wai-eo@w3.org>
This is a draft wrap up of our comments from our past several weeks of our discussion. For the purposes of this draft, I have left in the link to the record of our discussion, but would leave it out in the actual comments submission. Also I would be cleaning up the capitalization and punctuation, etc. The comments are taken from the following week's action item summaries: http://www.w3.org/2007/06/08-eo-minutes#ActionSummary http://www.w3.org/2007/06/15-eo-minutes#ActionSummary http://www.w3.org/2007/06/22-eo-minutes#ActionSummary In addition, I have left a batch of other related action items from these three weeks, where in some cases we had wanted to come back and work more on certain items but had not been able to do so yet. Regards, - Judy DRAFT COMMENTS: - [conformance section] EOWG feels that the goal for the section on accessibility supported technologies should be that the average developer should be able to read the section and understand the concept; understand the importance of the concept; and understand that you should be able to go to a list of accessibility supported technologies. [recorded in http://www.w3.org/2007/06/08-eo-minutes.html#action09] - [conformance section] explain clearly & simply, as part of the introductory paragraph, that some technologies support assistive technologies, and these are the ones that you should use. [recorded in http://www.w3.org/2007/06/08-eo-minutes.html#action04] - [conformance section] in first paragraph of "accessibility support of web technologies" please add "web" in front of the two uses of "technologies" that do not currently have any other descriptor. [recorded in http://www.w3.org/2007/06/08-eo-minutes.html#action05] - [conformance section] please be sure to present the reader with a clear & preferably simple statement or definition of what accessibility supported technologies are, before telling us when/where they need to be used, and that the author must use them. right now the definition is doubly embedded in two other concepts in the intro paragraph. [recorded in http://www.w3.org/2007/06/08-eo-minutes.html#action02] - [conformance section] please be sure to present the reader with a short description of what accessibility supported technologies are, before telling us when/where they need to be used, and that the author must use them. right now the definition is doubly embedded in two other concepts in the intro paragraph. [recorded in http://www.w3.org/2007/06/08-eo-minutes.html#action03] - [conformance section] take the sentence about what this section covers and put it at the very beginning of the section; then give the short version of what conformance means; then say it's normative; then make sure that the promised sequence matches the actual sequence. [recorded in http://www.w3.org/2007/06/08-eo-minutes.html#action01] - [conformance section] the reason for the previous request is to clearly separate reference to the authors' (Web) technologies from reference to the users (assistive) technologies; and we suggest that this differentiation be checked throughout the document. [recorded in http://www.w3.org/2007/06/08-eo-minutes.html#action06] - [principle 1] "'Perceivable'" is neither explained, nor defined here, nor is there a link to an explanation or a definition. Where it is introduced in the introduction, the explanation is brief, and not linked to the expanded explanation in the "Understanding" document. Please explain, or define, or link to such information. [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action11] - [reference] The current draft uses inconsistent terminology for conformance levels (see the intro, then the conformance referencing section). Please synchronize. [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action05] - [referencing: support documents] This section needs simplification and copyediting to clarify the meaning and eliminate redundancies; also, it should be included in the supporting documents. [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action09] - [referencing] Add "or must" after "shall" [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action02] - [referencing] After "this is informative," add "Please note that the following language for referencing WCAG 2.0 can be inserted into your own documents." [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action01] - [referencing] If maintaining that all of Level 3 should not be required, a better explanation is needed for this. [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action10] - [referencing] Please simplify "That is, it is possible to require "all of Level 1 and [some specific list of success criteria in Level 2 and Level 3]" be met" by turning it into an example, e.g.: "For example, 'all of Level 1 and [some specific list of success criteria in Level 2 and Level 3].'" [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action06] - [referencing] The 4th subprovision under the "shall" section contradicts the third example, in that it implies that one can require conformance to all Level 3 success criteria. [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action07] - [SC 1.1.1] Flip the sentence from existing to: "If non-text content is any of the following, then text alternatives at least identify the non-text content with a descriptive text label: multimedia, live audio-only or live video-only content, a test or exercise that must be presented in non-text format, or primarily intended to create a specific sensory experience." [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action12] - [guideline 2] the difference between 2.2.2 (blinking) and 2.3.1 (flashing) is not clear even with the links to definitions, as the definitions are mutually self-referencing and seem just like different degrees of the same thing. either differentiate more in the SC themselves, or combine them. [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action07] - [SC 1.2.1] Replace "multimedia alternative to text" with "audio and/or video alternative to text" since it is possible to gloss text w/ audio only, or w/ silent video only (for instance, sign language) or w/ audio & video together (e.g. video of talking head). [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action08] - [SC 1.3.1] What does this mean? Most of us had no idea, and the few who did had difficulty explaining what the practical implications of this would be for content development. Do you mean "semantics conveyed through presentation?" Or is it the semantics about the relation between objects? Either one of these, or both, would be more understandable. [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action09] - [SC 2.4.2] Do you mean the title tag or the title that goes in the H1? Please clarify (even if in some non-HTML specific way). [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action10] - [SC 3.1.4] We debated this but could not agree on a common interpretation. What do you mean? [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action11] - [gloss-assistivetech] drop note 1 [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action05] PENDING ACTIONS: - [essential components] re-check at some point in future to see if the concept of accessibility supported technologies should be added anywhere. [recorded in http://www.w3.org/2007/06/08-eo-minutes.html#action08] - EOWG revisit choosing web technologies, and explanation of accessibility supported technologies [recorded in http://www.w3.org/2007/06/08-eo-minutes.html#action07] - EOWG revisit possible redundancies or "shouldn't-this-be-in-the-guidelines-section-ness" of items 5 and 6 in the conformance requirements section. [recorded in http://www.w3.org/2007/06/08-eo-minutes.html#action10] - EOWG: come back to the intro of the referencing section and suggest a clarification that the "requiring" is by other organizations, not by w3c/wai [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action03] - JB ask them to clarify their intent abt level 3 [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action08] - JB check w/ WCAG WG Co-Chairs on what their intent was in the "referencing" section. [recorded in http://www.w3.org/2007/06/15-eo-minutes.html#action04] - wayne's redef: drop last sentence of first paragraph [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action01] - wayne's redef: remove "stand alone and" [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action03] - wayne's redef: remove note 3 [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action06] - wayne's redef: remove the entire sentence starting with "In either case,..." [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action04] - wayne's redef: still need to revise "In this definition, mainstream user agents denote user agents in the familiar sense of the term" -- does not work. [recorded in http://www.w3.org/2007/06/22-eo-minutes.html#action02] -- Judy Brewer +1.617.258.9741 http://www.w3.org/WAI Director, Web Accessibility Initiative (WAI), World Wide Web Consortium (W3C) MIT/CSAIL Building 32-G526 32 Vassar Street Cambridge, MA, 02139, USA
Received on Friday, 29 June 2007 13:54:24 UTC