- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Sat, 23 Oct 2010 05:57:40 -0500
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone, Since the last we have had: 5 bugs escalated. Details are in section 1. 2 bugs reopened. Details are in section 2. 1 bug assigned. Details are in section 3. 2 bugs verified. Details are in section 4. No bugs were marked fixed, won't fix, needs info, remind, later, invalid, or closed. No new a11y bugs were reported. 10 total new a11y bugs existed on October 23, 2010. An October 23 bug snapshot is at: http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot_20101023 A backlog of 91 a11y bugs on the HTML5 Spec await task force decision of whether to apply the a11ytf keyword or not. Details are in section 5. Details are as follows. 1. ESCALATED BUGS: 1.1 Bug 10853: "HTML5 lacks a verbose description mechanism" reported by Gregory J. Rosmaita. Sam Ruby had removed the TrackerRequest keyword on October 12. Martin added TrackerIssue keyword on October 19 saying: "Bug triage sub-team adding TrackerIssue keyword since this is related to ISSUE-30. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10853#c5 Shelley Powers commented on October 20: "It's inappropriate to remove TrackerRequest because this bug is only incidentally related to the Issue 30 decision...I agree on this being a TrackerIssue. I do not agree that this should be associated with a previously decided issue, because this bug is not asking that longdesc be returned, but that something be created to provide the functionality that longdesc provided. The original bug provided very clear and very concise requirements for this replacement." http://www.w3.org/Bugs/Public/show_bug.cgi?id=10853#c6 Note: Bug 10853 depends on bug 10455: http://www.w3.org/Bugs/Public/show_bug.cgi?id=10455 Question to the task force Chairs and members: What is the Accessibility Task Force position on Bug 10853 and 10455? In addition please note that longdesc research continues for John Foliot's Formal Objection: * Examples In the Wild (approaching 100 sites using longdesc) http://www.d.umn.edu/~lcarlson/research/ld.html#wild * Guidelines, Laws, Policy, and Standards http://www.d.umn.edu/~lcarlson/research/ld.html#glps * Tools (browsers, assistive technology, authoring tools) http://www.d.umn.edu/~lcarlson/research/ld.html#tools * Online Tutorials and Documentation http://www.d.umn.edu/~lcarlson/research/ld.html#tutorials * HTML5 ISSUE 30 Info: http://www.d.umn.edu/~lcarlson/research/ld.html#issue * Notice of Impending Formal Objection to HTML5 Issue 30 Decision (@longdesc) - John Foliot http://lists.w3.org/Archives/Public/public-html-a11y/2010Aug/0027.html Question to the task force Chairs and members: Will the Accessibility Task Force be formally supporting John's longdesc Formal Objection? Is this something that this group will help John pursue? 1.2 Bug 10921: "Put back direct link to the W3C version of the canvas 2d context spec"" reported by Steve Faulkner. Sam Ruby raised Issue HTML ISSUE 135 on Steve's behalf. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10921#c3 http://www.w3.org/html/wg/tracker/issues/135 1.3 Bug 10831: "Provide tablist and tab states for menu and command elements respectively" reported by Everett Zufelt. Sam Ruby raised Issue HTML ISSUE 134 on Everett's behalf. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10831#c5 http://www.w3.org/html/wg/tracker/issues/134 1.4 Bug 10645: "Add a modal attribute to html5 to indicate a modal segment of the DOM" reported by Everett Zufelt. Sam Ruby raised Issue HTML ISSUE 133 on Everett's behalf. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10645#c12 http://www.w3.org/html/wg/tracker/issues/133 1.5 Bug 9077: "Lady of Shalott example doesn't really 'enhance the themes or subject matter of the page content'" reported by Ian 'Hixie' Hickson. Ian had asked that Bug 9077 be deescalated. http://www.w3.org/Bugs/Public/show_bug.cgi?id=9077#c8 Sam Ruby's response: "Call for proposals went out on 15 September: http://lists.w3.org/Archives/Public/public-html/2010Sep/0182.html We received a proposal on 13 October: http://lists.w3.org/Archives/Public/public-html/2010Oct/0182.html http://www.w3.org/html/wg/wiki/ChangeProposals/thematicimages The chairs have agreed that withdrawing the issue after a change proposal has been received is not appropriate. Ian: do you have a realistic deadline in mind? Barring an acceptable suggestion, the plan is to issue a call for consensus on the change proposals that we have got on Wednesday morning." http://www.w3.org/Bugs/Public/show_bug.cgi?id=9077#c9 Close ISSUE-122 (shalott-example) by Amicable Consensus Sam: If there are no objections, we will close ISSUE-122 on October 28th. http://lists.w3.org/Archives/Public/public-html/2010Oct/0323.html 2. REOPENED BUGS: 2.1 Bug 10873: "Provide a method of explicitly setting a tooltip for an element" reported by Everett Zufelt. Martin reopened saying: "HTML a11y TF bug triage sub-team adding a11yTF keyword and assigning the bug to the editor because his response to the REOPEN state change is needed next." http://www.w3.org/Bugs/Public/show_bug.cgi?id=10873#c12 2.1 Bug 10419: "<video> should allow muted as a content attribute" " reported by Adrian Bateman. Simon Pieters reopened saying: "I'd like the editor to consider the comments here http://html5doctor.com/html5-simplequiz-3-how-to-mute-a-video/#comments There are many different opinions, and one could draw different conclusions... I'll refrain from doing further analysis of the comments myself at this time." http://www.w3.org/Bugs/Public/show_bug.cgi?id=10419#c17 3. ASSIGNED BUGS: 3.1 Bug 10988: "add slider element" reported by Jim Michaels. Jim Michaels assigned this bug to himself. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10988 4. VERIFIED BUGS. The following bugs were marked "VERIFIED" by Ms2ger. Marking a bug VERIFIED starts a TWO WEEK clock to take action. If no action is taken, the bug is marked NoReply. A NoReply puts a bug in a terminal state. See the HTMLWG Decision Policy for details: http://dev.w3.org/html5/decision-policy/decision-policy.html#states-and-keywords 4.1. Bug 10465: "provide correct aria mapping and role info for the table element" reported by Steve Faulkner. VERIFIED DUPLICATE by Ms2ger aka Maciej. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10465 4.2. Bug 10783: "change summary from an attribute to an element" reported by Gregory J. Rosmaita. VERIFIED DUPLICATE by Ms2ger aka Maciej. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10783 5. "A11yTF" KEYWORD BACKLOG: We currently have ninety-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 One bug on document "HTML5: Techniques for providing useful text alternatives Bugs" awaits task force decision. Michael(tm) Smith is editor of that document. http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#HTML:_The_Markup_Language_Reference_Bugs_Awaiting_Decision One bug on document "HTML Working Group Decision Policy" awaits task force decision. Maciej Stachowiak, Paul Cotton, Sam Ruby are the editors of that document. http://www.w3.org/WAI/PF/HTML/wiki/Bugs/http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Bugs_Awaiting_A11yTF_Keyword_Decision#HTML_Working_Group_Decision_Policy_Bugs_Awaiting_Decision No bugs on document on the document "HTML5: Techniques for providing useful text alternatives Bugs" await 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 6. RELATED REFERENCES: Weekly Resolved and Rejected Bugs Reports Archive http://www.w3.org/WAI/PF/HTML/wiki/Bugs/Weekly_Resolved_and_Rejected_Bugs_Reports A11y Resolved Bug Comparisons: http://www.d.umn.edu/~lcarlson/html5bugchart/ New Bug Snapshots http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot 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, 23 October 2010 10:58:18 UTC