W3C home > Mailing lists > Public > public-html-a11y@w3.org > December 2010

Minutes: December 7: HTML Accessibility Bug Triage Sub-Team

From: Martin Kliehm <martin.kliehm@namics.com>
Date: Tue, 07 Dec 2010 18:14:18 +0100
Message-ID: <4CFE6B6A.100@namics.com>
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
CC: Joshue O Connor <joshue.oconnor@cfit.ie>, Michael Cooper <cooper@w3.org>, Marco Ranon <marco.ranon@rnib.org.uk>
http://www.w3.org/2010/12/07-a11y-bugs-minutes.html

====

HTML Accessibility Bug-Triage
07 Dec 2010

Attendees

Present
     Marco_Ranon, Michael_Cooper, Martin_Kliehm
Regrets
     Laura_Carlson
Chair
     Martin_Kliehm
Scribe
     kliehm

Contents

* Topics
   1. Triage of Laura's list of bugs awaiting the a11yTF keyword decision


TOPIC: Triage of Laura's list of bugs awaiting the a11yTF keyword decision

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6496

Assigning to Steve Faulkner as it is related to ISSUE-31, adding a11yTF 
keyword.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7076

The bug-triage sub-team doesn't consider this bug to be task force 
priority as the @coords attribute on the anchor element hasn't been 
implemented in many browsers since HTML4.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8646

@alt text in private communication: The bug-triage sub-team doesn't 
think this is a accessibility task force priority, no a11yTF keyword 
required.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9135

The link to the canvas 2D document has been removed again, so the bug 
should be reopened. Still the bug-triage sub-team doesn't think is task 
force priority.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9213#c1

<Marco_Ranon_> zackim, ??P24 is me

Although a @missing attribute is not part of the text alternatives 
package, the bug-triage sub-team doesn't think this is an accessibility 
task force priority.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9217

Since this bug is verified closed, the bug-triage sub-team doesn't think 
it's accessibility task force priority any longer.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9218

The bug-triage sub-team thinks since this is a duplicate it's not 
accessibility task force priority.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9233

The bug-triage sub-team doesn't think this is a priority for the 
accessibility task force.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9241

The bug-triage sub-team sees that there is a general issue regarding 
links to other W3C documents that should be addressed by the task force. 
But this particular bug shouldn't be task force priority.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9485

The bug-triage sub-team agrees with Henri's comment but is bringing it 
forward to the accessibility task force to achieve consensus.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10450

The bug-triage sub-team agrees this bug is fixed per bug #10919, Maciej 
please verify and close the bug.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10451

The bug-triage sub-team thinks this is task force priority. Assigning 
the bug to Cynthia Shelly so that is handled in ISSUE-129.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10452

The bug-triage sub-team thinks this is task force priority as it is 
closely related to ARIA mapping. Assigning the bug to Cynthia Shelly so 
that is handled in ISSUE-129.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10455

Adding a11yTF keyword since ISSUE-30 is still a hot topic on the mailing 
list.

MC: I suggest in order to make faster progress in the next bug-triage 
meeting handling the remaining bugs from this week's homework that each 
member prioritizes the bugs into easy bugs that could be addressed 
without much discussion at the beginning of the meeting, and bugs that 
need the discussion of all sub-team members.

+1

<Marco_Ranon> +1
Received on Tuesday, 7 December 2010 17:14:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:27 GMT