- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Wed, 19 Sep 2012 16:56:42 +0200
- To: Sam Ruby <rubys@intertwingly.net>
- Cc: Laura Carlson <laura.lee.carlson@gmail.com>, James Craig <jcraig@apple.com>, Cynthia Shelly <cyns@microsoft.com>, David Bolter <david.bolter@gmail.com>, Ian Hickson <ian@hixie.ch>, public-html-a11y@w3.org
Sam Ruby, Wed, 19 Sep 2012 10:02:30 -0400: > I will first note that you are not likely to get a straight answer to > the first question -- pre-announcing support for features before they > are implemented is rarely a successful strategy. 'pre-announcing' ... ... > I will close this email by noting that David Bolter previously > participated in this discussion[7], and perhaps the points that he > made at that time should be discussed. > > You might be pleased to see that he seems to agree with you that this > should not be implemented in ARIA. > [7] http://lists.w3.org/Archives/Public/public-html-a11y/2012Mar/0405.html Thank you for pointing to David's message. Clearly, name change might be a better idea than we have admitted. In that case, a logical 'deal' to consider, could be to make @longdesc obsolete but conforming as long as its value would have the same meaning/value as "@duck_soup". HTML5 contains similar 'deals' for some of the obsolete but conforming feature. [1] And for @maxlength and @size it uses back-compatibilty as argument. [1] http://dev.w3.org/html5/spec/obsolete.html#obsolete-but-conforming-features -- leif h silli
Received on Wednesday, 19 September 2012 14:57:20 UTC