Meeting minutes
Agenda Review & Announcements
janina: A little of a whirligig: Horizontal Review will get more space today.
janina: A reminder to us all that we are moving off of Trackbot and even RRSAgent. We're trying to use zakim start meeting and end meeting in our calls. It does all what we need for us in our calls.
janina: For isntance, when we use zakim end meeting, it dismisses all the present]es from before. The participant lists should be accurate that way.
janina: Plus, of course, it generates the minutes as usual.
janina: THese are active tools, actively maintained and developed.
APA Charter Voting Review https://www.w3.org/2002/09/wbs/33280/apa-wg-recharter/
janina: The voting for the charter remains open.
janina: If your organization has yet to vote, plase get your AC reps moving.
<Lionel_Wolberger> ./me I already voted
TPAC 2023 Planning
janina: We have confirmed with the organizing committee that wwe will be meeting Monday, Tuesday and Thrusday. That's all we know.
janina: It's up to us to schedule the cross-group meetings, ontrary to our first impressiosn. They will assign rooms once we are closer to the event itself based on expected attendance.
janina: A meeting as large as CSS we will go to them, some of the other meetings we have asked for could be well acommodated in our rooms.
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
Roy: Nothing new this week.
Explicit Review Requests https://github.com/w3c/a11y-request/issues
Roy: Nothing new here either.
new on TR http://www.w3.org/TR/tr-status-drafts.html
RDF star WG
<Roy> - spec: RDF 1.2 Semantics
<Roy> - spec: SPARQL 1.2 Entailment Regimes
<Roy> others: https://
Roy: There are two new publications!
Roy: Both from the RDF working group.
Roy: Last time, we asked Lisa to review the large batch of documents, 18 in total counting this week's clutch.
PaulG: Nothing new rom CSS. All is very technical recently.
CSS Update (Paul) https://github.com/w3c/css-a11y/issues
PaulG: Nothing new. Al very technical...
Getting a Grip on the A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
<matatk> HOWTO guide for horizontal review: https://
<matatk> Plain GitHub Issues in the HR issue review request repo: https://
matatk: Our main responsibility is to review everything coming out of the W3C for a11y which is why we do horizontal review.
matatk: Others include i18n, security, privacy etc.
matatk: As well as eht spec reviews, we occasionally get asked to comment on issues raised by other groups before they get into specifications.
matatk: There is a dashboard we use with Github issue labels and so on (linked to in the header of this agendum).
matatk: If someone has a question for us they put a specific label on their issue and we get notified.
matatk: We have gotten a lot of isues raised in this way to comment. We do have a backlog of over a hundred issues now.
matatk: Many of them will have been overcome by events, things may have happened, people may have said things on them and so forth.
matatk: I also linked to a how-to document which explains how the labels work and such things.
matatk: What we are proposing to do is: we'd really like any of you how would like to have a look at any of this, to do so and do a little gtriage. If you do and we talk about it on a call, it would be helpful if you had formed an opinion on what might be needed. Just if you think there is an issue here or not.
matatk: THe tracking issues are just Github issues. We can assign them to ourselves and anybody who wants to take them. That won't disturb any of the original issues.
matatk: Please give specific attention to the "closed?"/labelled issues.
<PaulG> https://
<Roy> https://
<Roy> Minutes record
matatk: Many assignments made: thanks everyone for taking these issues!
janina: And thanks Roy for letting us know that we are a little more up to speed than we thought.
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
Task Force & Deliverables Updates
subtopic? Maturity Model
Maturity Model
Fazio: MM is getting ready to publish again.
Fazio: By the end of June we will probably have an update ready.
janina: We will be done with the drafint of the actual guidance in less than a year from now, probably next spring. Which leavesd work to do for building a consistent interface to populate a database.
FAST Organization
<Roy> https://
<Roy> https://
<Roy> public-fast@w3.org
Fredrik: I haven't be able to do any work. However, we have to interested members - Todd and whomever Raja is proposing
<Roy> https://
<Roy> w3c/
janina: RQTF is willing to be the FAST partner. The group that has developed most of the a11y user requirements. If you are interested Fredrik
Fredrik: Yeah sure!
Roy: First Link is the homepage on the WAI-Website. The second one is for the official FAST website
<Roy> My email address: ran@w3.org
Roy: If you want to join then just talk to janina, Fredrik or me
janina: It will probably hard to get a group starting in summer, but we are giving our best of course.
Fredrik: Is anyone up to taking up an action and look at a website and read through the text to see if the information is understandable
sorry, not Fredrik but matatk
Other Business
janina: No other business.
be done
janina: Thanks everyone! GGreat and productive call!
ACTION: Fazio: Review FAST TF site and document for clarity
<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.
<ghurlbot> Cannot create action. Validation failed. Maybe Fazio is not a valid user for w3c/apa?
ACTION: David: Review FAST TF site and document for clarity
<ghurlbot> Cannot create action. Validation failed. Maybe David is not a valid user for w3c/apa?
<Roy> ghurlbot, Fazio = Helixopp
ACTION: Fazio: Review FAST TF site and document for clarity
<ghurlbot> Created action #333