See also: IRC log
SAZ: the review process works
... but it is hard without tools
... talked about the necessary tool during last F2F
... try to get tools ready by January
... hopes this help to increase participation
... as the learning curve will be lower
CV: after looking the requirements don't think
could develope such a tool in a reasonable time
... thinks the best approach is try to get something and tune it
... something like Jira
<cvelasco> http://www.w3.org/WAI/ER/tests/WebInterface/Mockups/design.html
SAZ: the difficult part would be the WG tool, not the public interface
CV: also the validation process
SAZ: don't think it is so complicated
... we already have the schematron
... could run it on the CVS commit
... think could manage with something simple
... if there is a tool with that funcionality could do that
CI: thinks may be better try to manage with what we already have than trying to figure out how to do the same with a new tool
MS: would prefer to use an existing tool than
develope a new one
... concerns about the new development been more complicated than expected
SAZ: next step for WCAG 2 may be focusing on techniques
MC: not sure how to follow right now
... need to define the maintenance of understanding and techniques
documents
... don't expect much more work on accessibility support within the group
... to some extent need more communication between the WG and the TF to get
better understanding of the test samples potential usage
SAZ: an important question would be time commitment
CV: the first quarter would be very
difficult
... preparation of the project would be very time consuming
<Tim> I don't have answer right now but will come up with answer by Jan
SAZ: need a critical mass of time commitment
... net telecon
... two regrets Jan 6th one Jan 13th
... next telecon Jan 13th