<scribe> scribe: joconnor

McCool: We have a bunch of things we would like to talk about.

Important to get Michael Lagallys input here.

We do not have a use case for a11y

We could write one for IoT devices

e.g finding accessible services

McCool: We do have a template

One focussed on a11y could be helpful

Lagally: Goes over current use cases

Smart homes and Multimedia etc

Input from RQTF would be useful.

Items related to discovery would be good.

Janina: Discovery is important.

We did discuss cases via the WBS survey circa TPAC time.

<kaz> WoT Use Cases Note Editor's Draft

McCool: There are other categories - access to existing services, or creating new ones for wheelchair users

Janina: Also for blind users needing direction services

McCool: We have AR use case we are working on.

Joshue: Michael have you a URI for any of the AR work?

Janina: Should we point them to the Silver XR work?

<McCool> https://github.com/w3c/wot/issues/955

Silver XR sub group https://w3c.github.io/silver/subgroups/xr/index.html

Plan 2nd meeting with Spatial Data on the Web IG/AR #955

<kaz> VR/AR use case

Janina:

McCool: I've been collecting info on other related work

Please put that into the GH

McCool: There is also the Geolocation info, we have Smart Cities Geolocation etc
... We hope to have a more concrete spec, looking at Geospatial queries etc

Scott: To ask - what about education and WoT?

I've been doing research - what about a student who needs access to beakers and IoT devices?

There was another use case where students using AT can interact with Whiteboards?

Is that useful?

ack /me ok

McCool: We are talking about science related use cases.

Kaz: To mention, that during one of our f2f meetings, we had professor Tamura from Sophia University - he had some proposal and we can ask him to contribute

We also have interest from the publishing group - new generation publishing - audio books, and new media publication

Lagally: We have some angles here - use cases

that effect other specs - if there are semantic annotations for specific devices we may need to include ontologies etc

Core use cases?

We are looking for straight and direct options if possible

Alternative ways of operating on things.

<Zakim> joconnor, you wanted to talk about future work on use cases

Joshue: Are we going to add to WoT group use cases or are APA going to create a user needs document?

Janina: I'd prefer WoT to do this.

Lagally: As would we.

We need review and contribution etc.

And a review of any that are not covered.

McCool: Review of our specs is good - or writing them up independently.

We have a process and a repo

<McCool> https://github.com/w3c/wot-usecases/tree/master/USE-CASES

Lagally: Please do join the next use case call Feb 9th

Janina: Please send to list

Lagally: We encourage you to join, we run them every two weeks.

PRs welcome

We have a bunch or horiz - and vert use cases - need to extract them

Kaz: Info on our approach - we first collect use case descriptions and categorize them

Into common and vertical specific use cases

A11y is a common horizontal req - if you can think of industry specific let us know

Josh or someone can join the use case call etc

and think about how to capture requirements

We can look at the existing ones from a11y docs and think of both directions.

Janina: I'm trying to get our colleague who worked on 24752 involved - Gottfried Z

McCool: Our problem is finding people to do the work.

Getting more people with expertise and time is important.

Janina: Understood.

It would be good to get someone in there consistently.

There is a lot of material to go through

<scott_h_> Education use cases ref: https://www.ncsehe.edu.au/wp-content/uploads/2018/08/2017-IoT-Report-FINAL-20171020_Accessible.pdf

We have rough drafts, but they will help with getting people to understand what we are doing

https://www.w3.org/TR/xaur/

XR Accessibility User Requirements

Joshue: This will be useful for your work and may inform your user requirements for WoT/AR
... A challenge for us is to identify the locus of responsibility regarding a11y in XR, and emerging tech like WoT

McCool: There are other services that will enhance a11y - regarding the locus, the WoT group should be going more here and we need help.

Janina: +1 to all of that.

McCool: Agenda check
... Regarding Ontologies - thing descriptions and sensory modalities

Some may not be accessible - so they may need to be remapped.

Devices turn up in the network API

There may be capabilities but no documentation

We are trying to solve this.

Janina: This is a song APA have heard many times.
... We like to say 'no API with out documentation'

McCool:

There is an issue with very small devices and the overhead of including documentation in micro devices

You may need human readable names - in multiple languages

bone of contention.

Regarding the thing mode - description of class of devices etc -

Thing descriptions only need the necessary info to do what they need to do.

Other metadata should just be in the thing model

can be refered to on a need to basis.

So what are the use cases for when this isn't good enough

Kaz: Just to think of "human readability" information in TD would not suffice, we need to think of when and how that info should be presented to the users.

We need input from a11y experts here.

Judy: I liked Michaels description of the problem - regarding sending help info from small devices etc

Can you use progressive disclosure etc?

Is that doable?

McCool: This is probably reasonable.

We've added this capability to new directories etc

To give minimimum TD for connection and when generating UIs you may need to be served with more info.

Judy: How easy could that be for the user?

McCool: This is relevant and leads back to a discovery requirement.

Kaz: Our points were related.

McCool: The context of use is important.

End user, or a user with a disability?

They may not need to know about package encoding details or semantics.

But diff natural language is required.

Languages and contexts could be captured in TD.

Joshue: This is great example where we need a clear user need.

Rather than just riffing on requirements

Janina: Maybe on the dashboard level we need this.

Are we creating a self assembled dashboard here?

McCool: Yes

Janina: With the contextual data you need?

McCool: Right

With descriptions etc

McCool: This is general usability

<Zakim> Judy, you wanted to ask about progressive disclusure of relevant documentation, with preference-setting by user

<sebastian> I'm sorry, I have to go. Thank you for the meeting.

McCool: I'll relate this back to Michael

Will raise natural language and profile issues - these were lucky things..

If we follow up on looking at use cases etc we will extract more.

Getting input from an a11y person would be good.

McCool: We've also talked with the privacy group.

Looking at May for primary draft of CR

not a lot of time.

Aim for March for internal first drafts - we need feedback as soon as.

We will recharter next year - willing to break backw compat.

Janina: Sounds reasonable

McCool: Short term heavy workload.

Judy: If there are placeholders for planned work etc that can make things smoother.

For a taxonomy of use cases etc - what about WAUR? WoT A11y User Requirements etc that we can figure out who would work on that.

McCool: We have use cases in our repo - and easier if you make PRs, modifications and new ideas welcome please.

Please do review current use cases document

We are working on some AR use cases - and wish to capture a11y aspects.

So do focus on WoT use cases doc

There is also the discovery doc

Privacy and Geolocation based discovery will be an issue

A11y is also a part of the stack - what are appropriate controls etc?

McCool: We will want to exclude what is unnecessary
... Having help from a volunteer etc would be great - do post things to the issue tracker.

I'm happy to guide through the process.

Janina: Will follow up with Gottfried.

McCool: We will meet again when we have concrete drafts.

In March there will be a virtual F2F.

March 15th-26th - we will allocate time

I can grab a slot to discuss a11y with the group.

Janina: Very good.

trackbot, bye

<kaz> kaz: thinks there are at least 2 levels of work, 1. guarantee the current web accessibility within the WoT environment, and 2. new generation accessibility for IoT purposes