<Sage> Having trouble getting in, but working on it

<Wilco> Same... I think the wrong zoom link is in the W3 calendar?

<Wilco> Kathy dmontalvo are you in?

<Kathy> I got invalid meeting ID

<Sage> That was my guess, based on the note that there is a new Zoom link. I also got invalid meeting ID

Scribe+

Zakim take up next

Annual Rule Reviews

Wilco: Why is there so many tabs open?
... there are a few gaps to cover from last time
... and some reviews are not complete

Shunguo: I found it hard to add my responses to the spreadsheet?

Wilco: There is a survey to complete to do this -and is will populate the spreadsheet directly

Sage: I would love some details to my personal email as work are making it complicated

Wilco: I have assigned a few more to others - please complete these by our last meeting this year
... We have some format and an issue with a PR: aknb7n
... We want them to look at the proposed rules first and why it was done this way
... Do we add 2.13 as a secondary requirement
... But it seems wrong to me as any time this rule fails both will fail

Helen: Is it because is it a AAA it should be secondary?

Wilco: No as it will fail regardless, and you do not need to report it if not testing AAA
... There is a bug IBM have here - but they can fix that I hope?

Tom: There is nothing here that makes it an exception then?

Shunguo: There are differences in FF and Chrome for iFrames - is it documented here?

Wilco: Not in this case as not required for this rule. It is a complicated and ongoing issue.
... Chrome is going to make iFrames focusable by default - so will only be Safari that does not focus them.
... Good to go?

Kathy: Yes

Wilco: 0ssw9k - same mapping with 2.1.3

<Kathy> scribe+

<Kathy> tom: will look at 2198 issue on inconsistent results

<Kathy> wilco: 2217 merged

<Kathy> tom: think rule is good to go

<Kathy> wilco: meta element rule responses from sage and suji

<Kathy> sage: partial consistency in rules format. True positive is not true

<Kathy> wilco: will review 4.14.1 Consistency for True positives failed test cases text

<Kathy> sage: #2207 may have been resolved

<Kathy> suji: failed example 1, no content loads

<Kathy> wilco: some content on the page, like a timer, would be helpful

<Kathy> suji: will open an issue

<Kathy> wilco: with review of true positive definition, and added issue, rule is done

scribe+

Wilco: de46e4 - open issue for Tom about extinct human languages

Tom: I'm good for it to remain

Wilco: Form field is ok - so closing this
... 4 or 5 left to go

Sage: I will try to get it done when I get access

Shunguo: Me too

Add note to glossary

<Wilco> https://github.com/w3c/wcag-act/pull/580/files

Wilco: a few unheard comments...

<Wilco> https://github.com/w3c/wcag-act/pull/580/files

<suji> +1

<Sage> +1

+1

Tom: Can you add an example of this please?

Wilco: We can do?

<thbrunet> +1

Tom: It will help to keep it consistent

Wilco: Where do I put the example? And what of - so not just a date?

Tom: Maybe a link to one?

Wilco: I am not sure it really adds anything

RESOLUTION: PR 580 approved

Tom: Ok

Cancelling December 26, January 2nd

Wilco: Next week we have a CG meeting and the 19th - we have a few missing - including Kathy and Helen but I will be there getting my work done!

Helen: I did an announcement in W3C - please share it!

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: kathy, suji, Helen, Wilco, thbrunet
Present: kathy, suji, Helen, Wilco, thbrunet
No ScribeNick specified.  Guessing ScribeNick: Helen
Inferring Scribes: Helen

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.)