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

Criteria for "a11yTF" keyword application

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Sun, 21 Mar 2010 18:58:07 -0500
Message-ID: <1c8dbcaa1003211658l20b1cf6wd57aff3b5c41c990@mail.gmail.com>
To: "Michael(tm) Smith" <mike@w3.org>, Janina Sajka <janina@rednote.net>
Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hi Mike, Janina, and everyone,

Thank you for going over the bug report in last week's teleconference.
I appreciate the discussion on establishing bug criteria for "a11yTF"
keyword application. The relevant part of the minutes [1] and some
comments from me for consideration.

> MS: There is a non trivial cost to taking up these issues with the TF.
> ... We need to agree criteria for our decisions to take on issues.
> Is that not just based on importance?
> MS: Could you take that to the list, that would be great?
> I get ya
> JS: Yes, it takes time
> MS: At one extreme we just take them all on.
> ... But we should decide where and how to draw the line.

This is a good idea, Mike.

> JS: Michael did try to group them to make it easier.

Yes the topic groupings are useful. Thank you Michael.

But we have had a11y bugs submitted since Michael made his cut that
are instrumental to the current HTMLWG tracker alt issue 31 [1] [2].
Plus there are a couple of bugs that are instrumental to Issue 31 that
were missed in the initial a11ytf keyword tagging.

> MS: It is a matter of cycles

This is true. Some suggested criteria:

For a bug to have the a11ytf keyword applied, it:

* must be a bug that at least one task force member has volunteered
and agreed to actively work on and see through to closure. (This may
mean drafting, filing, commenting, escalating, writing surveys,
writing change proposals, etc) AND
* could be a bug whose purpose is to expedite an existing tracker issue, OR
* could be a bug that has dependency relationship with an existing bug
that the task force has already accepted, OR
* could be a bug that has a blocker relationship with an existing bug
that the task force has already accepted, OR
* could be a new bug that reports a problem where HTML 5 provides
guidance that conflicts with WCAG, UAAG, or ATAG, OR
* ?

Thanks for your consideration.

Best Regards,

[1] http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0401.html
[2] http://lists.w3.org/Archives/Public/public-html-a11y/2010Mar/0007.html
[3] Bug 8716 dependency tree:

Laura L. Carlson
Received on Sunday, 21 March 2010 23:58:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:33 UTC