wilco: Everything has been filled out!
... last week of this homework stuff.
... video element visual content has strict accessible alternative, I said fine and kathy said wcag inconsitency
... there is a bit of an audio problem with some of the videos. need to update the test cases. we did say we were going to move forward
... kathy, should we prevent them from getting published
kathy: looking at my comment, 4 of the test cases weren't working properly, is that a minor fix.
wilco: I think it needs to be fixed, I don't think it prevent adding them as proposed rules.
... we know its not quite right, but the point of the examples is clear
kathyeng: when they do get published, the test cases will need to be fixed for implementations
aron: will those proposed rules have links to open issues?
wilco: they will not, that would not be a bad thing to add to the template.
... hearing a few opinions against so going to block it for now.
aron: we will need to block the other related video rules as well
daniel-montalvo: understanding that these rules are just on hold until we make some of the minor adjustment.
kathyeng: Is there a way to mark on the rule that it is ready for implementation? If test cases are broken then testers will have to come back later
wilco: at the moment I don't think so, just a way to see what issues exist for a rule.
... unsure if I know how to make that judgement, should it have no open issues, what types of issues could it have
... noting that this is somewhat inconsistent with what we have decided before.
... setting it to block, will need to do similar for other video rules with audio
... next rule, orientation of the page is not restricted by using css transform property.
kathyeng: we have discussed before, matter of determining what the S.C. is requiring
... when I read the S.C. and understanding, I interpret it as orientation upon opening should be oriented correctly.
... the rule is checking that while the content is open, rotate and then check and see if orientation.
wilco: this rule does not say that you should rotate the device. though it doesn't prohibit it either
kathy: the note in the expectation seems to say rotating while the content is open
wilco: there is some trickiness in this rule related to state. it doesn't tell you what orientation state different test cases should be in. actually it tells failure regardless of the state
... rule is failed if there are styles that prohibit orienting correctly
... should be a failure in either case for being opened or rotated.
kathy: I'm mostly looking at the note and determining if the S.C. requires the rotation or not
wilco: I think its worth a question to AG. Don't think the answer will change the rule, perhaps an additional assumption
kathy: If its just that when its open then the note under expectation should be updated.
wilco: video element auditory content has captions rule, has the same audio problems discussed above so will be blocked.
... video element visual content has audio description blocked for similar reasons.
... video element visual-only content has description track.
... the problem here is a description track can serve as an alternate
... wondering if we can still have the atomic rule, but should remove the atomic rule from its composite rule
<aron> +1
trevor: what does taking it out of the composite rule accomplish?
wilco: taking it out of the composite rule means that you can't satisfy the S.C. with it anymore
... issue becomes with the composite rule and not with the atomic rule.
... aria state or property has valid value editorial issues by aron and hard to understand by daniel
aron: it was more something I wasn't sure about. Problems with if elements can be referenced across shadow boundaries
wilco: at the moment you cannot reference across shadow boundaries, someone is working on an API.
... every DOM tree is its own self contained unit
... rule should maybe be updated to be same document tree or same shadow tree. Should have the same root element
aron: will leave a comment to make the expectation a bit more clear
daniel: I was having a problem with the same wording so that would help fix it
... alluding to the root would help.
wilco: marked as accepted w/ note
trevor: wanted to note we had a discussion awhile back about how this doesn't have a mapping
wilco: yep, planning to add as proposed and figure out what to do after that
... I will start doing some work to get the accepted rules into proposed. Will send out a CFC for everyone, AG has approved
... starting next week, we will start looking at resolving some of these issues.
aron: we can change the autocomplete rule to accepted
wilco: I think we should each take one of the blocked rules and see what progress we can make on it.
* assigning blocked rules for people to work on for next week *
wilco: we had a monday call with Silver. was hoping to get impressions
... we had meetings a couple weeks back, we are hoping to come up with a proposal for how to combine TF and Silver work
kathy: Think an hour is too short, there is a lot of word smithing going on. Do think its helpful since we need more detail and definition. Going in the right direction.
... the next meetings might move along more quickly.
wilco: Same, felt to me to be a bit chaotic, was not expecting as many people as showed up.
trevor: Feeling uncertain about how silver will be able to stay high level while also being specific enough for the testing purposes
aron: Is there a way to raise issues to get through them offline and bring them up in the meeting.
wilco: A lot of people don't want to work through github issues. Most of the work happens on calls.
... felt that the group pivoted rather quickly.
kathy: a lot of discussion about who needs to determine if a heading needs to be there.
... unsure if its obvious to everyone about how those requirements will be setup.
wilco: The plan is to continue these meetings for the next couple of weeks and to eventually come to a proposal that can come back to the wider group.
kathy: since we have a different workflow for them, is it something we can suggest to them to work on things through issues.
... might help move things forward faster
<shadi> +1 to not word-smithing during calls!
<ToddLibby> +1 to no wordsmithing as well!