- From: Sam Ruby <rubys@intertwingly.net>
- Date: Tue, 28 Feb 2012 08:36:18 -0500
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- CC: public-html@w3.org
On 02/28/2012 07:53 AM, Laura Carlson wrote: > >> You are asking that ISSUE-30 be re-resolved before Jonas and/or Matthew have >> completed their proposal(s). > > No, Sam I am not. I am asking for ISSUE-30 to be resolved before > publishing yet another draft. If also you want to resolved other > issues prior to publishing another draft that is your prerogative. Jonas's proposal was originally against ISSUE-30. We identified significant problems with the original proposal, and Jonas has indicated that he intends to address them. >> Can you explain the importance of what might very well be a temporary >> resolution of this issue would be? > > It would not be temporary if you resolve 204 first. Should Jonas submit a proposal for 204, would anybody here appreciate an opportunity to submit a counter proposal? > The importance of all of this is that longer longdesc is obsolete, the > more people will not use it or stop using it. It discourages and > deters uptake. I have collected a non-negligible number of examples > [1] that utilize longdesc in meaningful ways. However, delay is eating > way evidence. I have to remove examples weekly. People read that > longdesc is obsolete...so why use it? > > For instance, a page on about.com says, "The LONGDESC attribute allows > you to put a URL to a longer description of the image. This attribute > is obsolete in HTML5. You should use a normal A tag to link to a > longer description instead. This attribute is valid HTML4, and is not > deprecated in that version." [2] Jennifer Kyrnin has been contacted > numerous times (starting last June) informing her that longdesc is > currently an open issue in the W3C HTML5 Working Group and a change > proposal has been written, which the HTML5 Accessibility Task Force > supports. It would make longdesc conforming. She has been asked if she > could please update the text on her page to say that longdesc in HTML5 > is currently an open issue. She said she would but never has. The text > remains. Do you have evidence that she will updated it based on the publishing of a heartbeat draft? Again, I will point out that no matter what a heartbeat draft might say, the issue will remain open until everybody has an an adequate opportunity to make their case and provide their rebuttals. I will note that heartbeat documents prior to Last Call had issue markers. Would that suffice? > Every beat of HTML5's heart without longdesc, suffocates longdesc more. > > Best Regards, > Laura > > [1] http://www.d.umn.edu/~lcarlson/research/ld.html#wild > [2] > http://webdesign.about.com/od/beginningtutorials/a/image_tag_img.htm - Sam Ruby
Received on Tuesday, 28 February 2012 13:36:54 UTC