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

Weekly Resolved & Rejected Bugs Report

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sun, 11 Apr 2010 04:42:31 -0500
Message-ID: <q2w1c8dbcaa1004110242y47a684b9g79a2bde42f8cf393@mail.gmail.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone,

Since last week's report we have had three NEW a11y bugs reported. No
bugs were fixed or rejected.

It is anticipated that the survey for the CAPTCHA bug will happen
soon, as a draft was presented to Mike Smith three weeks ago.

We still need to agree on criteria for applying the "a11yTF" keyword.
I strongly recommend that this is be completed soon, as it is a
blocker for task force pursuit of work items key to our mission
(text-alternatives, ARIA, canvas).


1. NEW BUGS:

Bug 9437: "Change ARIA section title and add extra text about use of
ARIA" reported by Steve Faulkner.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9437
My View: I recommend that we expedite defining "a11ytf" keyword
criteria so Steve knows if the task force can officially work on this
item or if he has to go it alone. Currently not having the "a11ytf"
keyword designation blocks the task force from officially working on
bugs key to the task force mission.

Bug 9452: "Handling of additional tracks of a multitrack audio/video
resource" reported by Silvia Pfeiffer.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9452
My View: I recommend that we expedite defining "a11ytf" keyword
criteria so Silvia knows if the task force can officially work on this
item or if she has to go it alone. Currently not having the "a11ytf"
keyword designation blocks the task force from officially working on
bugs key to the task force mission.

Bug 9452: "Mandate in HTML5 that all conformance checkers and
validators must refer to the appropriate WCAG document and section
that provides remedial guidance to authors whenever text alternatives
are unknown or missing." reported by Laura Carlson.
My View: I recommend that we expedite defining "a11ytf" keyword
criteria so I knows if the task force can officially work on this item
or if I has to go it alone. Currently not having the "a11ytf" keyword
designation blocks the task force from officially working on bugs key
to the task force mission.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9485


2. CAPTCHA BUG:

Hopefully the survey for the CAPTCHA bug will happen soon. A draft was
delivered to Mike on March 21. The target time frame to go live was
over a two weeks ago.
http://www.w3.org/WAI/PF/HTML/wiki/CAPTCHA_Survey
http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0437.html

Mike, do you need any more help with this? Is there anything else I
can do to help move this forward?


3. ESTABLISHING "A11yTF" KEYWORD CRITERIA:

We still need to agree on criteria for applying the "a11yTF" keyword.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria
It would be good to settle this soon as this is a blocker for the task
force pursuit of items key to our mission (i.e. Text Alternatives,
ARIA).

The March 18, 2010 teleconference minutes indicated 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. A Wiki page
brainstorms ideas begun in the email "Criteria for 'a11yTF' keyword
application".
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 twenty-six HTML5 Spec (Ian Hickson Editor) bugs
awaiting task force decision
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#HTML5_Spec_Bugs_Awaiting_A11yTF_Keyword_Decision

We currently have four Bugs on the document "HTML5: Techniques for
providing useful text alternatives" (Steve Faulkner editor) which are
awaiting task force decision.
http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Text_Alternatives_Techniques_Bugs_Awaiting_A11yTF_Decision

We currently have five bugs that I am aware of that have had the
Keyword "a11ytf" applied with no approval from the task force:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7056
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8674
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8715
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8827
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9452

The initial set of "A11y" bugs which were determined to have the
"A11yTF" keyword applied to them in January 2009 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 2009 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

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 Issues in the HTML5 Tracker:
http://www.w3.org/WAI/PF/HTML/wiki/Issues

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, 11 April 2010 09:43:04 GMT

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