11 Dec 2007


See also: IRC log


Shadi, Drew, Christophe, Vangelis, CarlosI



45 new test samples uploaded

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

should be fewer issues during structure review due to scricter rules.

all new test samples are in the wiki

previous 3 comments were from Christophe

Shadi forwarded SSH key to systems team (AJL)

WCAG working Group has approved Working Draft. Last Call draft expected very soon (SAZ)

<CarlosV> Connecting from review meeting ;-)

When Last Call comes out, more focus on techniques and failures (SAZ)

Reviewing test samples for current working draft

CS: No new reviews this week.
... Fixed all the issues found by CV last week. Should be ready for another review. Many test samples with CSS and Javascript code inside HTML files. In the newest test files, these issues should not exist.
... CI raised issue of primary and complexity attibutes. They are required in TCDL2, may want to make them optional

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

<shadi> http://www.w3.org/WAI/ER/tests/xhtml/metadata/sc1.3.1_l1_045.xml

<shadi> <rule primary="yes" xlink:href="http://bentoweb.org/refs/rulesets.xml#WCAG2_20060427_1.3_content-structure-separation-programmatic">

SAZ: Is the question, is primary always "yes"? ie: is it always redundant?

CI: This is a compatability issue.
... In our use case, we should focus on the primary rule. The sample will map to one rule.

CS: That means the test sample needs to pass all of WCAG except the primary rule.

SAZ: Each test sample must link to at least one technique. One test sample could meet more than one technique or use case. A test sample can show more than one thing, so it makes sense to have a primary and a secondary.

CI: We decided some time ago we would focus on one WCAG success criterion in each test sample.

SAZ: If you do not meet 1.4.3 you will not meet 1.4.5. Some of the SC are in direct relationship to each other. In that case, its useful to have this relationship info in the metadata as well.
... The question that CI raises is what is the criteria for calling something primary vs secondary.

<shadi> vk: in BenToWeb we use rules to point to different version of the WCAG documents

VK: in BenToWeb, we also use 'primary="no"' to reference versions of the same SC in older WCAG drafts

<carlosI> Not sure what the "it must not combine several issues in one test" mean if we use several rules

CS: Easiest way to proceed is to make primary attribute optional. Make the default value yes, but this removes the possibility to map to several SC.

<EtnaRosso> hi Christophe hi all

CI: if we allow the use of several rules, not sure what it means to combine several issues into 1 test. If we do this, we need to change the first step in the content review.

<EtnaRosso> what is this channel about?

CS: We need to clarify what "issue" means. The terminology is different between the WCAG doc and the review process document.

<scribe> ACTION: CI to continue discussion of primary and secondary attributes on the mailing list [recorded in http://www.w3.org/2007/12/11-tsdtf-minutes.html#action01]

CS: RR has uploaded test cases to the wiki

<EtnaRosso> ah ok it is a "one time" channel

Test suite ID in metadata

<EtnaRosso> see you gui, have a nice meeting

<Christophe> Test Suite ID: http://lists.w3.org/Archives/Public/public-wai-ert-tsdtf/2007Dec/0000.html

Continue this discussion on the mailing list.

Next meeting 8 January 2008

<shadi> no thanks, i'll do that

Summary of Action Items

[NEW] ACTION: CI to continue discussion of primary and secondary attributes on the mailing list [recorded in http://www.w3.org/2007/12/11-tsdtf-minutes.html#action01]
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.128 (CVS log)
$Date: 2008/01/07 17:32:31 $