W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2012

Re: 48-Hour Consensus Call: InstateLongdesc CP Update

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Sun, 16 Sep 2012 10:31:40 +0100
Message-ID: <CA+ri+VnM7kKUqoX_uHvtYmNSgLBNrfVh+dmdbYuMkJ+=NF0jWA@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hi all,

I abstain from this CFC.

I have made my antipathy towards longdesc clear in the past, the
majority ( i think) of the taskforce can live with longdesc back in
the spec or not in the spec. I could live with it back in the spec, I
could live with it not in the spec.

There are  substandard features in the spec, there are features that
are not yet supported, there are features that not yet accessibility
supported.  if longdesc is put back in the spec i would consider it
appropriate to have a warning about its use. I would consider it  a
feature at risk CR wise unless its interoperable support in browsers
is improved. I would consider it a failed feature unless it is
meaningfully supported across the major browsers and AT. i.e. if
browsers such as IE and webkit based browsers, and AT such as
voiceover and NVDA do not implement meaningfull support for it.


On 13 September 2012 18:10, Janina Sajka <janina@rednote.net> wrote:
> Colleagues:
> The HTML-A11Y Task Force has twice resolved support for the InstateLongdesc
> Change Proposal on Issue-30 Longdesc reconsideration, most recently as
> logged at:
> http://lists.w3.org/Archives/Public/public-html-a11y/2011May/0399.html
> http://www.w3.org/html/wg/wiki/ChangeProposals/InstateLongdesc
> As we expect reconsideration of the Issue-30 decision on longdesc will
> be taken up by the HTML-WG soon, the Task Force Text Subteam has
> provided a narrative wrapper for this CP which is intended to serve as
> concise orientation at the top level of
> the CP, leaving detailed evidence and argument to subpages.
> http://www.w3.org/html/wg/wiki/Talk:ChangeProposals/InstateLongdesc
> The Task Force teleconference on 13 September reviewed this approach for
> the second time and confirmed no objections to it:
> http://www.w3.org/2012/09/13-html-a11y-minutes.html#item02
> As was noted during the teleconference, the Instatelongdesc CP had this
> kind of top level presentation until the evidence in the CP became so
> extensive that it seemed prudent to reformat the CP using subpages.
> The discussion page to review is at:
> http://www.w3.org/html/wg/wiki/Talk:ChangeProposals/InstateLongdesc
> If you have objections, comments, or proposed edits, please respond by
> replying to this message no later than 12:00 PM (Noon), Boston Time, on
> Tuesday 18 September. This is 16:00 UTC.
> All Task Force participants are also invited to attend the Task Force
> Text Subteam teleconference at 1:00 PM Boston Time Tuesday, (17:00 UTC),
> when all comments received will be considered and the orientation page
> finalized.
> The Text Subteam uses Zakim channel 2119#; and IRC channel #text. An
> agenda will be published to the Task Force list before this
> teleconference as usual.
> --
> Janina Sajka,   Phone:  +1.443.300.2200
>                         sip:janina@asterisk.rednote.net
>                 Email:  janina@rednote.net
> The Linux Foundation
> Chair, Open Accessibility:      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/

with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
HTML5: Techniques for providing useful text alternatives -
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Sunday, 16 September 2012 09:32:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:30 UTC