Meeting minutes
<janina> Date 01 May 2024
<janina> /join #rqtf
<janina> ~scribe+
<JenStrickland> I can only attend for the first 20m
Agenda Review & Announcements
<janina> https://
janina: One announcement: CfC on adopting and publishing FPWD for Immersive CAptions CG report as a Note.
matatk: One of our team members, Muadh (who was on this call a couple of months back) was wondering if they'd considered internationalization (i18n).
janina: We'll be keeping in touch with the group, and have the standard process, which is to publish a First Public Working Draft (FPWD) to help us promote it, and seek comments.
janina: RQTF has already read it and that's where we'd likely work on it in future.
janina: Raja is engaged in this area.
TPAC 2024 Planning Begins
janina: We need to declare our intentions wrt meetings by the 20th. We expect we will meet across the week. Already one expression of interest in meeting, from MEIG.
janina: We committed to revise the MAUR to 2.0 - need to get funding for that work.
janina: I tried to find funding for it, but haven't as of yet. Concerns/thoughts from all of you are welcome.
janina: Any comments/questions/ideas about upcoming TPAC and collab?
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
gb, off
<gb> matatk, issues and names were already off.
HR A11y Review Comment Tracker https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review
[css-view-transitions] Users need to be able to disable view transitions
<Roy_> - issue: w3c/
<JenStrickland> For the MAUR reference earlier, I found this link: w3c/
<Roy_> w3ctag/
PaulG: This is similar to the page-level animations discussed last month. prefers-reduced-motion should limit or shut it off - if that's not mentioned here that's an important comment.
PaulG: The second link is about Document Render Blocking, which is related, and I'll check will be covered similarly to View Transitions.
<JenStrickland> w3c/
<JenStrickland> PaulG w3c/
<PaulG> I'm looking at w3c/
matatk: So our answer to this is 'Yes!'
JenStrickland: +1
janina: +1
PaulG: +1
Use v2 context for the data-integrity
<Roy_> - issue: w3c/
<JenStrickland> +1
Explicit Review Requests https://github.com/w3c/a11y-request/issues
janina: RQTF doesn't have any concerns about the TAG Privacy Principles
Paul raised an issue on our call last week: https://
PaulG: It was around ensuring the most vulnerable have the same access and privacy protections.
PaulG: There is a section, 1.2, about vulnerability. Doesn't mention disability specifically but it is good. I'll check whether my comments were addressed and follow up if need be.
janina: It is a big document - maybe needs an index?
PaulG: I'll probably come back to it - there is mention of 'additional' protections, but my point is that also the _standard_ ones need to be available to vulnerable people.
janina: What's the timeframe?
matatk: Need to sign off - if we are happy for it to be published - today.
PaulG: It's a great document - but we need to make sure, e.g. that we don't end up with CAPTCHA 3.0 in the race to make things more private/secure.
janina: We have an update pending to our CAPTCHA document from 2019.
janina: Any objection to signing off on this, modulo the foregoing discussion?
Fazio: No objection - doesn't WCAG 2.2 Accessible Authentication help here?
PaulG: Specifically for auth yes, but the principles in this document are much wider.
PaulG: Would like to borrow some of that language.
PaulG: Access comes up in Transparency section; not Consent/Widthdrawl. Need to make sure that APIs developed are carrying appropriate data.
Fazio: John Rochford was the main person on the accessible auth stuff - suggest connecting with him.
<Fazio> John Rochford is the point person for accessible authentication
new on TR http://www.w3.org/TR/tr-status-drafts.html
CSS Update (Paul) https://github.com/w3c/css-a11y/issues
<PaulG> w3c/
prefers-interaction-side
PaulG: This was posted in the accessibility Slack channel. I'd like to hear some feedback from the community.
… The concept is a media query that would allow specific controls to move from one side of the UI to another, for disability and preference reasons. Could be something like dark mode - widely used - but it's really for someone who struggles with controls on a specific side.
matatk: I was thinking about widescreen monitors and space wasted by toolbars on the top. Used to be options in various Linux/UNIX GUIs to have toolbars on the side or bottom instead. Related?
PaulG: +1
PaulG: There's not really mention of that in the issue; suggest you comment.
… For Dark Mode it starts with a system preference. This is more web-focused. Coudl be adopted by others for other use cases?
PaulG: Is this something that Adapt TF would want to talk about?
… and maybe communities they talk to?
matatk: Worth mentioning in the call and hearing thoughts on this - I'll raise it with them
PaulG: Could be good for generating use cases.
matatk: RQTF too maybe - let's spread the news within APA
… Maybe worth announcing there. Maybe ARIA will be interested.
PaulG: All the examples given are left/right. But your new use case is e.g. top to left - need JS for that now. Need to link to Media Queries, API, observer, accessibility properties. Lots of steps; need other groups to weigh in.
Actions Checkin (Specs) issues/assigned
<PaulG> https://
*general discussion on the CSS color/shape issues from prior weeks*