Wilco: Do we want to allow expectations interlink
... What do we mean by distinct?
... recognizably different
... IBM is not objecting to it being linked
... Alistair had some objections to that
Anne: As per Alistair, he wanted rules to be atomic, but we feel it will be difficult to pass if we do that
Wilco: My take on it is, a conformance statement, defining WCAG, i feel we are overloading
Charu: how do we clarify what we mean by expectations
Anne: Kasper suggested Assertions
Wilco: I feel assertions is saying the same thing, it does not add anything to explain
Anne: A positive statement
Wilco: I am not sure where to go with this, could we say positive statement
Shadi: can you explain what is the issue with assertion?
Wilco: its saying the same thing
Stein Erik: i would vote for assertion
Wilco: Ok willing to go with that
Anne: its about changing the description not the heading
<Wilco> "An expectation is an assertion that must be true about each test target (see Applicability)."
Wilco: Any objection to this
+1
Stein Erik: This is the discussion around how agnostic we should be, not to be too specific or more general
Wilco: I like it
Shadi: i see as they are contradicting
Stein Erik: yes
Shadi: It is a edit with a change of meaning
Wilco: Can you explain why it is different
Shadi: One is saying its a DOM tree, we don't care how it
is constructed, the other is saying we build the DOM tree as per the
specification
... DOM tree is restricted to a DOM
Stein Erik: does it really matter
Shadi: if it is not a DOM tree why do we call it so
Stein Erik: Do we really care if it is a DOMx or DOM since we will explain it any ways
Shadi: Should we come back to this for the next drop?
Wilco: this for the next drop
Shadi: Ok then we need to discuss this
Wilco: If your technology has a faulty stack or not following specs,
Stein Erik:If we say DOM tree, do we expect it to be well defined DOM
Shadi: As per Romain, a DOM tree is only when defined as a DOM
Stein Erik: Anyone else has a strong opinion
Shadi: It is a suggestion to improve the spec
Wilco: Ok any objections?
... if no i will put in a comment and assign it to Romain
Wilco: N/A means pass
Stein Erik: yes, if he says that i agree
Wilco: only when mapping to WCAG 2x, N/A is a Pass
Shadi: For the format we use we can create a subclass and pretend it does not exist
Stein Erik: i can write it in an email
Wilco: Romain is saying 2 types of test cases, one for
applicability and one for expectations
... don't see any benefit to distinguishing that
Shadi: every pass is applicable
Wilco: yes
Shadi: idea is what if the test case has applicable content
and the test case does not return pass or fail
... Alistair means if there was a pass or fail, then it was applicable
Wilco: i have a list of results of test, if i get more or do not get an outcome than it is a failure
Shadi: what if we fail for the wrong reason
... Romain means you need to cross match the applicability
Wilco: that is implicit
Shadi: you compare that you got the correct results for the
correct elements
... if you get a mismatch, you have to manually check, that is debugging
... Romain has a point, checking 2 aspects, makes debugging easy
Wilco: ok
Shadi: one question, the documentation seems stern, is getting community feedback only or come with some follow up
Stein Erik: You can send an email of your idea, if we accept everything we might drown
Wilco: Yeah kind a like the open source, if the idea is good it will get picked up
Shadi: is there an incentive for any organization to go through the process, we need to find a balance and not have a very high threshold or very low
Wilco: this is of value to us
Stein Erik: this is also of value to us
Anne: if it does not sound open enough, we can add you can send an email to us
Wilco: Community group is where to take that feedback