W3C home > Mailing lists > Public > public-html-a11y@w3.org > June 2010

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sun, 6 Jun 2010 05:01:49 -0500
Message-ID: <AANLkTinBzPeXtzN2uUuStlwTTuIS0d12GrYiL7TnNdQc@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since last week's report one bug has been fixed. Details are in
section one below.

One new a11y bug was reported. Details are in section two below.

A draft survey for the CAPTCHA bug was presented to Mike Smith eleven
weeks ago. Details are in section three below.

The Task Force still has not agreed on criteria or procedure for
applying the "a11yTF" keyword to a11y bugs. Details are in section
four below.

1. FIXED BUG:

Bug 9835: "Remove image analysis" reported by Sam Ruby.
Sam filed this bug as a directive to the editor to settle Issue 66.
Ian removed the sentence from the W3C version of HTML5. Thank you.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9835

Ian's Check-in comment: "Checked in as WHATWG revision r5101. Remove a
paragraph from the W3C version by request of the chairs. Add a list of
differences between the versions of the spec to the WHATWG version now
that there's more than a few. Add a paragraph to the W3C version
mentioning this. Make it easier to keep track of what is in what
version of the spec when editing."

The WHATWG version reads:
<!--END w3c-html--><!--POLITICS-->
User agents may also apply heuristics to help the user make use of the
image when the user is unable to see it, e.g. due to a visual
disability or because they are using a text terminal with no graphics
capabilities. Such heuristics could include, for instance, optical
character recognition (OCR) of text found within the image.
<!--START w3c-html--><!--POLITICS-->

The relevant list item in the WHATWG Version is:
<li>The W3C version omits a paragraph of implementation advice for
political reasons.</li>

Full differences are at:
http://html5.org/tools/web-apps-tracker?from=5100&to=5101


2. NEW BUG:

Bug 9845: "Provide reference and info about HTML5: Techniques for
providing useful text alternatives in html5 spec." reported by Steve
Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9845


3. CAPTCHA BUG:

A draft survey for the CAPTCHA bug was delivered to Mike Smith on March 21.
http://www.w3.org/WAI/PF/HTML/wiki/CAPTCHA_Survey
http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0437.html
http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0402.html

As discussed at the March 18 teleconference, the target time frame to
go live was over ten weeks ago.
http://www.w3.org/2010/03/18-html-a11y-minutes.html#item02

Mike, what's up with this? Has it been decided to not hold a survey or
postpone a survey or cancel a survey? Is this bug now considered
superseded by the alt Change Proposals? Should I drop this item from
this weekly report?


3. ESTABLISHING "A11yTF" KEYWORD CRITERIA:

The Task Force still has not agreed on criteria for applying the
"a11yTF" keyword to NEW bugs. I have previously recommended that we
develop criteria, because on March 18, Mike Smith said that a non
trivial cost exists to tagging bugs "a11ytf" and that the task force
needs to agree on criteria for our decisions to take on bugs.
http://www.w3.org/2010/03/18-html-a11y-minutes.html#item02

Mike, what is the status with this? Has it been decided not to have
the group document and to agree a set of criteria in advance of
tagging bugs "a11yTF"?

Should task force members use their own judgment and tag bugs "a11yTF"
as they see fit? That would seem to be a simpler procedure.

I had started a Wiki page to brainstorm ideas for criteria but maybe
that is irrelevant now?
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria
http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0438.html

We currently have thirty two HTML Spec bugs awaiting task force
decision. Ian Hickson is editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Bugs_Awaiting_A11yTF_Keyword_Decision

At last week's teleconference it was decided that Bugs 9817, 9773,
9774, 9775 have the a11ytf keyword applied. Michael Cooper has done
that. Thank you, Michael.
http://www.w3.org/Bugs/Public/show_activity.cgi?id=9817
http://www.w3.org/Bugs/Public/show_activity.cgi?id=9773
http://www.w3.org/Bugs/Public/show_activity.cgi?id=9774
http://www.w3.org/Bugs/Public/show_activity.cgi?id=9775

We currently have five Bugs on Document "HTML5: Techniques for
providing useful text alternatives Bugs" awaiting task force decision.
Steve Faulkner is editor of that document.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Text_Alternatives_Techniques_Bugs_Awaiting_A11yTF_Keyword_Decision

The initial set of "A11y" bugs which were determined to have the
"A11yTF" keyword applied to them in January 2010 are at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/accepted

The initial set of "A11y" bugs which were determined not to have the
"A11yTF" keyword applied to them in January 2010 are at:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/rejected


4. RELATED REFERENCES:

Weekly Resolved and Rejected Bugs Reports Archive
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Weekly_Resolved_and_Rejected_Bugs_Reports

Bugs Awaiting A11yTF Keyword Decision
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision

Bug Status Table:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Bug_Status_Table

Escalating a Bug to an Issue:
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Escalating_a_Bug_to_an_Issue

Accessibility Change Proposal Status Table:
http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposal_Status

Best Regards,
Laura

--
Laura L. Carlson
Received on Sunday, 6 June 2010 10:02:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:12 GMT