Wilco: We have a new member- Todd
<Wilco> https://act-rules.github.io/rules/
Wilco: providing context- we would like migrate rules from ACT rules community to W3c
Wilco: there is a migrated status in the spreadsheet- added today
<Wilco> https://github.com/w3c/wcag-act-rules/pull/53
Wilco: I've started copying all of the rules that have been accepted
<shadi> https://www.w3.org/WAI/standards-guidelines/act/rules/
<shadi> https://www.w3.org/WAI/standards-guidelines/act/rules/html-page-lang-b5c3f8/
<shadi> https://www.w3.org/WAI/standards-guidelines/act/rules/html-page-non-empty-title-2779a5/
Shadi: see the list of published rules. When you look at the HTML page lang it has left navigation
... probably related to metadata
Wilco: I will have a look at that
Shadi: Let me know if there is any trouble with that, will help
<shadi> https://w3c.github.io/wai-wcag-supporting-documents-redesign/
<shadi> https://www.w3.org/WAI/standards-guidelines/act/rules/html-page-non-empty-title-2779a5/
Shadi: HTML has non-empty title- for proposed rules we need some sort of big banner that this is a proposed rule and we're looking for implementations
... for the redesign project Wilco please work with Hidde
Wilco: Do we want proposed rules to be included in JSON file mapping?
Shadi: I think we have the approval from the working group
Kathy: Are we going to have working examples available?
Wilco: not at the moment
... Implementers will be looking at test cases through the community rules website
Shadi: the notice for proposed rules has a link to the community rules website
Wilco: I had a conversation with the AG chairs. We need to have everything ready for WCAG 2.2 release
... Zoomed text node is not clipped with CSS overflow- rules format issue
Kathy: failed example 3 did not fail in Edge but did in Chrome
Trevor: I had the same experience
https://act-rules.github.io/testcases/59br37/0413dfd271c1fba476c3e73d82f8d79a75c7300f.html
does not fail for me when I zoom text only
In Firefox does not fail
Wilco: we need to investigate it more closely
Trevor: we could move forward with it
I don't think we should
Kathy: I don't think we can move forward
Wilco: Heading has a non-empty accessible name- Kathy has a concern
Kathy: 2.4.6 should not be included as accessibility requirement
Wilco: I don't think this is actualy a problem
Empty headings are an issue in Firefox and NVDA
Wilco: I don't mind moving forward with it providing that we will revisit the accessibility support section before we propose it to AG
... Kathy, do you want to block it?
... Aron to have another look at the rule
... That's the end of the list
... I need to see if we haven't missed anything because the numbers do not add up. If that's ok with everybody, I will assign a couple more for next week
... As of next week, we could start working on some of the blocked rules
Wilco: we have a bunch of rules that need to be moved over. How do we go about that? Should each one of us take one rule a week?
makes sense to me
Wilco: ok, I think everybody is ok with that
... We do have quite a lot of open issues in the community rules repository. We could help out with it.
... we should try to avoid a growing list of issues. Should this be a homework too?
Trevor: I'm fine with that
I'm fine with that too
Wilco: ok
<Wilco> https://github.com/act-rules/act-rules.github.io/pulls
Wilco: we should go through the ones we created and see if someone needs helop
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/1635
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/1612
Wilco: Can you please help out reviewing 1612
Kathy: Sure
Todd: yes
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/1583
Wilco: can someone review 1583?
Trovor: I will
Wilco: that's all
... Thanks everybody. Have a great weekend!