- From: Wendy Chisholm <wendy@w3.org>
- Date: Tue, 19 Apr 2005 18:26:32 -0400
- To: wai-gl <w3c-wai-gl@w3.org>
This message outlines a possible framework for planning discussion of issues related to each of the guidelines. I've also included a detailed example of the framework applied to tasks for the next few weeks. Basic framework: week 1 - tuesday (mailing list): issue summary and proposals related to 3 guidelines and their success criteria. thursday (telecon): raise issues with proposals, close as many issues as can week 2 - tuesday (mailing list): updated summaries for 3 guidelines and their success criteria thursday (telecon): close issues for 3 guidelines and their success criteria week 3 - monday (mailing list): proposals for techniques and test cases related to the 3 guidelines and their success criteria closed the previous thursday. wednesday (telecon): raise issues with proposals, close as many issues as can (meanwhile - tuesday/thursday ala week 1 for the next set of 3 guidelines) week 4 - monday (mailing list): updated proposals for techniques and test cases for the 3 guidelines wednesday (telecon): close issues for techniques and test cases for 3 guidelines (meanwhile - tuesday/thursday ala week 2) An example of how this would look (G: = actions related to thursday telecons, T: = actions related to wednesday telecons). NOTE: This is to demonstrate how we could stagger the work and not necessarily the order we will proceed in the next few weeks. This is a proposal for discussion. We also will need to coordinate with people who have taken action items to determine when they are available to do what. week 1 18-Apr Tuesday: G: (mailing list) issue summaries and proposals for guidelines 1.1, 1.3, 2.4, 4.2 Wednesday: T: (telecon) Plan for addressing techniques and test suites for 1.1, 1.3, 2.4, 4.2 Thursday: G: (telecon) raise issues with summaries/proposals for 1.1, 1.3, 2.4, 4.2 week 2 25-Apr Tuesday: G: (mailing list) updated summaries and proposals for guidelines 1.1, 1.3, 2.4, 4.2 Wednesday: T: (telecon) [unsure] Thursday: G: (telecon) close issues with guidelines 1.1, 1.3, 2.4, 4.2 Friday: WCAG 2.0 Internal WD with: guidelines 1.1, 1.3, 2.4, 4.2 week 3 2-May Monday: T: (mailing list) issue summaries and proposals for HTML, CSS, and scripting techniques and tests for 1.1, 1.3, 2.4, 4.2 to the mailing list Tuesday: G: (mailing list) issue summaries and proposals for guidelines 2.3, 2.5, 3.1, presentation/structure Wednesday: T: (telecon) raise issues with HTML, CSS, scripting techniques and tests for 1.1, 1.3, 2.4, 4.2 Thursday: G: (telecon) raises issues with summaries/proposals 2.3, 2.5, 3.1 week 4 9-May Monday: T: (mailing list) updated summaries and proposals for HTML, CSS, and scripting techniques and tests for 1.1, 1.3, 2.4, 4.2 to the mailing list Tuesday: G: (mailing list) updated summaries and proposals for guidelines 2.3, 2.5, 3.1 Wednesday: T: (telecon) close issues with HTML, CSS, scripting techniques and tests for 1.1, 1.3, 2.4, 4.2 Thursday: G: (telecon) close issues with guidelines 2.3, 2.5, 3.1 Friday: WCAG 2.0 Internal WD with guidelines: 2.3, 2.5, 3.1 Thanks to Andi, Marnie (IBM), Gregg, John, Mike, and Judy for helping with the plan. We are playing with a variety of scenarios based on this framework to see how and when we can aim to get WCAG 2.0 to Recommendation. Best, --wendy -- wendy a chisholm world wide web consortium web accessibility initiative http://www.w3.org/WAI/ /--
Received on Tuesday, 19 April 2005 22:26:42 UTC