- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Sat, 15 May 2010 02:55:37 -0500
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone, Since last week's report no bugs have been fixed or resolved. No NEW a11y bugs were reported. A draft survey for the CAPTCHA bug was presented to Mike Smith seven weeks ago. Details are in section section one. Mike, What is the status on this? The Task Force still has not agreed on criteria or procedure for applying the "a11yTF" keyword to new bugs. Details are in section two below. Janina and Mike, should task force members simply use their own judgment and individually tag bugs "a11yTF" as they see fit or will criteria and a procedure be defined? 1. 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 five 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? 2. 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 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 HTML Spec bugs awaiting task force decision. Ian Hickson is editor of that document. http://www.w3.org/WAI/PF/HTML/wiki/Bugs#HTML5_Spec_Bugs_Awaiting_A11yTF_Keyword_Decision 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 We currently have five bugs that I am aware of that have the Keyword "a11ytf" applied with no approval decision 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=9673 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 3. 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 Change Proposal Status Table: http://www.w3.org/WAI/PF/HTML/wiki/Accessibility_Change_Proposal_Status Best Regards, Laura -- Laura L. Carlson
Received on Saturday, 15 May 2010 08:26:22 UTC