Meeting minutes
Agenda Review & Announcements
Web Engeins Hackfest 2026
TPAC 2026
<matatk> Current state for review is on the wiki: https://
matatk: I've filed for 3 of 4 meetings
… Accessibility Guidelines Working Group, Accessible Platform Architectures Working Group Joint Meeting (Adapt discoverable destinations; symbols; AG updates/needs - possible RQTF involvement?)
Media and Entertainment Interest Group, Timed Text Working Group, Accessible Platform Architectures Working Group Joint Meeting (media taxonomy; MEIG & TTWG updates; MAUR 2 possibilities?)
Web and AI Interest Group, Research Questions Task Force (of Accessible Platform Architectures Working Group) Joint Meeting (RQTF's AI doc)
WHATWG, Accessible Platform Architectures Working Group Joint Meeting (Symbols PoC; Discoverable Destinations update)
… I want to go over the other 6 meeting suggestions
… Authoring Tool Accessibility Guidelines Working Group (assuming it's set up by TPAC).
We could point them to relevant RQTF work; Adapt's Symbols and Discoverable Destinations work? Also Maturity Model?
maybe we could add pronunciation
matatk: I've added it
… CSS WG
… user stylesheets could be exposed through less-technical means
… there's overlap with semantic selectors which I added to the wiki
… many developers aren't aware of features related to accessibility so we're looking for ways to raise awareness
PaulG: Concern on #2: How overwritten or nullified? We don't have ability with sudo
matatk: Added
matatk: there's all sorts of stuff coming for immersive web so I really want to meet with them
matatk: #4 Joint meeting with CSS, ARIA, and WHATWG regarding HTML in Canvas outstanding issues.
… we need to make sure there are actual issues to discuss at the time of TPAC
… #5 Would we want one with Publishing Maintenance (specifically accessibility people)
… we mainly need to discuss this extended descriptions spec
… #6 Joint APA, ARIA, AG meeting to discuss cross-cutting challenges that come up (e.g. Carousels, HTML in Canvas, …) - could do this as a breakout? Does this need to include AG?
PaulG: a question and an idea. question: I've seen a couple of these ideas; they seem to've started in Open UI or developed in Open UI. I don't know how Open UI relates to W3C and are they represented at TPAC? If they're not, can we get them there?
paul: A question and a notion ... Q: Is Open UI related to W3C? Are they at TPAC?
PaulG: When they're fostering ideas of a pure CSS carousel, can we get involved then?
paul: We need to be in comm with them
PaulG: The idea is maybe we could hook into something like Baseline where emerging patterns can be published with support info, and where there are question marks (certain combos of AT and platform) the info can be crowdsourced.
paul: Interested in emerging patt4rns being crowd sourced for eval and testing
paul: Seems could be baseline
matatk: could meet with Open UI and CSS?
janina: Could answer that as we explore policy with WAI and solutions and approaches with Open UI / CSS
<chiace> One thing I wonder is whether we should also frame one discussion around current accessibility barriers, not only around the technical solutions.
<chiace> For example, which barriers are users still encountering despite existing standards, which ones developers consistently miss, and which new barriers are emerging from modern frameworks, AI-generated interfaces, Open UI patterns, Canvas, and immersive web?
<chiace> This could help us prioritise where APA input is most needed across CSS, Open UI, ARIA, WHATWG, AG and developer tooling.