– DRAFT –
Adapt Task Force Teleconference

Welcome and Announcements

People are joining, we are waiting for more participants ...

WKD Options Demo -- Matthew

<matatk> https://w3c.github.io/adapt/presentations/ac2024/

Matthew is presenting ...

Notes this is a slightly different take from previous work on destinations ... Matthew will explain

Welcome and Announcements

WKD Requirements Discussion with COGA Representatives

lisa: Very good implementation, would love to see more

lisa: recalls first module, we didn't have the IETF spec to plug into

lisa: can it extend to things like "reach human help"??

lisa: what's the right page for feedback? or dealing with getting stuck?

lisa: real value in adding more things so people get in the habit of things like Ctrl-P for print

lisa: Ctrl-H take me to help

lisa: notes that help is sometimes too much -- can we support smart help?

matatk: Wondering

david: Looks great--clear solution solving many problems

david: Wonders whether there's a problem of too much leeway so can become ambiguous

julie: great presentation, have been clicking through the demo site

<julierawe> SamsungInternet/wkd-prototype

julie: wonders about contact vs help?

matatk: Notes that wkd will be subject to review; notes original list came from COGA; our list is a list of POSSIBLE destinations

matatk: Not every site will support each available wkd; but if they have one, they CAN support it

<Lisa> where is the speck?

<Zakim> Lisa, you wanted to ask about subsite home page

lisa: Notes Ctrl-P is UA specific

lisa: would like help to be smart

lisa: asks to go back to coga before we lock in on terms

lisa: we can coordinate time to have the keyword and the help conversations

lisa: wonders about page title

lisa: notes subsites of parent page is the plumbing issue

lisa: Content Usable will propose a way to go home vs subsite destination

matatk: Notes Abhinav has raised some of these same issues; good to hear there's agreement on use cases

<Lisa> and maybe base it on the rest architecture

<Lisa> REST

matatk: Notes there's a current weakness in our IA here related to this

matatk: We're unclear what the ultimate engineering approach will be; though we like the idea here for now

matatk: Notes there's possibility of beginning of addressing simplification; but it's different and not supported in IETF approach

matatk: We need to be careful to think not of all potential tech, but of the use cases

matatk: Notes 75-80% feedback from AC was positive; but remainder had objections

matatk: Need to hear from COGA to respond appropriately to the objections

matatk: one implication of this approach is to request a list of wkd in one http roundtrip

matatk: But is that critical? From the page one is currently on?

matatk: Or can we forego that

Lisa: How to show options for people if one doesn't do that? e.g. like bookmarks

lisa: concern to rank friendliness of site -- though not all that's needed, it's helpful to have this

matatk: Is this a COGA pre-identified need? But if there other nav requirements more important that we should address first? That's important for us

<Lisa> link to what this would be supporting : https://www.w3.org/TR/coga-usable/#support-a-personalized-and-familiar-interface-pattern

matatk: Notes this approach doesn't handle well: context; actions

matatk: This approach does destination brilliantly, but not the others

matatk: Also notes wkd are stateless; so Ctrl-P would not be a possibility from this approach

<Lisa> https://www.w3.org/TR/coga-usable/#objective-8-support-adaptation-and-personalization-0

lisa: We could improve those hooks in our next rev

matatk: Referrer page should be checked when help invoked

matatk: Could help solve context help without new tech

Lisa: Like help, can we pass other data e.g. preferred communication tech -- phone, email, text

Lisa: Would be OK if rev 2, but powerful to pass preferred mechanism

Lisa: It's something set once and remembered by UA

Lisa: Notes "help" is more than context, it's also I need a human, etc

Lisa: also to support feedback mechanism

Lisa: Critical to have those mechanisms

<Lisa> preferd mechanisim is realy important, email, phon,e chat etc

janina: Notes we can make a11y argument to include wkd so that WCAG and regs can require implementation to conform/comply

maWe need to satisfy ourselves that we will not block something we want very much by going down this road

<Lisa> feedback and reach a humen are two critical needs

janina: Restates need for incremental discovery vs full list from any site page

matthew: Discovery is an issue

lisa: That's why I mention titles --

lisa: Say: "home page for my subsite is here"

matthew: we're committed to making this work and thanks all around!