Bugfix Re: Call for Consensus (CfC): Transition the Image Description specification to Proposed Recommendation (PR) status

Dear all,

please note that we fixed a bug [1] caused by a typo in the draft specification yesterday.

The specification text used the lower-case "longdesc" for the IDL / DOM attribute, as well as for the HTML attribute. However, for DOM the attribute should be "camel-cased". This was brought to our attention recently by SImon Pieters (Thanks!!!), and we meant to clean it up in producing a PR-draft. Unfortunately, I dropped that ball, but I am grateful to Liam for making the change.

It was already "camelCased" (i.e. 'longDesc') in the HTML spec, in our own test cases, and in implementations we have tested. 

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=26653

chaals

05.09.2014, 04:43, "Janina Sajka" <janina@rednote.net>:
> Colleagues:
>
> This is a Call for Consensus (CfC) to the HTML-A11Y Task Force on three
> specific questions relating to our HTML Image Description Extension
> specification currently in Candidate Recommendation (CR) status:
> http://lists.w3.org/Archives/Public/public-html-a11y/2014Aug/0017.html
>
> Specification Changes to the CR Document
>
> Please note that we have updated our draft Proposed Recommendation (PR)
> specification based on implementer feedback during CR. Specifically, we
> have
>
> 1.) modified the language of the second provision in Sec. š3.0.3 to
> clarify that exposing longdesc to accessibility APIs means different
> things, depending on the accessibility API.
>
> 2.) Added a note in Sec. 3.0.2 to indicate that "there will be cases
> where user agents cannot or do not automatically restrict the
> information presented to the container element."
>
> We regard these as
> editorial clarifications. They better explain what to do, but do not
> invalidate existing implementations.
>
> The Proposed Recommendation (PR) draft is available at:
> http://www.w3.org/2014/09/04-PR-html-longdesc/
>
> Three CfC Questions
>
> Please respond on each of the following three propositions.
>
> PROPOSITION #1: The HTML-A11Y Task Force believes that the archived
> record of deliberation on the topics raised in the Formal Objection
> filed by Apple Computer on this specification is sufficient to support
> progressing it toward Recommendation status. šWe request that W3C
> management move forward toward an expedited resolution of that
> objection. The Formal Objection can be found at:
> http://lists.w3.org/Archives/Public/public-html-admin/2014Aug/0028.html
>
> PROPOSITION #2: The Task Force thanks Igalia for its implementation
> report and its comments on the CR specification and supports the
> disposition of those comments as proposed at:
> http://lists.w3.org/Archives/Public/public-html-a11y/2014Sep/0000.html
> with the additional modification (also accepted by Igalia) at:
> http://lists.w3.org/Archives/Public/public-html-a11y/2014Sep/0011.html.
>
> PROPOSITION 3: The HTML-A11Y Task Force recommends and requests that the
> HTML and PF Working Groups transition the HTML 5 Image Description
> Extension specification to Proposed Recommendation (PR status using the
> draft document at:
> http://www.w3.org/2014/09/04-PR-html-longdesc/
>
> Our Implementation Report for this specification showing that it meets
> W3C recommendation requirements is available at:
> http://w3c.github.io/test-results/html-longdesc/cr-report.html
>
> ACTION TO TAKE
>
> According to agreed Task Force Consensus Procedures, this CfC is now
> open for objection, comment, as well as statements of support via email
> on each of the above three propositions. Silence will be interpreted as
> support, though messages of support are certainly welcome.
>
> Please direct all responses by replying on list to this message no later
> than 23:59 (Midnight) Boston Time on Wednesday 10 September.
>
> Janina Sajka, For the HTML-A11Y Task Force Co-Facilitators
>
> --
>
> 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/

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com

Received on Tuesday, 9 September 2014 09:24:40 UTC