TSD TF

Reporting coverage issues to WCAG WG

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2007Mar/0002.html

http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2007Mar/0002.html

CV: summarize thread

SAZ: the mailing list might not be good place to store issues - better store in tracking system
... should keep discussion in our mailing list - keep it in one mailing list

CS: refer to before raised to WCAG or after?

SAZ: all in one mailing list

CV: everybody lese in gl mailing list?
... dont have many resources - need be efficient

SAZ: skip for now. sending to WCAG does not help now. Document issues somewhere and then point them there
... time for time just send summary
... just to be aware of this work

CV: how update wiki page? leave link for later?

<shadi> http://www.w3.org/2006/tsdtf/CoverageIssues

CV: similar template with review but can come from authors too

<shadi> http://www.w3.org/2006/tsdtf/TestSampleStatusList

SAZ: can this be integrated to status list somehow ?
... could be in the status column
... add another column (issue) and in column link the template - staff need to comm to wcag
... if there are open issues need to come to resolution-> this is recorded in issues for wcag wg

CV: if the issue come from the author it come in the beginning

SAZ: whenever it comes it needs a TF resolution
... if author has a comment about WCAG work this needs to be raised to wcag list not here

CV: talking about someone from TF

SAZ: put that in metadata - on review discuss in TF if this issue need to be raised to wcag

<shadi> http://www.w3.org/WAI/ER/tests/usingTCDL

CS: use expected result
... and document it in tech comments

<Christophe> For example, use expectedResult (cannotTell/pass/fail) attribute on location element, and document issue in techComment element.

SAZ: unclear what the result will be
... for now skip and just use techComment field

<shadi> RESOLUTION: if the test sample *author* identifies a potential issue, then add a comment in the techComment field of the metadata

SAZ: an entry for content review : responsible to raise the issue

<shadi> ACTION: CV to create an issues template in the wiki [recorded in http://www.w3.org/2007/03/13-tsdtf-irc]

<shadi> ACTION: CS to add an "issues" coloumn to the status list [recorded in http://www.w3.org/2007/03/13-tsdtf-irc]

<shadi> ACTION: CS to add description for the techComment field in the metadata document [recorded in http://www.w3.org/2007/03/13-tsdtf-irc]

<shadi> ACTION: SAZ update the checklist for content review to reflect raising issues [recorded in http://www.w3.org/2007/03/13-tsdtf-irc]

<shadi> ACTION: SAZ update step 3 of the process document to reflect raising issues [recorded in http://www.w3.org/2007/03/13-tsdtf-irc]

<shadi> ACTION: EV and DO to add their uploaded test sample to the status list# [recorded in http://www.w3.org/2007/03/13-tsdtf-irc]

<shadi> ACTION: CI to repeat the reviews but this time using the wiki and updated documents [recorded in http://www.w3.org/2007/03/13-tsdtf-irc]

<shadi> ACTION: CV to get in contact with non-BenToWeb'ers and get them to review test samples [recorded in http://www.w3.org/2007/03/13-tsdtf-irc]

<shadi> http://www.mozilla.org/projects/testopia/

<shadi> next mereting: Tuesday 27 March