- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Sun, 25 Apr 2010 05:07:21 -0500
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone, Since last week's report we have had six VERIFIED NOREPLY Bugs, one NEW bug, and one FIXED bug. It is anticipated that the survey for the CAPTCHA bug will happen soon, as a draft was presented to Mike Smith a month ago. We still need to agree on criteria for applying the "a11yTF" keyword. I strongly recommend that this be completed soon, as it is a blocker for task force pursuit of work items key to our mission (text-alternatives, ARIA, canvas). The details are as follows. 1. VERIFIED NOREPLY BUGS: As a small part of a HTML working group mass bug move, Maciej [1] [2] set the following six A11y bugs to NOREPLY. NoReply puts a bug in a terminal state. [3] 1.1 Bug 5807: "User Agent display of title attribute content not defined." Reported by Steve Faulkner. Status: VERIFIED NEEDSINFO Keywords: a11y, NoReply http://www.w3.org/Bugs/Public/show_bug.cgi?id=5807 1.2 Bug 5823: "Scope allowable on a td." Reported by Gez Lemon. Status: VERIFIED DUPLICATE of bug 5822 Keywords: a11y, a11y_table_headers, NoReply http://www.w3.org/Bugs/Public/show_bug.cgi?id=5823 1.3 Bug 6181: "Process table feedback (including headers='" issue)" Reported by Ian 'Hixie' Hickson. Status: VERIFIED FIXED Keywords: a11y, a11y_table_headers, NoReply http://www.w3.org/Bugs/Public/show_bug.cgi?id= 6181 1.4 Bug 7144: "I am not sure if we are ditching ALT in favour of legend. You don't make this clear here. Some of your alt examples here resemble longdesc, which I am in favour of ditching completely. I'd be interested to see your answer on whatwg list about this." Reported by contributor@whatwg.org. Status: VERIFIED FIXED Keywords: a11y, a11y_text-alt, NoReply http://www.w3.org/Bugs/Public/show_bug.cgi?id=7144 1.5 Bug 7404: "But only if the element is being rendered" needs to take into account <canvas> descendants if we're making them focusable." Reported by contributor@whatwg.org. Status: VERIFIED FIXED Keywords: a11y, a11ytf, a11y_canvas, NoReply http://www.w3.org/Bugs/Public/show_bug.cgi?id=7144 1.6 Bug 7740: "Authoring advice for canvas is bad for accessibility." Reported by Steve Faulkner. Status: VERIFIED DUPLICATE of bug 7011 Keywords: a11y, a11y_canvas, NE, NoReply http://www.w3.org/Bugs/Public/show_bug.cgi?id=7740 2. FIXED BUG: 2.1 Bug 9174: "Consider adding a Webcam example" reported by Laura Carlson on Steve's Document "Techniques for providing useful text alternatives". Reported by Laura Carlson. Status: Accepted Change Description: have added a webcam images technique and examples: http://dev.w3.org/html5/alt-techniques/#webcam Steve's Rationale: "It is useful to include advice on this particular type of image." My View: The fix looks like it is in accordance with WCAG2 to me. If anyone doesn't agree please speak up. http://www.w3.org/Bugs/Public/show_bug.cgi?id=9174 3. NEW BUG: 3.1 Bug 9589: "HTML5 should give examples for how to present @title when the user can't use a pointing device" Reported by Maciej Stachowiak. http://www.w3.org/Bugs/Public/show_bug.cgi?id=9589 My View: I recommend that we expedite defining "a11ytf" keyword criteria and accept this bug as official task force work. It is key to Issue 31 and 80 and their change proposals. 4. CAPTCHA BUG: Hopefully the survey for the CAPTCHA bug will happen soon. A draft was delivered to Mike a month ago on March 21. The target time frame to go live was over three weeks ago. http://www.w3.org/WAI/PF/HTML/wiki/CAPTCHA_Survey http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0437.html Mike, do you need any more help with this? Is there anything else I can do to help move this forward? 5. ESTABLISHING "A11yTF" KEYWORD CRITERIA: We still need to agree on criteria for applying the "a11yTF" keyword. It would be good to settle this soon as this is a blocker for the task force pursuit of items key to our mission (i.e. Text Alternatives, ARIA). The March 18, 2010 teleconference minutes indicated 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. A Wiki page brainstorms ideas begun in the email "Criteria for 'a11yTF' keyword application". 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 twenty-seven 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_Decision We currently have four 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_Decision We currently have seven bugs that I am aware of that have the keyword "a11ytf" applied with no approval 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=9437 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9452 http://www.w3.org/Bugs/Public/show_bug.cgi?id=9471 The initial set of "A11y" bugs which were determined to have the "A11yTF" keyword applied to them in January 2009 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 2009 are at: http://www.w3.org/WAI/PF/HTML/wiki/Bugs/rejected 6. REFERENCES: [1] http://lists.w3.org/Archives/Public/public-html/2010Mar/0344.html [2] http://lists.w3.org/Archives/Public/public-html/2010Apr/1040.html [3] http://lists.w3.org/Archives/Public/public-html/2010Mar/0193.html 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 Issues in the HTML5 Tracker: http://www.w3.org/WAI/PF/HTML/wiki/Issues 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 Sunday, 25 April 2010 10:07:55 UTC