W3C

– DRAFT –
Stronger Together: Super-charging Agentic AI with Accessibility Destinations

10 November 2025

Attendees

Present
Abhinav, chiace, Janina, Lionel_Wolberger, Neha
Regrets
-
Chair
Janina Sajka
Scribe
Neha, Lionel_Wolberger

Meeting minutes

Janina: Introduced about agenda

Lionel_Wolberger: Going through presentation

Abhinav is sharing presentation

Lionel: How Agentic AI is seen

Lionel_Wolberger: Statement - Compare accessibility statements across 50 partner websites

Abhinav: Explaining the steps

Abhinav: How agent will work on this example

Floor is open for discussion

Discussion

goto: Login aspect

Abhinav: Discover -> Navigate -> Fetch

Lionel_Wolberger: We will be approaching this with layers

Mark_Foltz: How do we ensure that the discoverable destinations list remains accurate

Lionel_Wolberger: The Discoverable Desintaions metadata could be generated and corrected by a site-side bot

Mark_Foltz: Should be thought from scalability perspective

Janina: Explore maintenance side

David_Fazio: Most sites on the web are content management systems

ErikAnderson: This feels like a site map, are we duplicating effort?

ErikAnderson: Sitemap can be one option

Lionel_Wolberger: Erik you are speaking our language and this is what we are asking to add ne wattribute

Lionel_Wolberger: We are also open to work with existing markup

Lionel_Wolberger: .. because we are wondering hoe agents are finding these pages

Goto: Elevate to the browser UI?

goto: We can think of elevating browser UI

Lionel_Wolberger: that is what we dream for

goto: Login is 'special'

David: it can be overwhelming for some users

goto: a browser UI for login would likely be welcomed
… password management a social login is currently, more and more, being mediated by the browser
… making the web more useful to users
… and giving the user-agent more agency over login
… I agree, if we make thiese things more discoverable, we help users and agents

david_fazio: Recommend seeing 'making content useable"

David: should consider multiple use cases

Abhinav: please add in issue list of adapt github

https://github.com/w3c/adapt/issues

List of proposed destinations

Lionel_Wolberger: The list is in our github as 'proposed destinations'
https://github.com/w3c/adapt/issues?q=is%3Aissue%20state%3Aopen%20label%3Aproposed-destination

janina: We were thinking of it as 'predictable destinations' for a while

goot: yes, login is predictably necessary
… there are patterns to websites

Neha: We tend to use icons as well for login, logout

Janina: General idea is good one and still new to come up something concrete

janina: Seems the idea, in general, and the direction, is useful and meaningful
… There are issues with maintainability that came up
… anyone disagree?

David_Fazio: Elevating to browser UI is exciting, but if all the proposed destinations are elevated, it becomes a long list

janina: The list is long now, we expect to pare it down to the really key things

goto: Favicons and HTML Title have both been elevated into the browser UI
… constructive and uncluttered

David_Fazio: COGA may want to discuss it

goto: Change password URL does not show up in the browser per se
… the browser is sotring poor passwords, hacked passwords, and can offer the user an opportunity to change it

Lionel_Wolberger: One of the task for agent would be look for the accessibility of a website

<Abhinav> Slide Link: https://raw.githack.com/w3c/adapt/main/presentations/tpac-2025/index.html

<goto> I'm goto@google.com and I'd love to continue the chat, including this week at TPAC

Minutes manually created (not a transcript), formatted by scribe.perl version 248 (Mon Oct 27 20:04:16 2025 UTC).

Diagnostics

Maybe present: David, David_Fazio, ErikAnderson, goot, goto, Lionel, Mark_Foltz

All speakers: Abhinav, David, David_Fazio, ErikAnderson, goot, goto, Janina, Lionel, Lionel_Wolberger, Mark_Foltz, Neha

Active on IRC: Abhinav, chiace, ErikAnderson, goto, Lionel_Wolberger, Mark_Foltz, Neha, tidoust