Accessible Platform Architectures Working Group Teleconference

Meeting minutes

<anevins> Are there any notes on how scribing works for first timers?

next item

janina: A bit of reshuffling in the agenda today - not much new, but just a new order in order for us to get to the things we need to get to. Teh Michael portion of the agenda is a bit scattered.

janina: We meet again next week, but not the week following. Expectations that we will meet on the 17th and not on the 24th. Three weeks in Dec> 1st, 8th and 15th.

CfC on CAPTCHA https://lists.w3.org/Archives/Public/public-apa-admin/2021Nov/0000.html

janina: Reminder, and a pointer, that we have a CFC about the CAPTCHA note. The mroe time-honoujred way int e W3C to resurrect what has been published as a note and reissue it as a FPWD for a Statement.

janina: There are proposals floating aroudn helping to kill CAPTCHA, which has been one of our goals in the past.

janina: There is also a new opportunity for a new kind of W3C publication in our Process 2021. We can take a note, which has always only been something that a WG said, and send it to the AC for a vote.

janina: If they agree, then, that is something the W3C says, not just what a WG says.

janina: The feeling in RQTF has been tha tyes, we hsould avail ourselves of this opportunity to get this elevated to a W3C Statement.

janina: Cloudflare is proposing an approach which we should document which may change our recommendation.

janina: The smoothest path is outlined in the CFC> publish the old note as an FPWD, assign it to RQTF for further development, give them the rihgt to publish WDs a sthey see fit, then coming back to APA to finalize the note.

janina: And then elevate it to the W3C AC for consideration as a W3C Statement.

janina: Thanks for all the votes on the CFC by the way.

janina: CFC stays open until Midnight Boston Time the 17th NOv.

janina: May get the FPWD already this year.

MichaelC: Probably.

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

janina: We had a long conversation with CSS who are deseprately waiting for orur signoff on scrollbars.

janina: We had e-mail from Florian today showing his adoption of what we talked about. He had already described some a11y considerations in the text of his document. We asked him to add them as an appendix.

janina: He has given us a draft of what he's written. If we oculd annotate this with the work he has done, we can sign off on it.

janina: Hearing no objections to signing off on scrollbars?

JF: No objection, but uncomfortable. Not lseping well but living iwth it.

janina: If we have a well-defined mechanism that users shoudl be able to override whatever the author has done, how can we argue that they shouldn't be able to?

JF: I'm doing some work in EPUB. These readers might not support user style sheets. I don't want to go back to CSS and say that this is harmful, but their justification fo rnot having the reverse of narrow has a rather flimsy excuse.

janina: Paul had a use case where he would have used wide not even thinking about a11y. These should be promoted on the CSS side.

JF: I would say that looking for use cases where wide would be appropriate or where thin/narrow is abused would also be useful.

janina: We mad eour case and it's documented.

JF: I ahve my concerns.

Fazio_: To a certain degree this relates to Content/Usable. The scrollbar helps with knowing the length of a document. I don't know how this relates to this, but it should be mentioned.

janina: There will be nother rev of this spec at some point.

janina: Do we have any ability to annotate this iwht last weeks minutes and Flrian's e-mail?

janina: Florian talks about what people should be mindful about when using that spec. That was our requestj.

janina: I'll respond to him onj thread informing him about the annotatiosn.

<JF> URLs: https://drafts.csswg.org/css-scrollbars/#scrollbar-width and https://drafts.csswg.org/css-scrollbars/#accessibility-considerations

janina: We have three other specs> EPUB, EPUB Reading Systems, EPUB Accessibility.

janina: Those all have notmative statements.

MichaelC: We did our own review on these.

janina: Avneesh, Ivan and Wendy should be reminded to use the dashboard.

janina: EPUB has had good accessibility work over the years and it's good to see that that continues.

MichaelC: CSS scrollbars also had a generic self review which I kept open. Do we want ot just close that?

MichaelC: It's not an actual comment on a spec or anything.

janina: We can clear that, too, I think.

TPAC Followup https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2021

janina: This is an open discussino topic for anybody.

Fredrik: The Cvent portal was not a very pleaseant experience. Should be considered for retirement... ;)

<Fazio_> valid points Janina

janina: Zoom could do things to make it easier to join a teleconference. IF COGA is meeting with RQTF it is fine for us to create a new meeting ID with its own password. Why can't Zoom just conference in the usual meeting ID for COGA and RQTF? They could do that at the server end. That would be much easier on the participants.

janina: I plan to write that up inj my followup.

<Fazio_> COGA will support

<Fazio_> accessible authentication

janina: Just because we can have heightened security doesn't mean we should. are we really seeing abuse that we are preventing with this 2FA?

<Fazio_> there is a sc on that

janina: Why so complex? When you ame a complex alphanumeric password, it just lets you in automatically when you dial in by phone.

Fazio_: There are WCA 2.2 success criteria about not having to redo things and also accessibile login schemas. These should also be noted.

JF: I'm looking forward to it being in person next year.

janina: Next year it wil be in Vancouver.

<Fazio_> LOL

janina: RQTF had much success with the specifications.

janina: Pronunciation also had success but some feedback from ARIA saying that some things don't need to be done via markup.

janina: Personalizatio had some very profitable sessiosn. SAUR had a very useful session with people active with TimeText, MediaWork and so on. The minutes read very well.

janina: There is a W3C workshop next week where we can share some of that work. It's related somewhat at the level of GIGO. How can you expect content to conform to sAUR if you don't have sync points?

janina: There is the need to support texted descriptiosn of video. It's in the HTML spec. If we're talking about authoring media, then let's support low budget descriptions of video. write it up in a file, put the time offset where it belongs and let the user agent do the rest.

janina: Our meetings with EPUB were great. Everytime in Silver when I give the examples of interlinear publications being something we don't know how to make accessible, I get roling eyes. EPUB concurs with me. I'm now writing things up on how this can be achieved.

janina: OUr page continues to be active with links to minutes as well as video recordings. This makes it a resource for us, too.

janina: Please add all relevant links as you have time and possibility.

IrfanA: We have a timing issue with teh next Pronuciation TF meeting and ARIA WG.

janina: I will follow up.

janina: Any updates for higher ground?

IrfanA: I and Paul are presenting. We are working on a presentation at this moment. We have pretty good feedback from TPAC.

IrfanA: It's easier for us to go forward with the one we always felt ocmofrtable with.

IrfanA: It willb egood to provide some updates for the audience from TPAC.

janina: Please talk about the single attribute approach as to where this is going.

IrfanA: That's the idea.

janina: I have no idea what James, James, Cynthia and Dominic came up with.

IrfanA: I think they read the gap analysis. At least I hope so.

janina: "You've got an approach? Write it up!"

IrfanA: After our meeting, interestingly, James Craig posted something about oging forward about the impleemtnation of the single attrribute approach.

IrfanA: Looks like he knows this stuff. We'll know more about ti when we talkto them as a group.

janina: I'm always interested in teh outcomesl. What do we do?

janina: Soem good progeress in RQTF, some good progress in Pronunciation.

janina: Thanks for all the work in the year just past and the year ahead.

Task Force Updates

janina: Other than what we talked about before, I would like to get CAPTCHA off early in 2022. It would be nice to be the first a11y related statement, and really nice to be teh first W3C statement in 2022.

MichaelC: We are having a hard time getting ourselves together in a room.

MichaelC: We want to fill otu a proposed strucutre.

janina: Those minutes were interesting.

janina: Those minutes should get on teh wiki.

<MichaelC> https://www.w3.org/2021/10/21-fast-minutes

janina: Silver is feeling like they're comign to a hand-it-back-to-APA point.