Accessible Platform Architectures Working Group Teleconference

22 June 2022


becky, Fredrik, janina, Lionel_Wolberger, Matthew_Atkinson, niklasegger, PaulG, Roy
Gottfried_Zimmerman, Mike_Beganyi, Nadine Sienel, Todd_Libby

Meeting minutes

Agenda Review & Announcements

janina: We have very much our standard agenda today.

PaulG: Has action items to present progress on. Also Focus Group.

PaulG: No concerns with Janina's draft response.

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

Roy: No new charters this week!

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

CSS Color 5

<MichaelC> - spec: https://www.w3.org/TR/css-color-5/

<MichaelC> - FO on CSS Color 4: https://github.com/w3c/csswg-drafts/issues/7310#issuecomment-1146693305

MichaelC: One on the review tracker: CSS Colour 5, a review of CSS Colour 4 as per wide review request is underway.

MichaelC: Objection was filed on CSS Colour 4 about the colour contrast algorithm. They are basically removing it from Level 4 and planning to address it in Level 6.

MichaelC: I don't think there is anything the group needs to do on this particula rone.

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

Core-AAM 1.2

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

<MichaelC> - draft: https://w3c.github.io/core-aam/

MichaelC: Not exactly new, but a WR request for Core AAM 1.2. What do we do?

MichaelC: I propose we don't need to review it.

janina: I think we're cool with this.


<MichaelC> action-2326?

<trackbot> action-2326: Paul Grenier to Report on open ui focus group proposal https://github.com/openui/open-ui/blob/main/research/src/pages/focusgroup/focusgroup.explainer.mdx -- due 2022-06-08 -- OPEN

PaulG: I made my comment to the Github issue and it hasn't received a response.

PaulG: The initial review was very positive, however, very quickly, when they tried to do nesting and tried to switch directions, it created a situation where the containing element o fthe other focus group was a no-role, no-name element.

PaulG: I felt like this is something departing from existing ARIA patterns. Teh demo did not work.

<PaulG> https://github.com/w3ctag/design-reviews/issues/732#issuecomment-1159814503

<Matthew_Atkinson> Via the actions page, this is the comment two which I think PaulG's referring: https://github.com/w3ctag/design-reviews/issues/732#issuecomment-1159814503

<PaulG> https://www.w3.org/WAI/APA/track/actions/2326

janina: Sounds like we should continue to track progress on this. Do we want to track this apart from trackbot and the action tracker?

<MichaelC> https://github.com/w3c/a11y-review/issues/113

MichaelC: We have a tracking issue for this.

janina: I think we want to hear from them, if they want to fix this now or in the future. It sounds like an issue worth pursuing.

MichaelC: I'm putting a link to Paul's comment in our tracking issue. If they clos ethe issue we'll get ap ing. We're on the side here. It's open in our spec tracker.

janina: So we can close Paul's action, because he did it.

PaulG: Thanks!

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

Reporting API

<MichaelC> - draft comment: https://lists.w3.org/Archives/Public/public-apa-admin/2022Jun/0013.html

<MichaelC> - tracking: https://www.w3.org/WAI/APA/wiki/Reporting_API_1

MichaelC: Only one today. Reporting API.

MichaelC: We have the gist of a comment approved, not the wording.

janina: There is a page, I don't have the wiki at hand, but if someone goes to the RQTF wiki, there is a reporting API use cases page that Jason has opened there and started to populate. We have starteed to collect the kinds of cuse cases we want to address in this kind of API.

janina: We do need to fix the comment request.

janina: I can sit down to update the draft messaging by next Wednesday.

Task Force & Deliverables Updates


janina: Teh report is that messaging has been forwarded for the SAUR. We did approve publishing that when Shawn is back.

janina: Matt needs to sign off, as does Roy.

janina: When Shawn signhs off the fireworks start.

janina: That is the status of that for now. the group si done with the SAUR.

janina: The next document in the pipeline, almost ready for CFC and publication, is the long document which is what we've learned form our experience of Covid and remote meetings.

janina: It is a best practicies kind of document.

janina: In a few weeks it will be here for a CFC, I guess.

(We're talkigna bout Remote Meetings here.)

janina: There is anew document that Roy is going to give us on Collaboration Environments Tools (like Google Docs, Word Online and so forth).

janina: We are going to do a Collaboritve AUR.

janina: I think we will have useful guidance and a lot of takeup from teh tool vendors rather quickly if we do our job well.

janina: I know that improving the accessibility is important so ome vendors that have these tools. Us articulating what is missing and what can be improved will be very helpful.

janina: It loloks like the central point is going to be that cognitive load is going to be the issue, not necessarily with COGA issues but for screen reader and low vision users.

janina: Fairly heavy set of issues with SR users. We are going to make sure that even the early drafsts have a lot of notes pointing to other issues.

janina: Teh organizing principle is being able to track and interact with things.

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

TPAC22 https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2022

janina: I hope by next week to have populated the page with the early organziational messaging which we will then turn into requests for joi9nt meetings at TPAC.

janina: We expect Matthew to be there in person, I expect to be there as well, however my travel is not yet approved. Matthew has approval already.

janina: The organizers want constant updates from us. We should do our meeting coordinations directly with others groups, nto with W3C management.

Other Business

be done

We're done! More than 12 minutes, perhaps even more than the entries in these minutes.

Minutes manually created (not a transcript), formatted by scribe.perl version 185 (Thu Dec 2 18:51:55 2021 UTC).


Succeeded: s/Ha sactionitems/Has action items/

Succeeded: s/by neext/by next/

Succeeded: s/jist of/gist of/

Maybe present: MichaelC