<CarlosD> scribe+ Wilco_

Call for review https://github.com/act-rules/act-rules.github.io/issues/461

Carlos: No pull requests for review

Assigned issues + help wanted https://github.com/act-rules/act-rules.github.io/issues?page=1&q=is%3Aissue+is%3Aopen

Carlos: Need to do more PR review

Jean-Yves: Work on inline assets in ACT rules. Need more reviews on 1923 & 1914

Gaicomo: 2007 ready for review
... Next week I'll work on the iframes PR, 2038

Carlos: Need a review of 2058 as well

Dan: Working on visible label in name rule, no PR yet, but commented and would like a conversation today

Helen: Start working on focus returns to trigger rule

Wilco: Working on tooling for how we render secondary requirements, and a couple other things related to rendering rules and examples

Kathy: Working on label in name

Update from the ACT Task Force https://github.com/w3c/wcag-act/pull/522/files

Kathy: Had a couple rules in survey. Page lang matches default language, and also the Audio element has transcript.
... Both require updates based on comments.
... We've talked about rules with state, and there's an open discussion on how we can include state in applicability and expectations.

https://github.com/act-rules/act-rules.github.io/discussions/2046

Carlos: Great news on ongoing work

TPAC F2F meeting

Carlos: We have the option of having our annual F2F meeting in Spain in September during TPAC.
... Wilco sent out an e-mail.

<CarlosD> scribe+ CarlosD

<CarlosD> Wilco_: It's almost certain that we will host one or two days there

<CarlosD> ... the meeting is hybrid so that there will be the possibility to attend remotely

https://www.w3.org/2023/09/TPAC/

Carlos: We have a couple issues related to this rule
... 1458 and 1650 deal with matching the label with the name
... 2040 deals with defining what the visible label is exactly

Kathy: Some of the issues have been discussed by TF. I left them open because I still need to update the rule.
... What we discussed is regarding symbolic text, and screen reader pronunciation help.
... and abbreviations. I'd appreciate if you can add comments.
... Dan has been working on the other issues

Dan: I'm pretty sure my ideas don't conflict, but there's a lot open

<dan_tripp> https://github.com/act-rules/act-rules.github.io/issues/1458#issuecomment-1524088094

Dan: My proposal is in this comment
... This isn't new. It's pulling together existing ideas. The algorithm I'm proposing is on whitespace, punctuation, and word order
... For phone numbers it makes the word more lenient.

<Jean-Yves> https://github.com/w3c/wcag/issues/1936#issuecomment-868676987

Carlos: I think Dan's idea works
... The behaviour of these systems isn't clear.
... If there's a link with the text 123, it'll still work if the accessible text is 1 2 3

Wilco: What false positives do we have if we don't allow spaces between numbers

Kathy: I think there was some research from Aron
... Most of the tools used either the accessible name, or the visible text, but there was one tool that only used visible text
... Maybe it would be helpful to have a text with that phone number example.

Carlos: This fails the rule, but if voice control allows you to activate the link by speaking the digits, then it shouldn't fail.

<Helen> +1

<kathy_> +1

+1

<dan_tripp> -1

<giacomo-petri> -1

<Jean-Yves> 0

<CarlosD> 0

<kathy_> https://github.com/act-rules/act-rules.github.io/issues/1615#issuecomment-858800969

<CarlosD> karen: We should redo Aron's tests with current technology to check if some issues haven't been already addressed

<CarlosD> CarlosD: We will ask for some volunteer to do that, and revisit this issue in the next meeting

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: CarlosD, giacomo-petri, Helen, karen, dan_tripp, Wilco_, Jean-Yves, kathy_, Sameera
Present: CarlosD, giacomo-petri, Helen, karen, dan_tripp, Wilco_, Jean-Yves, kathy_, Sameera
No ScribeNick specified.  Guessing ScribeNick: Wilco_
Inferring Scribes: Wilco_

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