- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Sat, 19 Jun 2010 13:16:26 -0500
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone, Since last week's report we have had one new bug. Details are in section one below. We have had one invalid bug resolution. Details are in section two. A draft survey for the CAPTCHA bug was presented to Mike Smith thirteen weeks ago. A status update would be useful. Details are in section three. We currently have an "A11yTF" keyword backlog of thirty-five bugs. Details are in section four. Complete details are as follows. 1. NEW BUG: Bug 9936: "onclick attributes on any element that is not focusable should trigger a conformance error" reported by Steve Faulkner. http://www.w3.org/Bugs/Public/show_bug.cgi?id=9936 Recommendation: Apply the "A11yTF" keyword, if Steve or another task force member volunteers and agrees to actively work on and see this bug through to closure. This bug meets draft a11ytf bug criteria. http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria 2. INVALID BUG: Bug 9804: "the alt attribute must be specified" so are you saying ALT is required?" reported by contributor@whatwg.org. http://www.w3.org/Bugs/Public/show_bug.cgi?id=9804 Maciej marked this bug INVALID. Maciej's Rationale: "That's what it says. INVALID as it is a question, rather than a bug." My View: This bug is indeed phrased as question. But I don't know if I would classify 9804 as INVALID. In comment two, I asked the commenter if any assistance is needed with bug. http://www.w3.org/Bugs/Public/show_bug.cgi?id=9804#c2 In these types of cases where the bug reporter is not a task force member but the bug is accessibility related, the task force should try to help or advise the bug reporter to the best of our ability. 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 twelve 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? 4. "A11yTF" KEYWORD BACKLOG: Mike Smith added "A11yTF" keyword to bugs 9871 and 9872 after last week's teleconference. Thank you, Mike. So, we currently now have a backlog of thirty-five bugs awaiting "A11yTF" keyword decision: http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision Martin made some good suggestions regarding bugs in his June 18 message. Thank you very much Martin. http://lists.w3.org/Archives/Public/public-html-a11y/2010Jun/0173.html In particular he suggested that bugs that have been raised by task force members be tagged "A11yTF". Point two of the draft Keyword Criteria document states that bugs, "Must have a minimum of one task force member volunteering and agreeing to actively work on/see through to closure". http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria So if a task force member intends to follow through and the bug meets the other draft criteria, I agree with Martin to tag them "A11yTF". I also agree with Martin that reporters should set the status to "closed" on bugs where appropriate. Martin asked about the procedure to advance a bug to an issue. That is explained at: http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Escalating_a_Bug_to_an_Issue 5. RELATED REFERENCES: Weekly Resolved and Rejected Bugs Reports Archive http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Weekly_Resolved_and_Rejected_Bugs_Reports Backlog of Bugs Awaiting "A11yTF" Keyword Decision http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision "A11yTF" Keyword Criteria (Draft) http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria 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, 19 June 2010 18:16:57 UTC