W3C home > Mailing lists > Public > public-rqtf@w3.org > April 2022

[WoT] Draft "Middleware" message--Please Comment!

From: Janina Sajka <janina@rednote.net>
Date: Wed, 27 Apr 2022 07:41:09 -0400
To: W3C WAI Accessible Platform Architectures <public-apa@w3.org>, public-rqtf@w3.org
Message-ID: <Ymkr1RXT2buGTRvA@rednote.net>

-- 

Janina Sajka (she/her/hers)
https://linkedin.com/in/jsajka

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa


attached mail follows:


Dear Michael, All:

I am mindful that APA has yet to sign off on WoT documents. I'm hopeful
we can quickly resolve the question that has arisen that would satisfy
our concerns.

For that to happen I need to briefly recall our last formal interactions
around the time of TPAC 2020. WoT had a series of use cases articulated,
and APA's Research Questions Task Force provided comments on
accessibility aspects of those use cases.

One question that arose from WoT was what specific accessibility use
case might need to be covered? As I recall, we were unable to articulate
anything specific at the time. We now do have a use case which is indeed
consequential, even though it's strictly informational.

We have discovered that many IoT devices are marketed as "works with
Alexa" or "with Google Home." Since Alexa and Home are generally
considered good for accessibility support, the customer may conclude
purchasing the device will provide something they can use, but this
isn't necessarily so because there is any additional level of software
required to manage the device which isn't always disclosed by device
marketing.

I'm referring to the ecosystems of device management such as Philips Hue
or SmartLife, just to name two examples. Among ourselves we have begun
referring to this level of device management as "middleware," having no
notion whether there's a more appropriate term current in WoT. We'll be
happy to change our terminology, so please advise on that.

The point, however, is that these middleware apps--whatever their proper
class name is--may, or may not be accessible. When they're inaccessible,
there's very little chance the customer enticed by "works with Alexa"
will ever succeed at getting the device to work with Alexa without the
assistance of a nondisabled third party helper.

So, our concern is that this "middleware" layer needs to be
systematically (and programatically) exposed, so that accessibility
advocates can advocate for accessibility support in "middleware," and so
customers can purchase with informed confidence.

Is this data layer exposed in the APIs your group is developing? If not,
how can we meet this accessibility use case going forward?

-- 

Janina Sajka (she/her/hers)
https://linkedin.com/in/jsajka

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Wednesday, 27 April 2022 11:41:23 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 17 January 2023 20:26:50 UTC