Meeting minutes
https://
accessibility and wishes to see each of them proceed unimpeded.
Publication plans, announcements https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts
judy: Assuming we all know what to do?
judy: Asking upcoming ...
judy: Asks ARIA ...
james: Core-AAM soon
judy: a lightweight announcement?
james: reuse what we used before
janina: We want to publish FPWD for Maturity Model and CR for Adapt's Content Module 1.0 before TPAC.
… We just added Conformance and Exit Criteria sections to Adapt's spec.
… We're doing our best to avoid a last-day announcement. Roy is on it and I believe Shawn's aware of the announcement. We worked on it last week and are passing it on to Shawn.
… Plan is for Maturity Model to publish on the 29th/30th.
judy: Aim for a few days before the cutoff.
janina: ACK
MichaelC: This is pending the approval of the transition request, which we hope the changes will satisfy (both for Adapt and Maturity Model).
judy: Will follow up outside of this meeting.
New work? Cross-WAI review requests?
janina: After CAUR, we are going to be working on the accessibility of accessibility evaluation tools.
… It wouldn't be appropriate in the CAUR doc, as it's too big a scope, but it's long-since been needed.
… The problems depend on the toolset being used. We want the accessibility industry to provide accessible tools.
Matthew_Atkinson: Recalls reading a paper on the topic, a usability study of AT
Matthew_Atkinson: Recognizes this isn't AT, but it was a good paper relating to UI and may be relevant
judySounds narrower than an AT scope, but agree it could be very relevant
judyRecalls related attempt to sue ...
judyAsks Katie, does RQTF advise IG when new work like this is taken up
janina: No, but we should
judyAssuming our AX testing tools created in AGWG are fully accessible
judy: Asks they be consideredzakim, next item
Accessible tools for our groups
judy: Noting, as we have before, many aren't as accessible as we need them to be
judy: Comes up when moving from one TF or WG where accomodations have been handled, but moving into another group raises the issues all over again
judyAsks whether there's a commonality of what we can say
janina: E.g. I can't use Google Docs, but accept its use in groups, and assume that really important things will come up in the discussions and on list.
janina: We need to try to make the process as accessible as possible, but not get caught up on the process.
katie: Believe we need something universally interoperable
katie: for text text
judy: A wall of text could be the problem; doesn't work well for everyone
Ryladog: There are ways to manage and we should explore among possible tools
judy: Asks other experiences
janina: We need to avoid people diving in to these issues on calls. We also have instances where people will e.g. make on the fly edits to a Google Doc that aren't understandable to the editors of the doc.
Ryladog: We shouldn't be waiting for people to speak up
Ryladog: Let people know that they can't rely on complaining
janina: In some cases, because it's easy to dive into Google Docs and make changes, some people have done this and thrown the editors of the doc into confusion, and taken us out of scope of the document being worked on.
… i.e. they have shoehorned their view into the doc.
Ryladog: That's not a good approach.
janina: ACK that some of these concerns are legitimate, but the process needs to be followed.
judy: Suggests we may need to continue again in future, and maybe offline as well
judy: There are two sides; need to ensure we're not maligning contientious contributors. Proposing to close this for now, do some background work. Think about documentation.
ac ja
Publication plans, announcements https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts
judy: reminding us all to be extra careful because we're so eager to get back in person; be mindful
judy: notes remaining items--proposes we can talk recruiting next time
judy: LE is in process, with BOD expected to be seated by 1 October