- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Sat, 26 Jun 2010 05:14:16 -0500
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone, Since last week's report we have had one bug marked invalid. Details are in section one below. We have had four new a11y bug reported. Details are in section two. A draft survey for the CAPTCHA bug was presented to Mike Smith fourteen weeks ago. A status update would be useful. Details are in section three. We currently have an "A11yTF" keyword backlog of thirty-three bugs. Details are in section four. Complete details are as follows. 1. REOPENED BUGS: Bug 9241: "Explicitly state, 'For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0' and link to WCAG 2.0" reported by Laura Carlson. I reopened this bug after Ian reverted the change that he had previously instituted. http://www.w3.org/Bugs/Public/show_bug.cgi?id=92411#c3 After he marks the bug is marked WONTFIX, I will be able to raise it as a tracker issue. I have begun writing a Change Proposal. Steve has expressed interest in collaborating on it. Task Force support would be appreciated and all help is welcome. 2. NEW BUGS: 2.1 Bug 10015: "longdesc URL checking" reported by Leif Halvard Silli. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10015 Recommendation: Apply the "A11yTF" keyword, if Leif 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.2 Bug 10016: "longdesc and @role (ARIA)" reported by Leif Halvard Silli. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10016 Recommendation: Apply the "A11yTF" keyword, if Leif 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. 2.3 Bug 10017: "longdesc and @aria-describedby (ARIA) How does longdesc and @aria-describedby work together?" reported by Leif Halvard Silli. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10017 Recommendation: Apply the "A11yTF" keyword, if Leif 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. 2.4 Bug 10019: "Native user agent support for exposing longdesc to all users" reported by Laura Carlson. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10019 Recommendation: Apply the "A11yTF" keyword, I volunteer to actively work on and see this bug through to closure. This bug meets draft a11ytf bug criteria. Reminder: HTML ISSUE-30: include a longdesc attribute for images - Straw Poll for Objections is open until June 30. http://www.w3.org/2002/09/wbs/40318/issue-30-objection-poll/ Results so far: http://www.w3.org/2002/09/wbs/40318/issue-30-objection-poll/results 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 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? 4. "A11yTF" KEYWORD BACKLOG: We currently have thirty-three HTML Spec bugs awaiting task force decision. Ian Hickson is editor of that document. 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#Text_Alternatives_Techniques_Bugs_Awaiting_A11yTF_Keyword_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 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, 26 June 2010 10:14:44 UTC