<Wilco> https://www.w3.org/2002/09/wbs/93339/act-state-22-04-08/results
<Wilco> https://github.com/w3c/wcag-act/pull/516/files
Trevor: can't find the corresponding rules
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/1010
Wilco: not sure which they are either
Trevor: might need to be a little more clear
... on relation between applicable states and applicable transitions
... if you had different expectations and states
Wilco: when would that be different?
Trevor: maybe when you get into transitions
... might transition to a state that is not in the applicable states
Wilco: so expectations should remain true, while or until the transition to a different state is completed?
Trevor: we had ran into a specific example or two but not able to recall them now
Wilco: regardless of example, we probably want to have it this way
Kathy: applicable states is necessary whenever there are applicable states
... but there aren't necessarily always corresponding expected states
Trevor: transitions from one to the other might not always be clear
Wilco: using pseudo-class to always have a list of transitions?
Trevor: partially
... let's be very descriptive of the specific transitions
... maybe can play with definition of matching a pseudo-class
... for example to cover emulating pseudo-classes through JavaScript
... but might also introduce some vagueness
Wilco: two ways to do this kind of pseudo-class stuff
... either simulate the state (eg. simulate that the element is focus, for example by setting the corresponding styles)
... or actually trigger the state
... that distinction is not clearly made here
... another idea is to enumerate the inapplicable states instead of the applicable states
Trevor: how would you define the inapplicable state?
Wilco: gives you more flexibility
... for example decendant of aria-busy
Trevor: haven't thought about this
... intent of pseudo-class was not to limit other definitions
Wilco: we have definitions
Trevor: may need to be expanded
Daniel: could become very long
Trevor: could have flashing content during the transitions
... so wanted to include the transitions
Wilco: pseudo-classes do not have transitions
... but can see the issue
Trevor: very specific things that would be inspected
... would need to be defined better
Shadi: have you considered transitions as states?
... for example, the state of transitioning from "on" to "off"
Trevor: have not thought about it but can see it could be helpful
Wilco: think it is a good idea too
... next comment from me
Trevor: not want to do all permutations
... need to be selective of the key ones
Wilco: next steps?
... take this feedback back to the group and come up with another update?
Trevor: yes, can do that
... also come up with some examples
... would help if you can provide a brief write-up of the inapplicable states idea
Wilco: looks like getting a new process
... part of it is checking proposed rules
... thought of maybe assigning rules to people
... maybe two people per rule
... divided up over several coming weeks
... the usual quality assurance checking
... do people agree with this approach?
Trevor: yes, I like that
<Wilco> https://docs.google.com/spreadsheets/d/1OSkPFocXk4K3zYLnwS78WLsWO4PvE5yRcsauyefuIUI/edit?usp=sharing
Susan: sounds good Wilco!
Wilco: any objections to signing each of you up for 3 rules?
[no objections]
Wilco: how many rules?
[converging on 4-5 rules per week per person]
Wilco: will make assignments and send out the document
... will check-in every week
Wilco: WCAG 3 Conformance Meeting conflicts with our 29th April meeting
... can we move?
... hour earlier or same time the day before (Wednesday)
[none of the options work]
Wilco: so will cancel the 29th but you will still have homework!