– DRAFT –
WAI-Adapt Teleconference

<Abhinav> https://github.com/w3c/adapt/blob/explainers-post-tpac-2024/explainers/well-known-destinations.md

Welcome and Announcements

[https://lists.w3.org/Archives/Public/public-apa-admin/2025May/0000.html](APA Charter CfC)

<Abhinav> PR- w3c/adapt#279

<gb> Pull Request 279 Update well-known destinations explainer in accordance with TPAC 2024 (by matatk)

Lionel_Wolberger: Reviewing the charter with the attendees

Lionel_Wolberger: At the sentence "Supporting documents for WAI-Adapt such as WAI-Adapt Explainer and Requirements for WAI-Adapt, etc.;"
… ... this includes the Well Known Destinations procedure that we are developing, on a Note deliverable track

janina: Adapt may need something normative
… as Ruby markup for the purpose of Symbols would display by default, and we want symbols display to be optional (e.g.,
… a person who wants symbols would enable symbols display = on
… this capability may require a normative specification

Well Known Destinations

Lionel_Wolberger: Let's review the PR together
… w3c/adapt#288

<gb> Action 288 Add list of proposed rel values to explainer (on matatk)

janina: a Rel value can be HTML Main as well
… if we want to support hte COGA use case of managing distractions, we will want to support destinations within a page (A div or span) and not just a page

Abhinav: Matthew's polyfill shows both a well known destination label (e.g., login) and an icon

Lionel_Wolberger: We created issue 296 to discuss localization

Abhinav: Next comment, will the UA scan the page for <rel> attributes in the page, to construct a list of Well Known Destinations

janina: I recall that we expected the relevant <rel> attributes in the header, and will not depend on a scan