Meeting minutes
<janina> zakim guide: https://
Agenda Review & Announcements
janina: Regarding the meeting with the web AI group, links to follow
<matatk> Web & AI IG minutes from Monday: https://
matatk: The minutes just pasted contain the links to the recording and slides
<matatk> https://
marcelo: Is there any reference in the AI tools document to understand how the tools themselves (for example Lovable) would be accessible
matatk: Additional perspective on AI tools, are the inputs accessible (covered by WCAG)?, are the outputs accessible, including code snippets or whole apps?
<matatk> https://
matatk: Feel free to review and comment on the issues.
<Zakim> stevef, you wanted to enquire as i thought i had been assigned a spec review
Spec review requests
Accessibility Implementation Guidelines (DVB BlueBook A185)
<matatk> request: w3c/
<matatk> tracking: w3c/
<matatk> Due: 2025-11-30
matatk: Regarding the DVB review request - anyone with expertise, please do make comments
CSS Anchor Positioning Level 1
<matatk> request: w3c/
<matatk> tracking: w3c/
<matatk> Due: 2026-01-30
matatk: Regarding the Anchor positioning, a document is being started and will work on it together.
matatk: Will create the google doc and share, request access if you'd like to work on it
matatk: TAG discussion on the concerns, could there be concerns when content moves in certain situations (e.g. Zoomed in). This spec is about giving the authors more control so this paper/proposal is unlikely to get worse from anchor positioning. Adding a risk in the accessibility considerations seems sensible.
Selectors Level 4
<matatk> w3c/
<matatk> Due: 2026-07-22
matatk: New item, not currently on Agenda. A11Y request for Selectors level 4
matatk: As a fundamental part of CSS, is this of interest to anyone?
matatk: No current interest but will continue to make this available.
Issue tracking
WG New Spec: Scroll-Triggered Animations
<matatk> source: w3ctag/design-reviews#1167
<matatk> tracking: w3c/
matatk: Have created a google doc on this. You need to request access to edit it. More editing to come.
matatk: Tracking issue 272 will give the link via second comment
Coordinates of keyboard-driven click events
<matatk> source: whatwg/html#12117
<matatk> tracking: w3c/
matatk: Concern that keyboard 'click' event at 0,0 would offset UI inappropriately.
Dark mode ReSpec display issues
<matatk> speced/
<matatk> speced/
matatk: Two issues raised, the ReSpec is not displaying dark mode consistently (light and dark mode, contrast mode when styled not being accounted for). Please feel free to comment on them.
PaulG: Regarding the coordinate issue - using the middle of the element wouldn't really be helpful as it's as consistent a pattern as 0,0. Random, fake coordinates could affect existing processes or dependencies. Keeping at 0,0 may a good flag for useful tooling.
Matatk: Will update the issue per Pauls comment
<Crispy> Quit
zakin, end meeting