W3C

- DRAFT -

Accessible Platform Architectures Working Group Teleconference

24 Jun 2020

Attendees

Present
jasonjgw, janina, Joshue, SteveNoble, scott_h, Joshue108
Regrets
Chair
jasonjgw
Scribe
SteveNoble

Contents


Accessibility of the Web of Things.

Jason: Web of Things taskforce has begun

<Joshue108> Open survey https://www.w3.org/2002/09/wbs/1/wot-uc-priority-202005/?login

Janina: survey response requested by Friday

<Joshue108> https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-1-2_unified-smart-home-control-and-status.md

<Joshue108> Unified Smart Home Control and Status Interface

<Joshue108> Audiovisual Devices Acting as Smartphone Extensions

<Joshue108> https://github.com/w3c/wot-usecases/blob/master/USE-CASES/mmi-1-1_audiovisual-devices-as-smartphone-extensions.md

<scott_h> link to IoT report: https://www.ncsehe.edu.au/wp-content/uploads/2018/08/2017-IoT-Report-FINAL-20171020_Accessible.pdf

<Joshue108> Great Scott! We link to that from here https://www.w3.org/WAI/APA/wiki/Wot_usecases

Janina: experience was that software for configuring devices is often innaaccessible
... third party vendors for "middleware" are not necessarily making these applications accessible

<Joshue108> https://www.w3.org/WAI/APA/wiki/Wot_usecases

Jason: use case development for our group will take longer than this week

But we could flag something now in the short term, and develop our use cases in the longer term

<janina> Amazon's Frustration Free Design guidance for developers is here:

<janina> https://developer.amazon.com/frustration-free-setup

Jason: conformance claims for an entire process, such as setting up and operating a device, becomes complicated due to different parties being involved

<janina> And the logo that goes with it is 'Certified for Humans:"

<janina> https://www.amazon.com/b?ie=UTF8&node=19982322011

Scott: example of Google assistant setting alarm and changing alarm sounds are handled in different ways

Judy: example of the miniapp framework and the work going on there

Janina: need to consider some possible quick consensus response to the survey

<Joshue108> https://github.com/w3c/wot-architecture/blob/master/USE-CASES/mmi-1-1_audiovisual-devices-as-smartphone-extensions.md

Janina: we should be able to support that use case

<Joshue108> Unified Smart Home Control and Status Interface

<Joshue108> https://github.com/w3c/wot-architecture/blob/master/USE-CASES/mmi-1-2_unified-smart-home-control-and-status.md

<scott_h> apologies, lost zoom conneciton - will try to rejoin

<Joshue108> JS: Set up and configuration information isn't addressed

Will mention in the APA call

<scott_h> sorry can't reconnect, will follow on IRC

Janina: we can respond to the survey by the deadline and also mention plans to address accessibility matters in the RQTF

<scott_h> support that Janina

Jason: next week to look at remaining issues in RTC and XAUR

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/06/24 14:01:44 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: jasonjgw, janina, Joshue, SteveNoble, scott_h
Present: jasonjgw janina Joshue SteveNoble scott_h Joshue108
No ScribeNick specified.  Guessing ScribeNick: SteveNoble
Inferring Scribes: SteveNoble
Found Date: 24 Jun 2020
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]