- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Thu, 29 Mar 2012 13:56:57 -0700
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
On Thu, Mar 29, 2012 at 9:45 AM, Janina Sajka <janina@rednote.net> wrote: > Colleagues: > > On 29 March last the HTML-A11Y Task Force teleconference meeting > reached consensus as follows: > > RESOLUTION: The HTML-A11Y Task Force confirms that ARIA-DescribedAT will > not be ready for HTML 5 in HTML 5's currently published timeframe, and > therefore reaffirms its support of Laura's authored CP to reinstate > longdesc (Issue-30). > > The TF resolution, together with minutes of the discussion leading up to > it, is logged at: > http://www.w3.org/2012/03/29-html-a11y-minutes.html#item03 > > As usual, if there is objection to this consensus position, please > respond by replying to this message no later than close of business, > Boston Time, on Monday 2 April. I have two comments on this: Laura's change proposal [1] asks for @longdesc to be reinstated for <img> elements. @longdesc is currently an obsolete attribute [2] for both, <img> and <iframe>. First a question: we are not asking @longdesc to be reinstated for <iframe>, or are we? And: why not? Secondly my opinion: if we are not planning to introduce a @aria-describedAt attribute into HTML5, we should drop issues 194 [3] and 203 [4] and defer them to HTML.next. I don't want to see the problem of long descriptions / transcripts solved for <video> elements in isolation from other elements. It would make more sense to have a common solution on all elements. Regards, Silvia. [1] http://www.w3.org/html/wg/wiki/ChangeProposals/InstateLongdesc [2] http://www.w3.org/TR/html5/obsolete.html#non-conforming-features [3] http://www.w3.org/html/wg/tracker/issues/194 [4] http://www.w3.org/html/wg/tracker/issues/203
Received on Thursday, 29 March 2012 20:57:45 UTC