Summary
| Disposition | Commenter satisfied | Commenter not satisfied |
|---|---|---|
| TF accepted comment | 3 | 0 |
| TF partially accepted comment | 2 | 0 |
| TF rejected comment | 2 | 0 |
Disposition was measured in the Task Force by responses to a WBS Survey.
Detailed Description of Comments
23287 - strengthen requirement for user access to longdesc
- First recorded: 2013-07-16
- BUG 23287
- Last modified: 2014-01-13
- Guy,
Thanks for your feedback. The Task Force has considered your suggestion to more explicitly define the behavior requirements on User Agents for accessing longdesc. We agree that discoverability is a key component in the success of longdesc, which is why we listed it in the Requirements section. However, the Task Force has decided to allow User Agents the flexibility to develop innovative solutions for users to discover and interact with longdesc content. There are known implementation strategies that would not meet the restriction you suggested in your comment, such as that used by the TellMeMore extension, or the ability to provide the description directly in a "popup window". Innovative solutions such as these would not be possible if the specification required any particular solution. - Review Status:
- Change declined
- Commenter Accepted
23288 - Reference for Authoring and Repair
- First recorded: 2013-07-16
- BUG 23288
- Last modified: 2014-01-13
-
added more precise references to relevant sections of ATAG in Requirements section, specifically: * Appendix A-3: Long text descriptions * Appendix B: Levels of Checking Automation * Appendix C: Levels of Repair Automation Changeset: https://dvcs.w3.org/hg/html-proposals/rev/145e07b3f468 Email Reply to Jan: http://lists.w3.org/Archives/Public/public-html-a11y/2013Dec/0046.html - Review Status:
- Change accepted
- Commenter Accepted
23291 - Add statements about when longdesc is inappropriate
- First recorded: 2013-07-16
- BUG 23291
- Last modified: 2014-01-13
-
added to the Authoring Requirements section: > Authors SHOULD NOT rely solely on longdesc where standards exist to provide direct, structured access. > Note: (informative) For example a MathML version of mathematical content, or an SVG image that uses the accessibility features of SVG, can provide better accessibility to users with appropriate technology. In such cases, it is appropriate to use longdesc as a fallback strategy, in combination with more modern techniques. Changeset: https://dvcs.w3.org/hg/html-proposals/rev/8d7c0e2d97d4 Email reply to James and Matt: http://lists.w3.org/Archives/Public/public-html-a11y/2013Dec/0045.html - Review Status:
- Change Accepted
- Commenter Accepted
23293 - Require descriptions which are not whole documents to be well-formed fragments
- First recorded: 2013-07-23
- BUG 23293
- Last modified: 2014-01-13
-
Andrew,
Thanks for taking the time to consider longdesc in the context of specific WCAG techniques, specifically the behavior of user agents when a longdesc refers to a document fragment. The Task Force has intentionally refrained from requiring any specific behavior in this respect from user agents. There is a requirement in the document that authors SHOULD put descriptions in well-formed fragments (which may include an entire page). Because there is existing, and will likely continue to be new content that does not meet this requirement, we do not propose a corresponding requirement on user agents. - Review Status:
- Change Declined
- Commenter Accepted - Reference Needed
23289 - Suggested editorial fixes from EOWG
- First recorded: 2013-09-16
- BUG 23289
- Follow-up: 2014-01-21
- Last modified: 2014-06-13
-
* Added text to the Introduction section that more clearly defines the longdesc attribute https://dvcs.w3.org/hg/html-proposals/rev/7e746d7c4194 * clarified linking to a fragment link https://dvcs.w3.org/hg/html-proposals/rev/8819e0678108 * changed human consumption to humans https://dvcs.w3.org/hg/html-proposals/rev/1cc33f01787e * made capitalization of headings consistent throughout document https://dvcs.w3.org/hg/html-proposals/rev/d43c6656524b * editorial changes to Conformance section https://dvcs.w3.org/hg/html-proposals/rev/b7ad741c26e5 * clarified scope of normative text in conformance section https://dvcs.w3.org/hg/html-proposals/rev/abeb3c959d45 * changed localized to translated https://dvcs.w3.org/hg/html-proposals/rev/fd6cee5efc3f * linked use case references to definitions, made case consistent and ordered definitions in alpha order https://dvcs.w3.org/hg/html-proposals/rev/c8da8ec4a07b * removed "title" attribute from example https://dvcs.w3.org/hg/html-proposals/rev/6ddbb6ab517c * removed "Note that" text from Abstract and Section 3 https://dvcs.w3.org/hg/html-proposals/rev/f4d139c52636 * removed "Note that" text from Abstract and Section 3 https://dvcs.w3.org/hg/html-proposals/rev/f4d139c52636
http://lists.w3.org/Archives/Public/public-html-a11y/2014Jun/0039.html* changed reference to WCAG to describe terms accessible and accessibility per comments from EOWG https://dvcs.w3.org/hg/html-proposals/rev/f4d139c52636 - Review Status:
- Change Partially Accepted
- Commenter Accepted
23290 - Additional use case for discoverability of long descriptions
- First recorded: 2013-09-16
- BUG 23290
- Last modified: 2014-01-13
-
We agree that additional use cases that demonstrate a need for discoverability should be added to this specification. We have added the following addition to the "Use Cases" section: Image Search Many search engines provide an option to search for images and present the results out of context. The ability to discover and process identified descriptions allows search engines to improve the source material they use to support text-based queries for images. Describing Images Image search tools identify multiple copies of the same image. Where a search tool can identify a description of an image, this can be provided to the user as a description for any copies of that image. Changeset73: https://dvcs.w3.org/hg/html-proposals/rev/f33a6fab75ed - Review Status:
- Change Accepted
- Commenter Accepted
26086 - UAWG comments on the HTML5 Image Description Extension
- First recorded: 2014-01-23
- BUG 26086
- Last modified: 2014-06-13
- Review Status:
-
We have accepted some changes, and did not make others where we had already reached compromises based on tension in either direction. More detailed explanation in our reply http://lists.w3.org/Archives/Public/w3c-wai-ua/2014AprJun/0063.html - Change Partially Accepted Email response (2014-06-13)
- Commenter Satisfied