- From: Sam Ruby <rubys@intertwingly.net>
- Date: Tue, 10 Sep 2013 20:05:48 -0400
- To: Robin Berjon <robin@w3.org>, Charles McCathie Nevile <chaals@yandex-team.ru>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, "Michael(tm) Smith (mike@w3.org)" <mike@w3.org>, "public-html-admin@w3.org" <public-html-admin@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, "team-html-a11y@w3.org" <team-html-a11y@w3.org>, W3C WAI Protocols & Formats <w3c-wai-pf@w3.org>
On 09/10/2013 07:36 PM, Janina Sajka wrote: > Dear All: > > I'm very disappointed to note that longdesc is still listed in the > obsolete (Sec. 11) of the HTML 5.1 nightly. Is this also the case with > the current crop of heartbeats? > > Surely everyone is aware that the TF's longdesc extension Las Call > expires Monday next? > > Can we please, please have this resolved immediately? As agreed? I encourage you to write a bug report. I'm confident that such will be handled appropriately. As to what we agreed to previously, here is what plan 2014 states: If such a specification obtains consensus and meets the proposed CR exit criteria by 2014Q2 it could be folded back into the core HTML spec by that time. http://dev.w3.org/html5/decision-policy/html5-2014-plan.html > Janina - Sam Ruby > Janina Sajka writes: >> Hi, Robin: >> >> Robin Berjon writes: >>> Hi Janina, >>> >>> On 24/05/2013 18:12 , Janina Sajka wrote: >>>> I will withdraw my objection at this time in the interest of preserving >>>> and furthering the comity that has arisen among us since Plan 2014. >>> >>> Thank you. >>> >> Well, it's not my intent to throw a major monkey-wrench into the works. >> Perhaps we should have inquired about prioritization and communicated >> our expected timelines before. >> >>>> While I do not think anyone is intentionally delaying here, continued >>>> delay does exaserbate W3C accessibility messaging. Also, we're now >>>> quite likely to have a Last Call for HTMl Image Description published before >>>> another HTML heartbeat is published. >>> >>> What is your time frame for LC? We're not really constrained as to >>> the minimal amount of time between heartbeats. >>> >> We're expecting LC late June. We further expect to prepare our CR >> implementation report during LC, so that we may well go to PR late >> August/early September, skipping CR. >> >>>> Is there any reason it's unreasonable to expect this bug to be resolved >>>> before the NEXT publication milestone? >>> >>> No, I wouldn't think so. As I said, it hasn't been handled either >>> high or low priority. I (and as far as I know, the other editors >>> too) tend to proceed by fixing blocks of bugs that are on related >>> topics. We can certainly handle this bug soon. >>> >> Thanks, Robin. That would be helpful. >> >> Janina >> >>> -- >>> Robin Berjon - http://berjon.com/ - @robinberjon >> >> -- >> >> Janina Sajka, Phone: +1.443.300.2200 >> sip:janina@asterisk.rednote.net >> Email: janina@rednote.net >> >> Linux Foundation Fellow >> Executive Chair, Accessibility Workgroup: http://a11y.org >> >> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) >> Chair, Protocols & Formats http://www.w3.org/wai/pf >> Indie UI http://www.w3.org/WAI/IndieUI/ >> >
Received on Wednesday, 11 September 2013 00:06:18 UTC