Meeting minutes
<janina> /join #rqtf
Agenda Review & Announcements
W3C Breakouts Day 2026
<matatk> w3c/
mtatak: Breakout day 2026 is coming, looking for talks, support, new considerations - TPAC style but standalone
matatk: Good for APA folks to even look at titles to get a feel for what's happening
matatk: read me has all the information and dates
matatk: Think about presenting based on your task force - especially if looking for greater input.
Meet the TAG
<matatk> https://
<Fredrik> So Steve is officially the main man. Thanks for clearing that up.
COGA and WCAG 3
<matatk> scribe+ Eric_hind: COGA is taking a super deep dive into the current WCAG 3 draft - bear with us.
<mpaiva> I am looking forward to seeing you all in Dublin
<matatk> janina: This is a great opportunity to look into WCAG 3 for everyone. Architectural decisions are being made.
<matatk> janina: More to come up on this call soon!
New charters review
[wg/webperf] Web Performance Working Group Charter
<matatk> w3c/
matatk: link is to the delta between the previous and proposed charter
matatk: interesting a11y perspective on reporting, could this help report accessibility issues? But there are privacy considerations.
matatk: Since this is intended to be normative, taking a look at this with an a11y perspective would be good.
matatk: Nothing of worry here, but worth having a think about from our group.
<Fredrik> +1
matatk: Any objections to approving the charter?
<Fredrik> rrsagent. make minutes
<Eric_hind> +1
<Neha> +1
<stevef> +1
matatk: No objections, we will support this
New on TR
CSS Selectors Level 5
<matatk> https://
matatk: This is already partially supported - there are a few items of note/intrigue. Such as semantic heading selection.
matatk: We should have a look at it after CSS Level 4.
paulg: Section 3 might be worth attention, guessing user intent by hover/focus, among other items.
<matatk> https://
paulg: Text is deep on visual perspectives and may not have AT perspectives as well as it could
matatk: Making it more consistent would be good.
matatk: Can be hard to fit this into the various platforms and agents.
matatk: CSS Level 5 assumes semantics and selectors will go together - if not, then it becomes problematic in the future.
paulg: There are some implicit assumptions around ARIA and other a11y perspectives.
janina: Feels this should be an APA issue as does matatk
matatk: Will draft the issue per the process
Dpub/DAISY Extended Description Draft
<janina> https://
<Fredrik> Assign me!
janina: Email request from Dpub. We should file one of our issues on this.
<Neha> Add me as well
matatk: Fredrik will review, about certain types of content and best practices not working for Dpub.
matatK: Will make the issue and assign the interested folks.
<mpaiva> https://
<matatk> https://
<mpaiva> link to the issue: w3c/
matatk: AI and accessibility, we need participation and mpaiva will be jumping
janina: Note that updating CAPTCHA is in queue this year too
<matatk> This doc to be updated this year: https://
Spec review requests
Accessibility Implementation Guidelines (DVB BlueBook A185)
<matatk> tracking: w3c/
<matatk> Due: 2025-11-30
janina will be posting on this very soon after some edits
CSS Anchor Positioning Level 1
<matatk> tracking: w3c/
<matatk> Due: 2026-01-30
matatk: We have discussed and content was updated in the google doc found in issue. If you'd like to edit, ask for rights.
matatk: Some examples were created by neha which we could copy and paste. We need framing text to allow it generalize
paulg: For the example code, willing to test or validate. Concern that focus gain/lost and reading order is not as usable. Practical testing does allow real-world compatibility
matatk: agree that this is a good thing to show the teams - suggest that anyone who works on the examples (popover, describedby, custom disclosure), mention it in the issue
paulg: Biggest concern is the custom disclosure - the popped or open item may not be a direct sibling
<mpaiva> so we need demos for: tooltips, popovers, accordions, notifications?
Selectors Level 4
<matatk> request: w3c/
<matatk> tracking: w3c/
<matatk> Due: 2026-07-22
matatk: Looking for assignees. Feel free to assign yourself to the issue.
Issue tracking
WG New Spec: Scroll-Triggered Animations
<matatk> source: w3ctag/design-reviews#1167
<matatk> tracking: w3c/
<matatk> We need to continue working on the draft.
matatk: Outline of what should be included is there - with some comments. Looking for conversations to kick off on the sections, a good start but need some momentum
matatk: Anyone who wanted to contribute, not been able to. If so, request edit.