scribe+ CarlosD
Jean-Yves: One 1-week call for
review from Helen which I'll merge after the meeting
... nothing on 2-week call
CarlosD: No updates from me
Wilco: Been doing TF work
... trying to get AG to review some of our rules
ToddL: Been doing reviews, but no PRs assigned to me
giacomo-petri: Been busy, so no
updates from me
... PR #2007 been stuck, it needs additional reviews
Jean-Yves: Waiting for reviews on
#1994 and #1923
... gave a try at the Role is permitted rule (#2084)
Wilco: Does anyone have plans to
write rules for WCAG 2.2?
... I will look at target size, but would appreciate pairing
with some one
Jean-Yves: We're also looking at
that, so I can pair with you
... WCAG 2.2 could be a topic for TPAC
... Focus not obscured might be one we can work on also
... but there are no good targets for fully automated
... we could focus on manual rules
Wilco: AG is changing the process
to review
... we've almost completed the anual review cycle
<Wilco> https://github.com/act-rules/act-rules.github.io/pull/2086
Jean-Yves: Remember to register... early bird ends Friday
Carlos: The event is from the TF
which is preventing CG members that are not W3C members from
registering
... Daniel is aware and the events team is working to change
the registration rules
Jean-Yves: Tom wanted to have more information about related rules on the background section
CarlosD: We could have templates for the different rationales
Wilco: It would be nice to have a
PR to start looking at this
... Do we want to apply this to every rule, or do we make it
optional?
Jean-Yves: We can start optional, assess the progress and then decide if we want to make it mandatory
<ToddL> +1 with this being optional to start and I'm okay with this.
Wilco: This is a non-issue... it has been solved by changes in the HTML in ARIA
Jean-Yves: In our rules we do not
target pseudo-elements, but we target things like visible text
that can be changed by pseudo-elements...
... how do we want to handle this? Ignore, have rules specific
for pseudo-elements, or have the current rules changed to
handle them?
Wilco: How can they be tested? We can't access them from the DOM API
Jean-Yves: In Alfa we have access to the CSS so we could access them, but we currently don't, and it would be a lot of work to do it
Wilco: What rules would we change?
Jean-Yves: There are some cases
Wilco: Do we have the language to talk about that in the rules?
Jean-Yves: I assume that in the CSS spec there would be something that we could use
Wilco: I believe these are such
extreme edge cases that I think is reasonable to ignore
them
... We could add exemples in rules that use the accessible name
computation, because in those we take the pseudo-elements into
account
... Are we trying to make implementations more difficult or is
this a real problem?
Jean-Yves: I agree that in most of the cases we are just creating false negatives, so I'm not too worried if we don't handle them
CarlosD: Agree that we do not need to worry and also that we could have some tests with pseudo-elements in rules that require accessible name
Jean-Yves: This overlaps with the next agenda item
Jean-Yves: I was changing
visibility test in Alfa to check for text that can be scrolled
into the viewport
... that applies to vertical and horizontal scroll, but we
don't have rules that test for that
... we have around 50 rules that use this definition, should we
update all, or just some of them?
... Could we have fake rules that would allow implementers to
check their implementations of the definitions?
... For exemple, a rule "Is the element visible" that would
have test cases for checking the implementation of the visible
definition
Wilco: That would only work for rules that have a boolean outcome?
Jean-Yves: Even for other rules we could have expectation that we control, for example, all accessible names would compute to "Hello World"
Wilco: I like that, but we should separate these rules and test cases from the others
Jean-Yves: Would it be better to have this as part of the web platform tests?
Wilco: How would we use it?
Jean-Yves: I need to look into having the possibility to automate from there
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) Succeeded: s/to. me/ to me/ Succeeded: s/platform directory/platform tests/ Default Present: CarlosD, ToddL, Wilco, giacomo-petri, harris, Jean-Yves Present: CarlosD, ToddL, Wilco, giacomo-petri, harris, Jean-Yves No ScribeNick specified. Guessing ScribeNick: CarlosD Inferring Scribes: CarlosD 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: 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]