<scribe> scribe: Lionel

<scribe> agenda: this

Rules ready for W3C publication https://github.com/act-rules/act-rules.github.io/issues/1120

<Wilco_> https://github.com/act-rules/act-rules.github.io/pull/1554

Blocked by 1554

Jean-Yves: Blocked by 1554

Wilco_: We are not getting reviews at the velocity that we were before.
... consider putting a recurring calendar item to check this
... use Slack as well when looking for reviewers

<Wilco_> https://act-rules.github.io/pages/contribute/join/#join-us-on-slack

Aron: A bit stuck with, "Table with non-empty cell assigned"
... The rule is that table headers have assigned cells
... aria table and html table
... the challenge is: columna and data cell correspond to the same data element

Jean-Yves: There are complexities here.

Aron: I don't feel there is an issue mixing html and aria

Jean-Yves: Maybe. That can throw off the content module in HTML

Wilco_: propose making a group to look at this.

Jean-Yves: A partial fix would be, look only at HTML
... postpone looking at aria table, and mixed html/aria table
... Aron agrees.

Wilco_: Update from TF call regarding the process document
... The pull request author will no longer be responsible for merging the pull request, this goes to the TF organizers.

Jean-Yves: This works well with GitHub

Wilco_: There will be some joint meetings
... open to stekholders interested in keeping the rules up to date
... this opens the door to Community Group members who have 2-4 hours available for this task

Aron: Count me in

Wilco_: Any other takers?
... This joint meeting starts next week

Lionel_Wolberger: Lets reach out to new members as well.

Aron: Rule mapping to message status criteria?\
... I was planning to write a rule, not sure if someone is writing it?

Wilco_: Propose to change Zoom accounts. There was confusion two weeks ago.
... I propose to move this to the TF zoom, I will update the email
... Be sure to update the calendars

Lionel_Wolberger: Suggest during time zone changes, put the GMT delta

Does autocomplete attribute need appropriate type? https://github.com/act-rules/act-rules.github.io/issues/1562

Aron: type should correspond with the autocomplete attribute value
... the primary purpose is not auto-fillin of input fields
... but something for AT to hook into and potentially personalize the look and feel of the form
... did a web page with two input fields
... one birthday-month, one username
... two test pages, one with an incorrect type attribute and one with correct
... the browsers do not follow the type attribute
... Chrome / Safari do not provide suggestions for birthday month or username
... Firefox as well
... should we follow the spec?

Lionel_Wolberger: We see similar issues in Personalisation, that autocomplete is not type aware and types are not being enforced

Wilco_: If browsers dont care, makes sense that we shouldn't either.
... Im OK with taking out the specification that type matches up
... Add a note that type is not a barrier to accessibility

John_H: Are there certain things that will not get filled in?

Wilco_: Example, Chrome will not autcomplete birthday

John_H: Other types?

Should "instrument" / "mechanism" be accessible? keyboard actionable? https://github.com/act-rules/act-rules.github.io/issues/1524

Jean-Yves: Reviewed the issue.
... It is critical that "The mechanism needs to meet all success criteria for the conformance level claimed."
... is a note.

Wilco_: Example, if there is a keyboard failure, the rule violated is not "bypass block". It is a failure of keyboard nav.

Jean-Yves: Putting that instrument must be accessible will end up cascading (recursing, linking) failures
... +1. Need a note

Wilco_: Proposed, put a note in the definition of instrument

Jean-Yves: I'll do 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: Lionel_Wolberger, CarlosD, Jean-Yves, Daniel
Present: Lionel_Wolberger, CarlosD, Jean-Yves, Daniel
No ScribeNick specified.  Guessing ScribeNick: Lionel_Wolberger
Found Scribe: Lionel

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