- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Sat, 10 Jul 2010 03:06:39 -0500
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone, Since last week's report we have had one new a11y bug reported. Details are in section one. A draft survey for the CAPTCHA bug was presented to Mike Smith sixteen weeks ago. A status update would be useful. Details are in section two. We currently have an "A11yTF" keyword backlog of thirty seven bugs. Details are in section three. Complete details are as follows. 1. NEW BUG: 1.1 Bug 10077: "The <embed> should support an alt attribute. While the embedded content should provide for accessibility of the embedded object, the developer doesn't always have control over those content, some embeddable formats are inherently less accessible, and the developer should have a means to provide added context (title can help, but different purpose) to help the user determine whether the embedded content is worth navigating into." reported by contributor@whatwg.org. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10077 Recommendation: Apply the "A11yTF" keyword, a task force member volunteers and agrees to actively work on and see this bug through to closure. This bug seems to meet draft a11ytf bug criteria. http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria 2. 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 thirteen 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. "A11yTF" KEYWORD BACKLOG: We currently have thirty seven HTML5 Spec bugs awaiting task force decision of whether to apply the a11ytf keyword or not. http://www.w3.org/WAI/PF/HTML/wiki/Bugs/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/Bugs_Awaiting_A11yTF_Keyword_Decision#Text_Alternatives_Techniques_Bugs_Awaiting_Decision The initial sets 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 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, 10 July 2010 08:07:08 UTC