Meeting minutes
<janina> gb, off
<matatk> gb, status
<gb> matatk, the delay is 15, issues are on, names are on, full issues are printed 10 at a time; and the repository is w3c/
<matatk> gb, off
<NehaJ> +present
Agenda Review & Announcements
<matatk> https://
matatk: Document is about AI and the web, result of the whole w3c, can recommend reading this
janina: RQTF will also focus more on this topic in the future
Fazio: Really good that we start looking at AI more
TPAC 2024 Planning Begins
matatk: Please raise TPAC in your groups: With who do you want to talk about what?
Request to put 360 Captions Report on Note Track
<matatk> https://
<matatk> https://
https://
janina: This report could help drive the design of these systems. In RQTF we voted on a solution today: See link above
janina: Next step will be a call for consensus
New Charters Review https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22
Federated Identity Working Group Charter
<Roy> - charter: https://
<Roy> - issue: w3c/
<Roy> Adding Digital Credentials to the FedID WG
<Roy> comments from APA last time: w3c/
Roy: It is a re-charter. We reviewed it a few months ago.
matatk: A lot of development there, since the last time I looked at it. Any a11y from anyone?
*Any a11y concerns
<Roy> w3c/
Privacy Principles review
<PaulG> https://
<PaulG> "All of these sources of data can reveal personal data about a person's configuration, device, environment, or behavior that could be sensitive or be used as part of browser fingerprinting to recognize people across contexts."
<matatk> Tracking issue for this review: w3c/
PaulG: There is one section, I want to empathise: see above
<JenStrickland> That's a great point PaulG. Using the mosaic effect it's possible to use that data along with other data and be able to identify individuals, for a variety of purposes — without informed consent and privacy considerations.
<JenStrickland> I do need to drop for a different meeting, and am infinitely grateful that PaulG raised this! Thank you!
<JenStrickland> These considerations can also impact folks for uses like NSA, identity hacking/theft, etc.
PaulG: We need to make sure that everything that sits on top of these APIs, the devices and so on, need to be accessible.
matatk: I think raising a Github issue is the way to go here, you can do it yourself
CSS Update (Paul) https://github.com/w3c/css-a11y/issues
PaulG: I responded in the list about the color-contrast
<PaulG> w3c/
PaulG: Automatically switching colors to meet contrast requirements. However, too much contrast is also programmatically. We propose a clamp solution (with a maximum and a minimun)
matatk: Please read through the issue and add your points/ ideas, if you have any: See link to the Github issue
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
Task Force & Deliverables Updates
RQTF
<matatk> https://
janina: We are worried, not enough people reviewd/ looked at the ctaur document
<matatk> Collaboration Tools Accessibility User Requirements - review request coming soon
<matatk> Side note on *AUR docs: Digital Accessibility User Requirements - https://
Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/actions/open
Update the accessibility section 14 to include RFC 8865 for real-time text in WebRTC data channel
<matatk> w3c/
Allow additional elements to be considered labelable
<matatk> w3c/
matatk: We talked about this before and thought it was good idea
<matatk> whatwg/
matatk: We wanted to make sure the click to focus works. Paul added this comment (see above) for this reason
Task Force & Deliverables Updates
Other Business
matatk: More TPAC information: W3C is 30 years old, founded in 1994. There will be something on TPAC
matatk: 5.4 billion people have access to the internet, so our work can and will have a big impact on a lot of people. Keep up the good work