- From: Léonie Watson <tink@tink.co.uk>
- Date: Wed, 13 Mar 2013 14:58:48 -0000
- To: "'Kelly Ford'" <Kelly.Ford@microsoft.com>, "'Jim Allan'" <jimallan@tsbvi.edu>
- Cc: "'HTML Accessibility Task Force'" <public-html-a11y@w3.org>, "'WAI-ua'" <w3c-wai-ua@w3.org>
- Message-ID: <002a01ce1ffb$47bd8c60$d738a520$@tink.co.uk>
Kelly, Thanks to you and the UAAG WG for agreeing to take a look at these bugs. Today we tagged them with the a11y_ua keyword and removed the a11ytf keyword. This query string should display them all: https://www.w3.org/Bugs/Public/buglist.cgi?keywords=a11y_ua Léonie. From: Kelly Ford [mailto:Kelly.Ford@microsoft.com] Sent: 12 December 2012 16:40 To: tink@tink.co.uk Cc: Judy Brewer; jimallan@tsbvi.edu; jeanne@w3.org Subject: RE: UA a11y bugs I will work on this in the next week, starting later today and appreciate you bring it to my attention. Kelly From: Léonie Watson [mailto:tink@tink.co.uk] Sent: Wednesday, December 12, 2012 8:39 AM To: Kelly Ford Cc: Judy Brewer; jimallan@tsbvi.edu; jeanne@w3.org Subject: UA a11y bugs Kelly, The HTML-A11y TF is trying to clear all a11y bugs marked resolved NeedsInfo/won’tFix. I’m reaching out to you and the UAAG WG for any help you might be able to offer. Several bugs are assigned to Greg Lowney [1]. I tried to get in touch with him earlier in the year, but as I don’t know him personally I’m not sure my emails reached him. Could I trouble you to ask him? Another bug is assigned to you Kelly [2]. If you’re able to review and respond to it, that would be a great help. We still have around 50 bugs to reassign, now that Hixie and/or the What WG are no longer active in this context [3]. The HTML-A11y bug triage team will be doing this over the next couple of weeks, but if you and/or the UAAG WG would have time to look through the list and identify any that fall within your remit, that would sincerely be appreciated. Essentially we need to review the reasons why each bug is marked NeedsInfo/won’tFix, and either close the bug, or re-open it with further information. In the latter case it may be sensible to move the bug to HTML.Next, rather than pursue it under the current CR. Thanks for your time and input on this. Léonie. [1] 13630, 13623, 13616, 13594, 13579, 13555, 13539. [2] 13564. [3] http://tinyurl.com/d9u2d2o
Received on Wednesday, 13 March 2013 14:59:25 UTC