Meeting minutes
Intro to Adapt
matatk: Introduces WAI-Adapt beginning with personal introductions ...
[intros all around]
CG Work
AdamSobieski: Introduces the CG
AdamSobieski: Shares slides ...
AdamSobieski: will email slide deck to Adapt
matatk: all sounds compelling -- and notes incorporation of Adapt thinking!
matatk: Asks about CG deliverables?
AdamSobieski: At this point thinking first of outline functionality
matatk: Notes the problem of finding the specific adaptation the user may need; sometimes finding that specifif item is the a11y challenge
janina: I'm delighted to hear that cogent and complete overview of what's possible, especially when we throw AI into the mix...
… In the Research Questions TF (RQTF) we are working on a document looking at use casses.
… One problem is finding the right adaptation for the user, and hiding the others.
… Getting these things into a user profile that directs the adaptation would be helpful.
… This need emerged from the Accessibility at the Edge CG (looking at post-source accessibility).
… Can be powerful to apply rule-based adaptations at that stage - or even more powerful, AI-based ones.
… I think we want to think about hiding things that are problems for users - e.g. adapting foreground and background color isn't relevant for me. If you know that context and we can set that in a predictable way, that would be helpful. I don't want to repeat that with every AI I use.
… Really excited by what you've talked about AdamSobieski
… I think this is where W3C needs to go in the next 5 to 10 years
matatk: Notes much of our concern is in education; also in proper TTS pronunciation
matatk: Notes context may be knowledge domain specific
matatk: Notes example of chemistry diagrams esp in assessment situations
janina: I think 'domains' is an important thing - biology very different to music or theology. But may use the same words with different meanings.
… so telling AI about the domain may increase the quality of the results we get.
… We've talked about this at various TPACs but never got enough agreement on it. Specifying a knowledge domain could really help.
AdamSobieski: Agrees it makes sense .. Glad aI and education came up
AdamSobieski: Also thoughts on accomplishing knowledge domain specificity
Irfan: Is there any plan of advertising personalization specifics? Cross-origin data shiring
AdamSobieski: Not previously considered ...
AdamSobieski: Certainly privacy and security concerns; but also an opportunity to define trusted sites
Intro to Adapt Current Work
Well-known destinations: https://
Symbols - example 1: https://
Symbols - example 2: https://
matatk: Introduces site navigation and Discoverable Destinations
matatk: Still under construction, but solution seems well in hand; needs example implementations
matatk: We're relying on link elements; could be rhel values, etc
matatk: Tokens a user doesn't see; but presentable to the user in appropriate ways
matatk: Next introduces AAC symbols on web
https://
Content Usable (COGA): https://
Also suggest the "Aspirational Section" of: https://
NOTE: Adam's slide deck is provided at: https://