W3C

– DRAFT –
Accessible Platform Architectures Working Group Teleconference

01 December 2021

Attendees

Present
anevins, becky, Fazio, Fredrik, Irfan, janina_, JF, Jonny_James, Lionel_Wolberger, MichaelC, mike_beganyi
Regrets
Gottfried_Zimmerman
Chair
becky
Scribe
Fredrik

Meeting minutes

<janina_> https://www.w3.org/2021/12/01-rqtf-minutes.html#r01

Agenda Review & Announcements;

janina: Friendly reminder: weƤre meeting today, 8th, and 15th and then resume on the 5th of January.

Task Force Updates;

janina: RQTF has an action.

janina: We reached consesnsus on starting an update to our 2019 APA note on the inaccessibility of CAPTCHA whcih itself is an update to a note from 2005.

janina: There is a new category available in W3C publications as of Nov 2 called a W3C statemeent. We can actually get all of W3C's endorrsement of what we say ina note assuming we can get agreement on what we have said.

janina: We ran a CFC on it. Meanwhile a few weeks have gone by and we were made aware of some proposals from an Australian company called CloudFlare (the world's fastest DNS resolve, if anyone cares). They have a specific proposal for getting rid of CAPTCHA.

<janina_> https://raw.githack.com/w3c/captcha-accessibility/main/#cryptographic-attestation-of-personhood

janina: We have updated our editor's draft for our repo where there is a direct pointer to teh section that's new.

janina: It may need more elaboration.

janina: We will get decnetralized identifiers, audthentication group and so on involved as well.

janina: We should go FPWD with the best we konw at the moment, i.e., with what we've added as well now.

janina: We have a short analysis from CloudFlare on the economic impact of CAPTCHA on the amount of time wasted on solving them.

janina: RQTF's poposal is to publish our updated working draft as our FPWD.

janina: The second question is if we should run another CFC for this.

janina: It's going to take another week for us to get the messaging arranged, so we have time for a CFC as well.

janina: Do you think we should do the CFC?

Lionel_Wolberger: I'm very excited for the work but I think we should do a second CFC to get people like me to pipe in.

Lionel_Wolberger: I don't want to gum up the gears on this, since I'm also excited about the whole thing.

Lionel_Wolberger: Would we be saying, through aCFC, that we want to promote it to a W3C stateement because we see it as important to the whole W3C?

janina: Yes. Publish as many UWDs as possible, advance it to an APA note in 2022 (hopefully) and once we have it as an APA note, we can ask W3C to accept it as a W3C statement, whereupon it depends on a vote if it becomes a statment, whatever taht would then entail.

Lionel_Wolberger: I'd like appoofing round.

janina: Editorail updates are always accepted as longas a CFC is running. Please give pull requests for typos and so on.

Lionel_Wolberger: Git link please?

becky: Let's make edits, then make a CFC and then make it official as an FPWD. right?

<MichaelC> https://github.com/w3c/captcha-accessibility/

Irfan: Prounication: We had an interesting meeting with ARIA-WG.

Irfan: Nobody was opposiing things during TPAC. Int terms of implementation we have eight properties and ap proposal to identify the most important ones.

Irfan: Today's discussion was around that topic. The next action item is to discuss what we should trim, but that will be based on the use cases in a more detailed discussion.

Irfan: Today's discussion was very important and positive.

janina: We asked them if they could think of a way we can experiment with screen readers.

<Irfan> https://www.w3.org/2021/12/01-pronunciation-minutes.html

Fazio: Nothing from COGA at the moment.

becky: Internationalization has issues still. Everyone is working fro a recipe for both English and Hebrew. We have the code but not the rendering.

becky: We can't really show anything visually to Internationalization.

Lionel_Wolberger: I also have a vague hope that we can go back to I18n without rendering. It's obvious it's word by word, direction is not an issue.

FAST Progress

janina: Can we point i18n to our big document?

Lionel_Wolberger: I will do that.

Joshue108: Brief update. Michael and I met with Make adn Todd during the week. We are looking through tthe spreadsheet we're working on, the user needs mapping.

Joshue108: We're kind of saying the same things again and again. One of the interesting things that came out of the call on Tuesday is taht we are going to try a now slice...

Joshue108: We hope, before Christmas, to have something that's ready to show you then or at least fo rthe new year, that we can demonstrate to APA and otehrs about our thinking and what we want to do.

Joshue108: We have a very focused methodology for the coming weeks. We have a narrow increment we hoope to be update you on before Xmas.

New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22

MichaelC: there is one, Second Screen WG.

<MichaelC> https://github.com/w3c/strategy/issues/291

MichaelC: We have worked with them. They have added to define piS TO ALLOW SCRIPTS TO QUERY DEICES ABOUT CONNECTED SCREENS.

janina: tHE REASON THIS IS BACK IS BECAUSE i HAVEN'T DONE MY ACTION.

janina: i SHOULD WRITE A NOTE ASKING THEM IF WE ARE USING "SECOND SCREEN" GNERICALLY AND THAT OUR apiS WILL HANDLE ALL THESE THINGS.

janina: We had disagreement some time ago, but the membership of the group may have changted substantially. We should just reaffirm a previous agreement.

Accessibility Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review

MichaelC: Nothing!

MichaelC: A lot of stuff that has been published, but nothing new to the radar.

new on TR http://www.w3.org/TR/tr-status-drafts.html

Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned

On the half hour!

<MichaelC> https://github.com/w3c/a11y-request/issues/18

MichaelC: A review request, a new one.

MichaelC: CSS custom properties for cascading variables.

MichaelC: They want a generic review request.

MichaelC: We decided six years ago that we don't need to review this spec.

becky: Do we have anyone that can review it?

janina: Do we have a significant reason to?

MichaelC: They aren't defining categories or variables or such.

<MichaelC> https://www.w3.org/WAI/APA/wiki/Web_of_Things_(WoT)_Profile

MichaelC: Web of Thigsn Profile. Josh sent review comments but we haven't discussed them yet.

Joshue108: We talked about doing some kind of presentation at some stage.

MichaelC: Are the comments discussable?

Joshue108: I want to look at them first.

<MichaelC> https://lists.w3.org/Archives/Public/public-apa/2021Sep/0029.html

becky: It was from September. Forgetting is very understandable.

MichaelC: Should we agenda this for next week? we've been circling this one for a while.

becky: I'll make a note to discuss them next week.

<MichaelC> https://www.w3.org/WAI/APA/wiki/WebXR_Layers_API_Level_1

MichaelC: WebXR Layers API 1.0. Josh has an action to comment.

Joshue108: Wehy don't we try and do that next week as well?

MichaelC: Please send the comment before the meeting.

Joshue108: I have some questiosn.

becky: And some review notes.

<becky> https://lists.w3.org/Archives/Public/public-apa/2021May/0040.html

<MichaelC> https://www.w3.org/WAI/APA/wiki/Language_Tags_and_Locale_Identifiers_for_the_World_Wide_Web

MichaelC: Lnaguage Tags on Locale Identifiers. Janina was going to add an issue.

janina: Tehre was a question if that covers sign languages. I'm adding it to my list.

Fazio: Sign language is super cultural.

janina: There is an ISO SPEC THAT PROVIDES SPECIFIC DESIGNATORS FOR SPECIFIC slS AROUND THE WORLD AND WE WANT TO MAKE SURE THAT THOSE ARE COMPREHENDED IN REFERENCE DOCUMENTS.

janina: tHE QUESTION IS HOW WE GO ABOUT GETTING IT INCLUDED, THESE DESIGNATORS.

<MichaelC> https://www.w3.org/WAI/APA/wiki/Input_Events

MichaelC: Input events. We've been danglign on this for years and years. In 2017 we said we were going to work with them. My proposal for now is we shoudl figure it out.

MichaelC: It was still a WG 2 1/2 years ago. We sent feedback in '17. We wanted them to provide a notification to ATs.

becky: They want a notification that a text insertion was complete so taht you get some kind of positive enforcement.

janina: So we do have some issues. It's about a better supported editing environment.

janina: We had a conversation in Lyon about it. It needed to get done, but what I was getting confused in was an older conversation about the meaning of "click".

ACTION: frederik to review Input Events

<trackbot> Error finding 'frederik'. You can review and register nicknames at <https://www.w3.org/WAI/APA/track/users>.

ACTION: fischer to review Input Events

<trackbot> Created ACTION-2311 - Review input events [on Fredrik Fischer - due 2021-12-08].

<MichaelC> action-2311: https://www.w3.org/WAI/APA/wiki/Input_Events

<trackbot> Notes added to action-2311 Review input events.

MichaelC: Taht's it for danglign specs.

Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open

becky: Please, look at your actions whether they are in the tracker or not.

Other Business

janina: A request to Michael or Josh: Anyone able to give me the locked-in URI for the CAPTCHA-Accessibility for the CFC?

janina: *CAPTCHA-Accessibility

<MichaelC> https://raw.githack.com/w3c/captcha-accessibility/05bdd8c0d8b8a89860aca3a149c53ea4d7998a11/index.html

be done

Chag sameach everyone!

Summary of action items

  1. frederik to review Input Events
  2. fischer to review Input Events
Minutes manually created (not a transcript), formatted by scribe.perl version 159 (Fri Nov 5 17:37:14 2021 UTC).

Diagnostics

Succeeded: s|https://github.com/w3c/captcha|https://github.com/w3c/captcha-accessibility/|

Maybe present: janina, Joshue108