Re: ISSUE-122 shalott-example: Call for revisions

Hi Paul, Maciej, Sam and everyone,

> Maciej has said that my proposal for HTML-ISSUE-122 [1] is larger in
> scope than that of the 122 issue.
>
> So instead, I have requested that the HTML Chairs apply my issue 122
> proposal to the third question of alt HTML-ISSUE-31, as it would
> be a better fit; is an applicable and relevant solution; and is based
> on the third draft deliverable [3] of HTML-Action-54 [4] which is
> bound to alt HTML-ISSUE-31.
>
> Maciej said that the Chairs will discuss it [5]. (For details please
> refer to the previous messages in this thread).

Could the HTML Chairs please let me know your decision on whether my
proposal [1] for ISSUE 122 will be applied to ISSUE 31 question number
3 [2] before the February 14 deadline that you gave me to revise my
proposal? If the answer is no I will take Maciej advice and  narrow
the scope for ISSUE 122 to thematic and presentational images and
raise a new bug that covers everything.

It would however be more efficient for everyone involved, if ISSUE 31
question number 3 could be decided before ISSUE 122. If it is decided
that Proposal 9 solves ISSUE 31 question number 3, then ISSUE 122
becomes moot.

Sam, Paul and Maciej, can ISSUE 31 question number 3 please be decided
before ISSUE 122? Can we solving the "Where" question before all off
the "What" questions?

If we are going to piecemeal ISSUE 31, I will need to write change
proposals regarding ISSUE 122  as well as write change proposals for
CAPTCHA and Webcam  as  both Steve's document and Ian's document set
opposing normative guidance. I have filed bugs for both CAPTCHA and
Webcam and had them under the ISSUE 31 umbrella.

CAPTCHA
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9216
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9169

Webcam
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9215
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9174

The HTML Working Group should not be setting normative advice for alt
values. That is WCAG's domain, especially when that advise is in
opposition to WCAG's advice. Providing the mechanism(s) for a text
alternative is an inalienable HTML WG concern. Whereas providing
guidance on values for alternative text is an inalienable WAI concern.

Best Regards,
Laura

[1] http://www.w3.org/html/wg/wiki/ChangeProposals/TextAlternativesIssue122
[2] That question is:  "Where/who will define requirements on the
possible values of text alternative examples?".
http://www.w3.org/html/wg/wiki/ChangeProposals/ImgElementSurveyConformaceChoices#3._Text_Alternative_Examples_Question:_.22Where.2Fwho_will_define_requirements_on_the_possible_values_of_text_alternatives_examples.3F.22

-- 
Laura L. Carlson

Received on Friday, 11 February 2011 13:23:38 UTC