- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Mon, 12 Apr 2010 11:22:34 -0500
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: HTML Accessibility Task Force <public-html-a11y@w3.org>
Hi Silvia, > Not sure what that means, but if I'm sorry if I added the "a11ytf" > keyword by mistake. I thought it was one of my actions coming out of > the F2F meeting. No problem, Silvia. A procedure and criteria for adding the "a11ytf" has not been agreed to yet so there is bound to be confusion. If you had an action coming out of a teleconference to create a bug, that certainly seems to me to be good criteria. Same with the bugs that Maciej asked me to file for the text alternative change proposal. I put up a page in the Wiki to track the matter and brainstorm ideas. Please add your thoughts. Edit at will. http://www.w3.org/WAI/PF/HTML/wiki/Bugs/KeywordCriteria The initial set of "A11y" bugs which were determined to be accepted [1] or rejected [2] had a boiler plate statement on them by Michael Cooper. Accept statement: The HTML Accessibility Task Force intends to track these issues, per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html. Reject statement: "Per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html, the HTML A11Y TF does not plan to formally work on this issue at this time. This does not mean the TF has no interest in it, but does not have immediate plans to work on it. The TF may review the issue in the future." To avoid confusion going forward, we should probably have similar language and a link to the decision, added to a11ytf bugs. That would clearly document that the task force has decided to work on an item or decline. Best Regards, Laura [1] http://www.w3.org/WAI/PF/HTML/wiki/Bugs/accepted [2] http://www.w3.org/WAI/PF/HTML/wiki/Bugs/rejected -- Laura L. Carlson
Received on Monday, 12 April 2010 16:23:07 UTC