scribe+

ACT stand-up

Jean-Yves: stand up
... preparing slides for WCAG 3 to provide foundation
... made a survey to indicate whether you prefer to work on WCAG 3 or ACT Rules
... survey is open to CG and TF

Kathy: helping to plan the ACT work changes

giacomo: answered the survey and checked some issues

dan_tripp: label and name PR

Shunguo: filled in survey

godwin: catching up

sashanichols: need to review my PRs

dan_tripp: working on this PR for a while. It went to AGWG and have been dealing with the feedback

<Jean-Yves> https://github.com/act-rules/act-rules.github.io/pull/2075

dan_tripp: have addressed concerns
... two comments from Mike Gower

<Dan_Tripp> https://github.com/act-rules/act-rules.github.io/pull/2075#discussion_r2064865390

<Dan_Tripp> https://github.com/act-rules/act-rules.github.io/pull/2075#discussion_r2042562242

dan_tripp: PR is not in draft. what's the next step?

Jean-Yves: CG submits rule for approval to become official

dan_tripp: Mike Gower thinks PR makes some problems worse
... don't understand

Jean-Yves: if we follow the new ACT process, you can be a lead on this project
... need internal review and address his comments

<Dan_Tripp> https://github.com/w3c/wcag/issues/4312#issuecomment-3807073030

Jean-Yves: will request more reviews

<Dan_Tripp> says "@bruce-usab @alastc is this now defunct?"

Jean-Yves: Patrick asked is this now defunct
... you can reply it's not defunct
... and still working on it
... you made changes and they can look at it

<Jean-Yves> scribe+

<Jean-Yves> Kathy: old process is for CG to agree, then TF, then submit to AG.

<Jean-Yves> Kathy: this can be good for figuring the new process for when rule is ready.

<Jean-Yves> Kathy: people who stay in CG and work on rules should establish process.

Jean-Yves: CG will need internal review and address MGower's comments

giacomo-petri: in past rule, empty headings, the normative and understanding lacked nuances.
... what if we set a more strict applicability using only words; no abbreviations or punctuation
... remove from applicability that has no consensus

Jean-Yves: would that remove too much?
... removing too much might make rule useless

dan_tripp: the concerns have been on the weird cases

Jean-Yves: would make sense to help move forward

dan_tripp: have customer experience, not often but maybe 5%
... text in an image that is part of a link, poor OCR will cause false positives
... update applicability for this
... will limit applicability per giacomo-petri's suggestion
... no brackets, hyphenated words, etc

Shunguo: many accessible name calculations
... suggest move forward, and in future open new rule rather all in one rule

giacomo-petri: in Japanese, same sentence can be written in different ways but the pronunciation of label is the same
... different symbols but can spoken the same. May cause problems for AT

dan_tripp: assumptions has languages and parentheses. can assumption be language is English

Jean-Yves: it is possible. We have been very English-centric

godwin: not a fan of it
... how big is this issue?

Jean-Yves: maybe put it as an assumption

<giacomo-petri> I was proposing the same as Jean-Yves

dan_tripp: for spellings, move to applicability. for language?

Jean-Yves: leave language for another rule

dan_tripp: it has been 2 years
... will open an issue for language

godwin: will take a closer look at PR

Review work (if time permits)

jean-yves: closing remarks

giacomo-petri: look at requirement again. normative wording

kathy: agree with approach to move rule forward

dan_tripp: will review with giacomo

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: Jean-Yves, Daniel, giacomo-petri, Sage, Kathy, Dan_Tripp, sashanichols
Present: Jean-Yves, Daniel, giacomo-petri, Sage, Kathy, Dan_Tripp, sashanichols
No ScribeNick specified.  Guessing ScribeNick: Kathy
Inferring Scribes: Kathy

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