– DRAFT –
WAI-Adapt Teleconference

Administratrivia

janina: We are on next week March 31
… no call April 7th due to holidays

Symbols

<matatk> https://github.com/w3c/adapt/pull/323/changes

<matatk> This is the last line we modified: https://github.com/w3c/adapt/pull/323/changes#diff-4dd2bf44f7ecfd30115aa4db9bec5323ad3b16a4638d505fbef8611b21f4b191R107

Russell: We envision that the symbol set vendors would produce a default font for their symbol set
… and possibly software for configuration, perhaps via a web app
… for the client as part of their communication solution
… they would customize the font, with modifications for an individual as needed

Lionel_Wolberger: The vibe coding revolution has greatly reduced the cost (time, human resources) of producing apps

matatk: When you load a font in the browser, the web app could find out about this via existing APIs
… which makes the end-user's selection of that font potentially something that the user does not want to reveal
… and would be part of browser fingerprinting

Discoverable Destinations

<matatk> https://github.com/w3c/adapt/issues?q=is%3Aissue%20label%3Aproposed-destination%20sort%3Aupdated-asc

<matatk> Here's where I am getting the proposed definitions: https://raw.githack.com/w3c/adapt/CR-content-2022-07-26/content/index.html#values-0

<Zakim> matatk, you wanted to talk about impressum, and again about context-dependent stuff later?

ack

<matatk> https://en.wikipedia.org/wiki/Impressum

<matatk> (could be contact/about maybe)

matatk: Some destinations, while we want them to be discoverable, are highly dependent on which user journey, process, or context the user is in
… for example, COGA has mentioned they would like "return to first step" or "go to last step", but the steps themselves are dependent on which multi-step process the user is engage with

Lionel_Wolberger: We should focus in this version on destinations with a wide global scope
… and avoid destinations that are constrained by a particular process, journey or flow

janina: We should gather these context-sensitive ones, and present that to COGA
… we can think about that more deeply
… what procedure journey am I in, and what destinations are important in that journey

ack

matatk: I would call these 'fixed' and 'dynamic' DDs
… the ones that are fixed, are like landmark regions for the site or page
… broad strokes, not fine details
… this other category of 'dynamic' would be helfpul.
… note, these may overlap with the 'actions' that we were exploring in another module