- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Sat, 18 Dec 2010 12:15:59 -0600
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hello Everyone, Since the last report we have had: 3 WONTFIX bug resolutions. Details are in section 1. 1 NEEDSINFO bug resolution. Details are in section 2. 1 REOPENED bug. Details are in section 3. 2 NEW a11y bugs reported. Details are in section 4. 1 CLOSED bug. Details are in section 5. A backlog of 29 a11y bugs on the HTML5 Spec await task force decision of whether to apply the a11ytf keyword or not. Details are in section 6. 16 total NEW a11y bugs existed on December 18, 2010. A December 18 snapshot is at: http://www.w3.org/WAI/PF/HTML/wiki/Bugs/New_A11Y_Bug_Snapshot_20101218 Pre and post last call bugs are identified in each item. According to the HTML Chairs' message regarding deadlines, January 22 is the cutoff for escalating bugs for pre-LC consideration. All issues need to be in the HTML working group tracker by that date. The consequence of missing the January 22 deadline is that any further escalations will be treated as a Last Call comments. http://lists.w3.org/Archives/Public/public-html/2010Sep/0074.html The HTML5 Accessibility Bug Status is at: http://www.w3.org/WAI/PF/HTML/wiki/Bugs#Bug_Status_Table Details are as follows. 1. WONTFIX BUGS: 5.1 Bug 10723: "Support for media fragment URIs in relevant HTML5 elements" reported by Silvia Pfeiffer. (Pre Last Call1 Bug) Reopened by Raphael Troncy. Comment: "The Media Fragments WG would like to re-open this bug entry. We further detail below why we think this bug impacts HTML5 and its interaction with the Media Fragments URI specification..." http://www.w3.org/Bugs/Public/show_bug.cgi?id=10723#c5 Change Description: no spec change Ian's Rationale: see above http://www.w3.org/Bugs/Public/show_bug.cgi?id=10723#c11 1.1 Bug 10963: "Table prohibited from being used as a layout aid" reported by Rich Schwerdtfeger. (Pre Last Call1 Bug) On Tuesday Sam Ruby closed this bug and Issue 130 without prejudice as no one had written a Change Proposal by the deadline. He added the "WGDecision" keyword. On Wednesday Rich wrote a Change Proposal and requested Issue 130 be reopened. http://lists.w3.org/Archives/Public/public-html/2010Dec/0132.html Sam reopened Issue 130 and reset this bug to RESOLVED WONTFIX. http://lists.w3.org/Archives/Public/public-html/2010Dec/0133.html http://www.w3.org/html/wg/tracker/issues/130 http://www.w3.org/Bugs/Public/show_bug.cgi?id=10963 1.1 Bug 11395: "Use media queries to select appropriate <track> elements" reported by Frank Olivier. (Post Last Call1 Bug) Ian's Rationale: "Before we apply this to <track>, I think we should wait to have proven that it works with <source>. We can always add it to <track> later if it turns out that this works well." http://www.w3.org/Bugs/Public/show_bug.cgi?id=11395 2. NEEDSINFO BUGS: 2.1 Bug 11152: "Polyglot spec should mention accessibility" reported by Tony Ross on the "HTML/XHTML Compatibility Authoring Guide" doc. Eliot's comment: "I'm still looking into whether there are any issues in accessibility that are specific to polyglot markup and are not duplicates of HTML issues in general. If any arise, I will reopen this bug. Feel free to do so if any occur to you, as well. In the meantime I am resolving it as NEEDS INFO. Thanks for the suggestion" http://www.w3.org/Bugs/Public/show_bug.cgi?id=11152 3. REOPENED BUGS: 3.1 Bug 11540: "The willful violation clause is most unwise. A standard should not violate another standard for any reason..." reported by contributor@whatwg.org. (Post Last Call1 Bug) Reopened by Laura Carlson. Comment: "Reopening. Would like to hear editor's rationale. Also applicable to 'willful violations' of WCAG and other accessibility guidelines." http://www.w3.org/Bugs/Public/show_bug.cgi?id=11540#c3 4. NEW BUGS (All of these are Post Last Call1 Bugs): 4.1 Bug 11533: "Clarify if specially focusable elements mean 'all elements with defined valid tabindex' or 'elements with a tabindex that allows sequential focusing.'" reported by contributor@whatwg.org. http://www.w3.org/Bugs/Public/show_bug.cgi?id=11533 4.1 Bug 11557: "Authors should not be allowed to specify roles on elements that they already have by default. It's redundant and encourages authors to add roles in cargo-cult fashion on the theory that this will improve their accessibility reported by contributor@whatwg.org http://www.w3.org/Bugs/Public/show_bug.cgi?id=11557 5. CLOSED BUGS: 5.1 Bug 10645: "Add a modal attribute to html5 to indicate a modal segment of the DOM (modal dialog)" reported by Everett Zufelt. Sam Ruby closed this bug without prejudice as no one had written a Change Proposal by the deadline. He added the "WGDecision" keyword. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10645#c19 6. "A11yTF" KEYWORD BACKLOG: We currently have 29 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 7. 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, 18 December 2010 18:16:32 UTC