<scribe> scribe: dmontalvo
Wilco: I have updated the sheet
quite significantly
... I commented I have linked things from several places
... Now it has some general info about what the document is for
and some how-tos
... documentation on where different pieces of data come
from
... I have hidden some tabs that we don't need to look at
regularly
... Created a "surveys" tab, I see this is working as people
are filling in the surveys
Aron: I put "no" into one of the answers but then changed my mind. Can I change that in the spreadsheet?
Wilco: I don't think you can't.
You can change the data that is on the hidden tabs
... There is a "survey results" tab, you should be able to find
your response there and edit it accordingly
Trevor: I think the QA is a little broken. It is putting the ready made answers in the second column
Wilco: I will take a look
... Shall I lock these tabs once created?
Aron: Is it only members of the TF that have access to the spreadsheet and the form?
Wilco: I think the form is public, but only people in the TF has editing
Trevor: I need a third reviewer for my PR, the others said it works
Wilco: Will take a look
Kathy: The track description
Shadi said we should go back to AGWG
... We did when it was about headings and bypass blocks
Daniel: Discussed with Michael. As it is advisory, that technique probably would not need to be there anyway
Wilco: Good point, the technique should not be there anyway
<kathyeng> https://github.com/w3c/wcag-act-rules/issues/56
https://github.com/w3c/wcag-act-rules/issues/57
Daniel: I will take a stub at
fixing these issues
... The one thing to discuss is terminology, how ddo we call
the rules
... Shawn proposes to keep the group name but when referring to
rules use WCAG2 Testing rules or just Testing rules depending
on context
Wilco: I think the other things
do not need more discussion
... I will try to see if I can resolve this by next week
Kathy: Shadi also talked about the videos, for us to figure out if we want to create a transcript, maybe an explanation about the topic. People may not watch 30-minute videos, but at least we would have some information in that page
Wilco: Where the videos included
in the PR? I think the they are not
... We could discuss videos later when we deal with this
PR
... I have been working on my scripts to link to the test
cases. That script works but it does not work when checking in
to Netlify, I am working with Hidde on the details
... I think I will keep these changes for a later PR
Wilco: I reached out to some
implementors. We got positive responses. Everything that is
already migrated we have the OK to publish
... And also new implementors that may contribute by the end of
August
... Some are interested, and they may contribute in the
future
Karen: Exciting.
Wilco: Overall looking
positive
... We have only reached out to orgs we have talked to in the
past. There are many more that could potentially contribute
<Wilco> https://github.com/act-rules/act-rules.github.io/pulls
Wilco: #1563 seems to be related, I am approving that
Karen: I could take a look
wilco: I have given you write
access Karen
... "Video audio fix" I will do that
... "Definitions of text instructions is in draft"
... Another for Tod to look into, I think we need at least 1
week for review
... #1674 Update included in the accessibility tree
Kathy: I think it is ready for
review
... I think in the last note of the conversation I provided a
link for the definition and copied it there. I think it already
says what we wanted it to say
Wilco: I don't think so, that is something else. An element with ARIA hidden is still not supposed to be in the accessibility tree
Kathy: Is there something else?
Wilco: I thought we said we were going to explicitly say in the definition that elements with aria-hidden="true" are not supposed to be on the accessibility tree
Aron: The note says that
Wilco: First it is a note, and then it is assuming that, but does not say it explicitly
Kathy: Not in a note, right? Do you want to leave the note as is?
Wilco: I think the note is good, I am open to suggestions
Aron: Would it be better if that wasn't a note but underneath that descriptions we had a note that some browsers still expose these elements?
Wilco: We could do something like that
Kathy: I will take a stub at it
Trevor: I can take a look at #1674
Wilco: I am bit blocked on the
semantic role thing, we need to wait for people to review
... The description track is one Kathy is doing, #1665
... #1555 What is the status?
... It looks like you did the changes but you did not dismiss
the reviews. This is now ready for another review, I will do
that
... I am approving it
Daniel: Will take a look at it
Aron: I will have a look at it
Wilco: #1548
Aron: I have more work to do with
it for when the number of data cells in the rows are not equal
and then you span rows instead of columns
... The behavior seems to be that if you span the upper row,
those spanning rows are added to the bottom
... Also received another examples to work with, but there was
a different item that was failing. I don't think it is an
issue, it reflects the inconsistencies on how some browsers
handle this
Wilco: Have now these survey
tabs
... First comment on the letter spacing is mine, what we do
about this WCAG interpretation
... It seems to me that adding these assumptions about what
WCAG intended was useful for rules under the CG, this seems
like an odd phrase to put in a W3C rule.
Trevor: Thought about other ways to test it. If not, this assumption still needs to exist.
Wilco: This started becoming an
issue with line-hight
... What is the intent for WCAG is something would need to be
in the understanding doc instead of in a rule. We may want to
suggest that be in the understanding
Aron: Good idea
Karen: I agree
Wilco: Is there anything beyond this Trevor?
Trevor: Don't think so, I agree
Wilco: I will take this up
Aron: This rule assumes that if you have the letter spacing with !important there is no mechanism to override it, but you can do it by taking every single DOM node and override these styles. If so, the rule would always pass
Wilco: It is kind of the
intention of this assumption. You are right. This SC is not
particularly clear on what needs to be done anyway.
... If you are only interested in doing this in a browser that
supports user origin styles, you can do this. It are extensions
that add styles to the website to add line spacing
... You could have this not being a problem depending on the
accessibility support you have. Are you OK with this?
Aron: Yes.
Wilco: For those who did not fill
the survey in, please do. In the survey there is a link to the
rule that goes to the WAI website
... I may need to tweak the links for these rules if they get
outdated
... Other rules: implementation data, Trevor says no
Trevor: We discussed that PR already, I would need to update
Wilco: Have not come up with an idea of how to update comment. Need to include that in the survey. Maybe looking at the last time one's name si used
Trevor: Mainly updating only the "Yes", "No", "I don't know" dropdown boxes
Wilco: I'd rather we do
everything through the forms
... I need to look at how to work with multiple responses
Kathy: Are we still taking these responses and opening an issue like we did before?
Wilco: I think we would just make
the changes
... If we were to open an issue, we should assign that to the
liaison
Kathy: We can only open the examples from the ACT-CG version
Wilco: Would you prefer that I change those links to the CG until we migrate everything?
Kathy: I do usually test the examples, for me it would be easier
Wilco: Surveys are due next Thursday, please complete before next meeting
Aron: Is it set automatically that every changes made to the rule get updated?
Wilco: No. It is on the CG, but no in WAI website.