Meeting minutes
<janina> w
Agenda Review & Announcements
janina: No particularities. Let's talk charter.
fazio: Let's keep those downloads coming!
<Fazio0> Helix Opportunity's AI-powered digital accessibility auditing tool, Ottitor, Beta 3 release is free and open to the public on all chromium based browsers. You can download at Google Chrome Store here: https://
APA Rechartering
Rechartering
janina: Do we know anything about the deliverables yet?
PaulG: The meeting yesterday was me and a new person, so nothing to show, sadly.
PaulG: We'll need to have another meeting of some sort.
janina: We kinda need to know...
janina: Let's try again Monday and I'll be on the call.
New charters review
janina: Proposed charter coming up!
<janina> Media Working Group Charter
janina: That's the only one for today.
janina: This is an existing WG talking about some thigns they might want to to do in this new charter. I see nothing here that's a surprise to us. We've interacted with the various incarnations of these groups in the mediasphere.
janina: This WG are particularly concerned with tthe support for the Encrypted Media Extension.
janina: Any comments or questions?
janina: Any objections to signing off on this charter?
janina: Hearing none. There were no objections. We are signing off on this one.
Spec review requests
janina: We do have one actually.
janina: ...then again we don''t actually.
zzkim, close this item
Spec review requests
<janina> Audio Session
janina: There are spe reiews after all.
janina: We were rather settling into wanting to ask a question and perhaps suggest a11y considerations here. This was kind of sitting in my area to do that, and I haven't.
janina: Ij'm proposing to draft my response and review here on list.
janina: This was supposed to be done tomorrow. I think this might take a little longer and I will pign them to let them know that I am getting to it.
Neural Nets
<janina> Web Neural Network API
janina: For this we had an initial review from Matthew that went to the list.
janina: More of initial thoughts, really.
<janina> Initial overview and suggestions from Matthew are here: https://
janina: This is a useful e-mail because this is a huge spec and Matthew has pointed ot the parts we will want to look at.
janina: I would suggest that RQTF should do that. They won't be meeting until the 2nd week in May. Some work may happen asynchronously.
janina: We have until end June to make the comments we might want to make.
janina: It is an area of great interest since its implications for AI.
janina: There is a good summary in our issue as to what is new in the spec.
janina: Between all these poieces, I thiknk we have an initial overview to structure our look at it.
janina: Is anyone here interested in looking at this spec?
Demelza: I can look at it!
janina: Thanks!
janina: Any comments, thoughts, anything?
Comment review requests
<janina> [\[menu\] define orientation attribute](w3c/
janina: One item here.
janina: From the OpenUI folks.
janina: They are trying to figure out a behaviour.
janina: It sounds to me like they dove into a convo on a subject without stating what they are solving.
janina: Do we understand what they are getting at?
PaulG: Tablists are by default horizontal and aria orientation certical tells nonvisual users that it is a vertical oreintation. It is up to the developer to use the up and down arrow keys for navigation. This doesn't happen automatically anyway so I'm not sure what they are asking for. Nothing happens automagically here.
PaulG: The fact that the OP is referencing a menu list and not tabs doesn't matter because it doesn't do it for you.
janina: I don't usually think of tabs as a menu.
PaulG: Not sure this is anything.
janinaThere is no intrinsic reason except for screen alyout to default to the direction?
janina: Do we have a response to them?
janina: We don't sound clear why we want to define this.
PaulG: I want to ee if orientation is valid for menubar.
PaulG: You can make a menu ar, applya ria roentation to it, wire up your handlers to it to use the up and down arrow keys. If you're wound up babout MDN, tehn talk to Mozilla.
janina: Thanks.
janina: You can say we considered it.
CSS Update (Paul)
PaulG: There's only one thing I'm trackign rright now.
<PaulG> w3c/
PaulG: There is a lot of debate about how CSS namign should work.
PaulG: What they are trying to get to is honouring the user agent, operating system, font sizes, that are set... How does an author get that value and can theyy use that value for text zoom?
PaulG: They have resolved to call it PreferredTextScale. There may be another token to add to CSS to do it.
PaulG: It would be a unitless number and it would allow for authors to use that as a way to alter the presentation for users to honour the intent to have more or less scale fonts on their presentation.
PaulG: Right now only Apple's system has that capability right now. It's behind a prefix. It's only on the desktop so far.
PaulG: I like this for a11y, I like this for consistency, I like this for platofrm-switchers and so forth.
PaulG: If you're interested in this or have commetns or suggestisn or just want to track it, this may be a good one to follow.
janina: Is the point ot keep the variability within limits? Or am I misunderstadning this?
PaulG: The PreferredTextScale provides a facotr. If you said I want to use the Rem times a facotr, then that would change the way it renders based on the user's preferences and the UA defaults. Currently, if they are ona platform that doesn't support the Apple prefix, they might have to zoom or use browser scaling to increase the font size. Thsiw
would make it a little easier to do.
PaulG: I see very few ways this could be misused other than fingerprinting.
PaulG: I think it is likely not ot be a fingerprinting factor.
<PaulG> https://
PaulG: Have a look at the stats above, if you would.
janina: 40-60% comon use is pretty impressive.
Actions check-in
janina: Anyone?
janina: Matthew and I have had some convos about this. Things are coming and cooking.
Other business
janina: We may or not have a call on teh 7th of May. We will meet on May 1st. We will know for a certainty at the time of this call.
janina: That's 30th of April, not May 1st.
Be done
janina: And we're done! Thanks everyone for this. Happily ceding time.