- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Tue, 23 Mar 2010 18:33:25 -0500
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone, Since last week's report we have had two WONTFIX bug resolutions and one DUPLICATE bug resolution. Two bugs were REOPENED. One NEW bug was reported. A survey has been drafted for the CAPTCHA bug. Eleven bugs were downgraded from Priority 2 to Priority 3. Two bugs were upgraded from Priority 2 to Priority 1. Four bugs with the keyword "TrackerIssue" were mislabeled FIXED. No bugs were actually FIXED this week. The task force began discussion on criteria for applying the "a11yTF" keyword. A brainstorming Wiki page was created in this effort. The details follow. 1. WONTFIX BUGS: Bug 9212: "Change the Generator Mechanism for img from Document Level to Element Level". Editor's WONTFIX Rationale: "Quite contrary to the assertion above, I think making it possible for individual images to be tagged as 'don't validate me' makes it far easier for authors to neglect their responsibility than using meta generator..." LC: I can add the "TrackerIssue" keyword to this bug now since the editor won't fix the problem. And I can adjust the change proposal accordingly and remove the generator as option. The WAI CG text alternative document said that they wouldn't oppose a generated *attribute* but a document level generated mechanism that allows a full page of images to not have text alternatives is not allowed. I could file a new bug to eliminate the generator mechanism completely but I don't know if that would be productive, as I suspect it too would be marked WONTFIX. Task force advice would be appreciated. http://www.w3.org/Bugs/Public/show_bug.cgi?id=9212 Bug 9216: "Provide a CAPTCHA example that is in accord with WCAG 2 or Defer to HTML5: Techniques for providing useful text alternatives" Editor's WONTFIX Rationale: "WCAG2's suggestion on the matter is a workaround for a limitation of HTML4. We should be careful when applying WCAG2 suggestions to HTML5 to not automatically assume the advice in WCAG2 is the best possible solution, as it is constrained by what HTML4 allowed. HTML5's solution avoids conflating alternatives and purpose descriptions, and as such is an improvement over what could be done in HTML4." LC Suggestion: The task force should be having a survey on this fairly soon. Proceed after we have the outcomes. 2. DUPLICATE BUG: Bug 9218: "Enable Automatic Validators to Programmatically Determine the Presence or Absence of a Set of Text Alternatives. I marked this bug as a duplicate of 8716 as 8716 is the main bug for associated text alternative change proposal. http://www.w3.org/Bugs/Public/show_bug.cgi?id=9218 3. REOPENED BUGS: Bug 8171: "Implement the text alternatives proposal from WAI" reported by Michael Cooper. 8171 had been marked "NEEDSINFO". I reopened it as the bugs in the dependency tree provide further information for the editor. http://www.w3.org/Bugs/Public/showdependencytree.cgi?id=8171 Bug 7721: "Drag and Drop is not keyboard accessible" reported by Rich Schwerdtfeger was reopened by Mike Smith per discussion on 2010-03-18 a11y TF telcon. Maciej's comment: "Since this was originally resolved as NEEDSINFO, is anyone going to provide the requested info?" http://www.w3.org/Bugs/Public/show_bug.cgi?id=7721#c15 LC suggestion: Try to provide Ian the information that he needs. Rich Schwerdtfeger had previously volunteered to submit a change proposal. http://www.w3.org/Bugs/Public/show_bug.cgi?id=7721#c9 4. NEW BUGS: Bug 9280: "Add default button option/attribute for forms" reported by Jonathan Avila. LC Suggestion: It is currently unclear what is being proposed in this bug. Postpone applying the a11ytf keyword, until the bug description is clarified and "a11ytf" keyword criteria established. http://www.w3.org/Bugs/Public/show_bug.cgi?id=9280 5. CAPTCHA bug: A survey has been drafted for the CAPTCHA bug. http://www.w3.org/WAI/PF/HTML/wiki/CAPTCHA_Survey Ideas for improvement are most welcome. 6. PRIORITY CHANGES: Bugs Upgraded From Priority 2 to Priority 1 are 9215: "Provide a Webcam example that is in accord with WCAG 2 or Defer to "HTML5: Techniques for providing useful text alternatives". http://www.w3.org/Bugs/Public/show_bug.cgi?id=9215 9217: "Remove the Paragraph-Section-Heading loophole for not providing a text alternative. http://www.w3.org/Bugs/Public/show_bug.cgi?id=9217 Comments on the Webcam and Paragraph-Section-Heading loophole bugs from task force members would be appreciated. Steve and Maciej have already done so. Thank you both. Bugs Downgraded From Priority 2 to Priority 3 are 6496: "Allow <img aria-labelledby> to act as a text alternative". http://www.w3.org/Bugs/Public/show_bug.cgi?id=6496 7056: "<caption> and <figure><legend> elements should allow flow content children". http://www.w3.org/Bugs/Public/show_bug.cgi?id=7056 7076: "Client-side image maps attributes missing on the a element". http://www.w3.org/Bugs/Public/show_bug.cgi?id=7076 8646: "Private communication exception" (No text alternative allowed in email). http://www.w3.org/Bugs/Public/show_bug.cgi?id=8646 8716: "Replace img Guidance for Conformance Checkers with Suggested Text". http://www.w3.org/Bugs/Public/show_bug.cgi?id=8716 9061: "For Short Text Alternatives allow image maps on the canvas" element". http://www.w3.org/Bugs/Public/show_bug.cgi?id=9061 9098: "Correct the img element definition. Replace with suggested text". http://www.w3.org/Bugs/Public/show_bug.cgi?id=9098 9135: "Provide an inline link in the canvas section to the 2d context spec". http://www.w3.org/Bugs/Public/show_bug.cgi?id=9135 9213: "HTML5 Lacks a Way to Programmatically-Determine Missing Text Alternatives". http://www.w3.org/Bugs/Public/show_bug.cgi?id=9213 9214: "Allow role="presentation" on img". http://www.w3.org/Bugs/Public/show_bug.cgi?id=9214 9241: "Explicitly state, 'For guidance on accessibility requirements for text alternatives authors should consult WCAG 2.0" and link to WCAG 2.0'." http://www.w3.org/Bugs/Public/show_bug.cgi?id=9241 7. MISLABELED TRACKERISSUE BUGS: Maciej set the status on the following bugs to FIXED after they were reopened through a misunderstanding of the decision process at last week's accessibility task force teleconference. Maciej's rationale is that these bugs were already escalated to a tracker issues. VERIFIED with a TrackerIssue keyword is indeed the correct state for a bug that has been "resolved" by the editor but has not yet in fact been decided by the working group via the escalation process. Maciej was correct to move the following bugs back to VERIFIED. They shouldn't have been reopened per HTML working group process. However, they should have been left in the state that the editor had set them to last. Ian did not FIX them. The following bugs were not FIXED. I adjusted them accordingly. Bug 7362: "inclusion of the title as a case where the alt may be omitted is problematic" http://www.w3.org/Bugs/Public/show_bug.cgi?id=7362#c18 Bug 7633: The use of @summary should be encouraged when circumstances warrant". http://www.w3.org/Bugs/Public/show_bug.cgi?id=7633#c21 Bug 5758: "<audio> and <video> do not have sufficient support for synchronized accessibility content" http://www.w3.org/Bugs/Public/show_bug.cgi?id=5758#c22 8. ESTABLISHING "A11yTF" KEYWORD CRITERIA: Last week's 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. The following Wiki page is a starting draft of 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 9. RELATED REFERENCES: 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 Tuesday, 23 March 2010 23:33:54 UTC