21571 2013-04-03 15:29:23 +0000 The sub-sentence "but there are many resources available" etc. 2013-05-01 10:04:03 +0000 1 1 1 Unclassified HTML WG HTML Image Description Extension unspecified PC All RESOLVED FIXED https://dvcs.w3.org/hg/html-proposals/raw-file/0dd2e510d4e1/longdesc1/longdesc.html a11y, a11y_text-alt P2 normal --- 1 xn--mlform-iua chaals hans.hillen public-html-admin xn--mlform-iua public-html-bugzilla oldest_to_newest 85502 0 xn--mlform-iua 2013-04-03 15:29:23 +0000 Is the sub-sentence "but there are many resources available" really any useful - in a spec? Would it not be better to either skip that sub-sentence or to provide examples of some of these many resources or at least point to where to look for them? I feel that "full descriptions of images" may have to do the narrative, so to speak. I don't know enought about WCAG 2 to say whether it gives adequate guidance about image descriptions. Also, in the next paragraph, you point to WCAG, for a definitinon of 'accessible'. And I wonder if all readers will understand the difference between the 'narrative' issue and and the accessible issue, unless it is clarified more. PS: What I had in mind, originally, in bug 21437, was the (file) format of the description. I feel that a reference to http://www.w3.org/TR/WCAG20/#guidelines, like I propose the fift comment of that bug (https://www.w3.org/Bugs/Public/show_bug.cgi?id=21437#c5) would cover file format issues well enough simply because what I am after is a quick way to verify unintended and very suboptimal use of @longdesc. But technically, it seems to be the robustness princple I care the most about: http://www.w3.org/TR/WCAG20/#robust ("Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. Guideline 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.") I wonder if 'full descriptions of images' falls in under 'Perceivable' and 'Undertandable'. 87083 1 chaals 2013-05-01 10:04:03 +0000 The text has been edited, and the TF has agreed that the bug is now resolved.