Meeting minutes
matatk: we have a new member, Rita Shewbridge
Agenda Review & Announcements
matatk: I asked last week about who will attend CSUN because there's an opportunity to meet and conduct some WG or TF work
<Fazio> I'll be at CSUN
matatk: if anyone else knows they're attending, please let me know
Fazio: can we use the room to do presentations about w3c work?
matatk: I think it will depend on what agreement is reached with the conference. My expectation is that it's just for private work but I can ask
CSS Update (Paul) - https://github.com/w3c/css-a11y/issues
<gb> Issue 5477 [css-lists] CSS counter scope/inheritance is incompatible with HTML ordinals (by MatsPalmgren) [css-lists-3] [CSS2] [Needs Testcase (WPT)]
PaulG: About counters and how they work with HTML list structures. Currently there's not agreement, and they're trying to work through it.
Actions Checkin (Specs) - https://www.w3.org/WAI/APA/track/actions/open
Thank you to APA, from the Devices and Sensors WG: https://
matatk: (see the email) we came up with some text for Devices and Sensors compute pressure spec
<Lionel_Wolberger> +1 to APA team efforts!
matatk: and I'm going to approve it since it's exactly what we suggested
matatk: as discussed in the email, we talked about how they want to give developers resources to help reach these recommendations
… I'm asking if anyone wants to have another look or if we want to contribute to the guides
… a good example is
https://
https://
matatk: we're talking about software: color alone and toast messages
Fazio: icloud has a meter approach that doesn't rely on color
https://
I'll look at the examples to make sure we're talking about the right pattern to use here
Fazio: dynamic elements that appear to be interactive but aren't that's a problem
One's assigned GitHub tasks: issues/
Dangling Spec Review Cleanup - https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned
Task Force & Deliverables Updates
Adapt
matatk: if you're involved in TF work and you want to briefly share that
https://
matatk: in discussions something is discussed and later promoted into issues
… the challenge is you can comment on lines of code but that's not accessible to screenreader users
… discussions should be accessiblel
… so we're proceeding with discussions of general things and it's more integrated and visible to the public
One of the upcoming specs: https://
matatk: this is an example of a discussion being worked into a spec
Maturity
Fazio: there should be updates in the document we're going to publish before the end of the year
<Roy_> https://
Fazio: is there a good tutorial for github?
matatk: there should be one, especially for non-developers, that we can recommend
<Roy_> https://
Other Business
matatk: we are meeting next week.
… TF's may or may not