Research and Development Working Group Teleconference

Mark: comment from Yehya about specific type of exchange with APA
... worth discussion

Jason: PF has main meeting, and some of the people involved in TFs sometimes participate
... resources from the TFs are reviewed and approved by the main group
... mostly process-oriented

Shadi: Jason is right, TFs do not publish but WGs need to approve publication
... at least then there are discussions with the WG
... but that often rehashes discussion
... usually helpful to have common participants who act as bridges
... in addition, may be good to have the TF facilitators send a brief update from time to time
... and also join the main WG meeting from time to time, to present the update and provide an opportunity for questions & answers

Klaus: important to cover the logistics but need to get back to more content

Mark: agree but people need to be aware of the change of participation
... what are outreach opportunities coming up?

Klaus: we have a good collection of email lists that we used to inform people about symposia
... also can use social media, raise hand at conferences, etc
... maybe also desktop review of publications in the last year or two

Shadi: web of things is really important topic, but might also be attractive
... chicken and egg on getting this going
... but may be good to focus on
... also could think about outreach activity at Accessing Higher Ground

Mark: ASSETS also coming up

Klaus: AAATE in September

Web of Things

<mhakkinen> https://www.w3.org/WAI/RD/wiki/Web_of_Things

Mark: Web of Things vs Internet of Things?

Shadi: we believe that the web will be the value add to the internet-enabling of devices, just as on desktop

Jason: when using HTTP and web protocols, then participates in the web of things in addition to internet of things

Mark: looking at beyond HTML5
... like ARIA 2.0 and what is needed for such complex interactions
... what are the questions that need to be addressed

Shadi: we need accessibility use-cases for the underlying protocols to be developed
... is it all user interface only?

Jason: to make the interface accessible, there are implications on the underlying protocols
... like disclosing the device capabilities and functionality

Shadi: many of these are general interoperability requirements
... however, these are specifically relevant to people with disabilities
... need to highlight these requirements

Mark: smart thermostat in combination with voice command
... need to expose values and functionality

Shadi: how to collect such use cases?

Jason: need standard conventions for functionality and actions
... like the universal remote control console developed by Trace
... common APIs to make access more open
... self-describing if possible
... the hierarchy, data-types, etc
... can build user interfaces based on this

Klaus: describing use-cases is important, together with the technology implications

Mark: could form a small sub-group to get these examples started
... with Jason and Klaus

Jason: happy to volunteer

Klaus: good idea