<scribe> scribe: aron
<Wilco_> https://github.com/act-rules/act-rules.github.io/pull/1609#issuecomment-853952691
Wilco: 3 final calls sent today, 1 from me last week
Wilco: regarding Patrick's
comment (simplyfiyng rule a bit more)- reasonable, not a
blocker
... I will make a change, we'll have to make another final call
for it
... have a look at the other final call rules and leave a
review
Carlos: nice seeing more reviews in the past couple of weeks
Wilco: the scan of unpublished
rules completed. A couple of them are blocked and the TF will
look into them.
... almost 70 rules will get published as proposed rules.
Carlos: what's the timeline? will the rules exist in both places?
Wilco: hopefully by the end of
this year.
... what is left is the automation part.
... the rules will not be removed from the community group web
page immediately
Wilco: I wanted to ask if people would be up for talking about ACT
Jean-Yves: I submitted a talk for ID24, we'll see next week
Wilco: please do so
I will help out, not sure where and when
Carlos: publish on ACT slack channel talks about ACT so that people can volunteer
Shadi: I mention ACT whenever I can, e.g. when talking about WCAG 2.2. or about tools. One of the things to be careful of are distinguish between your opinion and talking on behalf of the group
Wilco: good point
... good to provide accurate information about the inner
working, what is ACT-TF and what is ACT-R
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/assigned/WilcoFiers
<ToddLibby> I don't mind speaking at all and anywhere I can help out, I will certainly do so.
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/459
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/1593 hoping to have a PR open for semantic element next time
Wilco: done define SVG and HTML
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/assigned/ajanec01
will create pr for https://github.com/act-rules/act-rules.github.io/issues/1603 and try to fix it
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/assigned/carlosapaduarte
Carlos: I hope to address #1502
in next week
... #1445 should also be address in next week
<Wilco_> https://github.com/act-rules/act-rules.github.io/issues/assigned/Jym77
Jean-Yves: I have pr on most of the issues
Jean_Yves: I think there are two pr that need reviews
Jean-Yves: the rest requires some group discussion
Daniel: #1576 has a pr so I will send an email with final call
Wilco: aria-errormessage
references non-existing element
... it may happen when the form control does not have a
reference
Jean-Yves: I guess we may change
the description a bit more clear what is "valid" id
... "valid" does not mean existing
Wilco: resolution: leave a comment in the pr to explain "valid"
Wilco: my suggestion is to change
phrase "each test target" to something more explicitly related
to applicability
... my impression is that people did not like "each applicable
button" but "each applicable element" was better
Carlos: "each applicable element"
may not be appropriate, the more explicit version, e.g. "each
applicable attribute" is more appropriate
... if we go with the more explicit version people may stop
looking at the applicability section
Wilco: I'm not too worry about it
Daniel: test target may not be understandable by some pople but each alternative may be problemmatic in its own terms
Jean-Yves: test targets are at
the same level as outcomes and we could have a definition of
test target
... it's not too helpful to be going to the definition
Carlos: did you have a feedback from someone about test target phrase?
Wilco: no, something I've not
been happy about
... would you like to change it or not?
... do you think it should be improved on?
-1
<CarlosD> -1
<Jean-Yves> -1
<ToddLibby> -1
<daniel-montalvo> -1
Wilco: pretty clear
Carlos: We can still link to the definition. What do you think?
Jean-Yves: we can do it when someone raises an issue
Wilco: resolution: I will close the issue
Wilco: does it work? This is to facilitate dictation software
Jean-Yves: splitting the numbers
could be better experience
... I think it is a failure
<Wilco_> https://www.w3.org/TR/spoken-html/
Will check it and document findings in the issue
Wilco: resolution: we try to figure out if this works reasonabily well and if it does that we allow the rule to be less strict
Carlos: I'm ok with it
Daniel: Me too
Jean-Yves: Yes
Wilco: resolution: I will create a pr
<Jean-Yves> https://github.com/act-rules/act-rules.github.io/pulls?q=is%3Aopen+is%3Apr+label%3A%22reviewers+wanted%22
This is scribe.perl Revision VERSION of 2020-12-31 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: aron, CarlosD, Jean-Yves, Wilco_, Daniel, ToddLibby Present: aron, CarlosD, Jean-Yves, Wilco_, Daniel, ToddLibby Found Scribe: aron Inferring ScribeNick: aron WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]