- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Sat, 31 Jul 2010 03:42:37 -0500
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone, Since last week's report no bugs have been resolved. Four new bugs were reported. Details are in section one. We currently have an "A11yTF" keyword backlog of forty-one HTML5 Spec bugs. Details are in section two. Complete details are as follows. 1. NEW BUGS: 1.1 Bug 10248: "Canvas requires a Caret Drawing call method" reported by Rich Schwerdtfeger. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10248 Recommendation: Apply the "A11yTF" keyword, if Rich 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 1.2 Bug 10249: "Canvas requires a content selection method" reported by Rich Schwerdtfeger. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10249 Recommendation: Apply the "A11yTF" keyword, if Rich 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. 1.3 Bug 10251: "Psuedo-Cascade of Multiple Accesskeys Definable for an Individual Element" reported by Gregory J. Rosmaita. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10251 Recommendation: Apply the "A11yTF" keyword, if Gregory 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. 1.4 Bug 10252: " HTML5 hard-binds "Action" to accesskey key-press " reported by Gregory J. Rosmaita. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10252 Recommendation: Apply the "A11yTF" keyword, if Gregory 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/Bugs/Public/show_bug.cgi?id=10251 2. "A11yTF" KEYWORD BACKLOG: We currently have forty-one 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 seven 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 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 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, 31 July 2010 08:43:11 UTC