– DRAFT –
APA Weekly Teleconference

<janina> /join #rqtf

agenda

zakim next item

Agenda Review & Announcements

TPAC 2026

<matatk> https://www.sovereign.tech/programs/standards

Opportunity of funding for open source contributor to join TPAC 2026

Paul: It is still not working and still spinning after submitting

janina: we will work on meetings agenda for TPAC 2026 soon

CSS Update (Paul)

<PaulG> w3c/csswg-drafts#9706

Paul: we will get to this today, psuedo classes usage

<PaulG> w3c/csswg-drafts#12659

PaulG: How and where aria-current atttribute should be implemented

matatk: Carausol usecase is bad usecase, but if they are doing it here it should be at other places as well, because consistency is needed

PaulG: They want to use aria-current=true, but it is not focusable it is of no use

matatk: Let Paul ask questions from his side and then we can check from APA side

janina: Can we ask - all Paul questions are APA questions?

matatk: APA answer-Should :checked and :indeterminate be exclusive? - yes they should be exclusive to match with ARIA and in future please make a match with CSS pesudo classes

PaulG: yes keep them exclusive and we want to see a separate proposal to match with CSS pseudo classes

PaulG: summarizing both issues for stevef

<PaulG> (article with example code https://www.sarasoueidan.com/blog/css-scrollspy/)

stevef: aria-current why do we have to label it?

stevef: It is sounding incorrect to add aria-current in DOM tree

matatk: They are just proposing to add semantics

janina: not so fast from APA side

janina: for the second issue

stevef: what ARIA WG take on this

TPAC 2026

Spec review requests

New on TR

Recognized Entities v1.0

<Roy_Ruoxi> - spec: https://www.w3.org/TR/vc-recognized-entities-1.0/

<Roy_Ruoxi> - tracker: w3c/a11y-longitudinal-tracking#47

Roy_Ruoxi: new publication

Roy_Ruoxi: they want to define data model for entity

janina: it is way below structure and we are fine with this unless someone wants to take a dig in it

Issue tracking

WebMCP Accessibility Considerations

matatk: people should read these issues as these are from agentic web and accessibility

<matatk> w3c/a11y-tracking#318

MCP protocol for agents to communicate

<janina> NOTE: MCP = Model Context Protocol

matatk: agents using this protocol, respect ARIA, this discussion in early stage, it is better to start participation

<PaulG> keep in mind that WebMCP may get tied to Goolge's google/A2UI where agents generate UI on demand. I've been opening accessibility issues there because it's extremely naive.

janina: Do we have a timeframe on it?

PaulG: code ot UI generated with this is still not accessible for AT users

PaulG: will keep an eye on this

Redundancy with the accessibility tree

<matatk> w3c/a11y-tracking#317

matatk: if agents should get all the things that they need for accessibility tree is a point of discussion

matatk: there are a couple of other items in the discussion and please read through it and add your thoughts to tracking issue

janina: isn't is creates a semantic structure already ?

matatk: do we need any technical protocol for communicate or we already have all this information from accessibility tree

matatk": this is the question and read it to hve more thoughts on it

q:

q:

Draft Review Process Doc for APA Members

<matatk> https://github.com/w3c/apa/blob/main/process/spec-review-guide.md#creating-proposed-issues-for-apa-discussion

<matatk> Sorry; link above too specific; here is full guide: https://github.com/w3c/apa/blob/main/process/spec-review-guide.md

janina: explaining the schema

janina: document of horizontal review process of APA

janina: word document and specification are synonyms - can it document throughout?

janina: will file an issue