wilco: most did the homework
... everything checked doesn't need discussing, discuss those that have one reject and one check, no discussion if both rejected
... first to discuss is attributes not duplicated
daniel: descriptions for test cases not up to date with editorial, pull request open, should this be addressed now before moving to website
trevor: like suggestion to improve descriptions
daniel: improvement to descriptions suggestion will likely come later
wilco: not sure this should be held up
daniel: ok with changing to checked
<Wilco> https://act-rules.github.io/rules/4c31df
aron: rejected because change to definition of instrument, second expectation not going to be needed. Note to instrument definition will assume accessibility.
... will change test example descriptions and references to second expectation
wilco: is this a blocker?
aron: ok with moving it forward
... change it to checked
wilco: autocomplete aron rejected
aron: substantial change to applicability of rule, auditors may fail rule on or off. update will not check on/off. Browsers do not respect control group.
... test examples will also change
wilco: agree. Ex: autocomplete username is not allowed on type=email but it works in browsers fine. CG would remove second expectation. Rule is too strict.
aron: yes, only safari respected type attribute
shadi: rule follows spec, not what browsers do
wilco: agree with aron to not move forward until PR is merged
daniel: how to keep track of decisions in sheet?
wilco: open an issue to explain reject
<Wilco> https://act-rules.github.io/rules/cf77f2
wilco: kathy said no
kathy: headings don't bypass blocks of content
wilco: inclined to support since it follows wcag
aron: agree with wilco
wilco: spec is documented to include headings
<Aron> https://www.w3.org/WAI/WCAG21/Techniques/html/H69.html
aron: H69 sufficient technique for headings at beginning of content for bypass blocks
wilco: ongoing WG discussion of it now
... will reject
... next Device motion does not follow rules format
<Wilco> https://act-rules.github.io/rules/7677a9#expectation
wilco: rule is ambiguous and not allowed in rules format
... how event is fired is not captured
... will reject
... add PR or issue link for rejections
... next week's assignments and no meeting next week
wilco: CFC for new publishing process, no objections. accepted and merged
... working on proposal on how to set up publishing system.
daniel: permalinks problem for screen readers
wilco: shadi suggested to include reason for rejections in spreadsheet.
shadi: expand pull down to see why it was rejected in spreadsheet.
daniel: wider column for comments for extra information
wilco: would like information in repo. would help discussion to have reason in spreadsheet
trevor: would like to discuss with other reviewer before meeting
wilco: will add more options for more data
wilco: waiting for AG chairs for ok to announce
... May 14 and May 21. save dates
close item 3
wilco: shadi, daniel, and I think publishing implementation data and rules when wcag 2.2 is out
<Wilco> https://act-rules.github.io/pages/implementations/overview/
wilco: overview page, lists implementers, report links with implementation tables
... improvements could be made but can go on wai website
... might encourage other implementers if they see implementations. more visibility with 2.2 release
trevor: no concerns
kathy: take Trusted Tester off if it doesn't have implementation data.
... no objection to publishing
shadi: implementers create repo for implementations to be added. need to talk about mechanics
... easier to have them all in one place
wilco: will talk to Hidde