– DRAFT –
Adapt Weekly Telecon

Administrivia

Next week we have meeting with the Adaptation and Personalization CG: https://www.w3.org/events/meetings/54e9a3f5-fd58-4371-be54-5af629aec28b/20260428T100000/

CG: https://www.w3.org/community/adaptation/

matatk: For Symbols, next week I could show the demo I showed at TPAC last year.

matatk: Did we update our slides re 'well-known' to 'discoverable' destinations?

Abhinav: Explainer yes, slides no

matatk: I'll try to update so we can show it next week

matatk: Will see if we have a good overview of the roadmap on the wiki, or in historic slides.

Abhinav: I will be on next week.

Thoughts on Well-known URI for accessibility reporting

https://autosponge.github.io/well-known-accessibility-report/spec

APA Minutes: https://www.w3.org/2026/04/08-apa-minutes.html

matatk: As Paul noted, he's proposing that well-known URIs _and_ @rel types be supported, so the author can use the one that fits best.

Abhinav: It's a good and mature proposal. Lots of depth.

matatk: Issue of context came up there, I was reminded of it... we need to be very clear in our work that DDs are site-wide (e.g. accessibility statement is always on a fixed page in whatever the 'site' is; whereas 'first step in the process I'm in' varies with context).

matatk: Is what Paul proposes a DD?

Abhinav: Yes

Abhinav: Primary proposal is well-known, then link type

matatk: I was assuming the feature was a UA/extension, that button in toolbar appears in browser, then sidebar/extension appears when activated, to collect standard info, and submit to endpoint.

Abhinav: What Paul was proposing to me was for an individual site, as each has their own set of info to report.

matatk: If you follow the link to the page to report the problem, you have left the page you were on; is that desirable? How does the form know where you came from? HTTP referer header?

Abhinav: we shall have to check the spec

matatk: It sounds like it has a lot in common with DDs

matatk: I think I should raise with TAG again - maybe helpful to have a design principle to say when we should have a well-known URI and when use links.

Abhinav: I think there are cases where well-known make sense, and some where links make sense. For us I think we should err on links.

Abhinav: well-known is for very global stuff (home, accessibility statement, accessibility reporting); but a contact page for a hotel, or something when you're logged in, not global; a <link> is more suitable there.

matatk: I think it's worth me filing an issue to ask the above question about the flow, and context; and also to check TAG design principles.

https://www.w3.org/TR/design-principles/

matatk: Steps to adoption... Note (for BPs); WHATWG (when we have demonstrated the use).

https://whatwg.org/

matatk to review w3c/adapt#335 (thanks Abhinav!)