- From: Martin Kliehm <martin.kliehm@namics.com>
- Date: Tue, 26 Oct 2010 18:17:40 +0200
- To: HTML Accessibility Task Force <public-html-a11y@w3.org>
http://www.w3.org/2010/10/26-a11y-bugs-minutes.html - DRAFT - HTML Accessibility TF Bug Triage Sub-Group 26 Oct 2010 Present kliehm, Michael_Cooper, Cooper, Marco_Ranon Regrets Chair Martin_Kliehm Scribe kliehm Contents * Topics 1. Previous homework 2. Next week * Summary of Action Items TOPIC: Previous homework <MichaelC> 10931 http://www.w3.org/Bugs/Public/show_bug.cgi?id=10931 <MichaelC> 10932 http://www.w3.org/Bugs/Public/show_bug.cgi?id=10932 <MichaelC> Editor response ok; not a TF priority; assigning to Cynthia to follow <MichaelC> 10933 http://www.w3.org/Bugs/Public/show_bug.cgi?id=10933 <MichaelC> assign to Michael to provide info; is a TF priority <Marco_Ranon> 10935 http://www.w3.org/Bugs/Public/show_bug.cgi?id=10935 <MichaelC> ACTION: Michael to get a bugzilla component created for the HTML Accessibility API Guide, and assign bug 10935 to that [recorded in http://www.w3.org/2010/10/26-a11y-bugs-minutes.html#action01] <Marco_Ranon> http://www.w3.org/html/wg/tracker/issues/30 Bug 10938, 10967, 11012 are related to ISSUE-30 longdesc and dependent on bug 10455 where a general solution needs to be drafted. Adding a11yTF and TrackerIssue keywords <MichaelC> adding dependency to 10455 Bug 10941: http://www.w3.org/Bugs/Public/show_bug.cgi?id=10941 Bug triage sub-team thinks this is a A11Y TF priority. Assigning to Silvia to continue work on this. Needs to be synchronized with the other media work in the media sub-group. http://www.w3.org/Bugs/Public/show_bug.cgi?id=10964 <MichaelC> assigning to Rich <Marco_Ranon> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10988 There's already an element for a slider functionality in HTML5, so this is not a TF priority <Marco_Ranon> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10994 http://www.w3.org/Bugs/Public/show_bug.cgi?id=10994 <Marco_Ranon> 10994 <Joshue> thanks <Joshue> URL? <Marco_Ranon> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10994 <Joshue> Are we just looking at keyboard related bugs? <Marco_Ranon> Michael's home work <Joshue> Should bugs that have been accepted but that don't have the a11ytf keyword, but are relevant still be tagged retrospectively? <MichaelC> Editors draft of HTML 5 <Joshue> Bug 10772 - accesskey and an ordered set of unique space-separated tokens [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10772 <Joshue> Bug 10774 - fallback for accesskey insufficiently defined <Marco_Ranon> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10774 <Joshue> I suggest escalating this bug. <Joshue> Bug 10775 - how is user to decide which set of access keys to use? <Marco_Ranon> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10775 <Joshue> WHATWG revision r5596. <Joshue> Bug 10776 - accesskey value token subsets <Marco_Ranon> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10776 <Joshue> Bug 10777 - user agent assignment of modifier keys subset of accesskey processing subset <Marco_Ranon> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10777 <Joshue> Bug 10778 - use element.accessKeyLabel to generate list of available accesskeys <Marco_Ranon> http://www.w3.org/Bugs/Public/show_bug.cgi?id=10778 10775-10778: The HTML A11y Bug Triage Subteam decided that this not an issue and that Gregory should escalate this bug if he feels it is warranted. We decided that 10888 would be the master bug for all accesskey related issues. TOPIC: Next week Meeting face to face next week at TPAC Summary of Action Items [NEW] ACTION: Michael to get a bugzilla component created for the HTML Accessibility API Guide, and assign bug 10935 to that [recorded in http://www.w3.org/2010/10/26-a11y-bugs-minutes.html#action01]
Received on Tuesday, 26 October 2010 16:18:17 UTC