W3C home > Mailing lists > Public > public-rqtf@w3.org > July 2019

RE: WoT Architecture Accessibility review notes

From: White, Jason J <jjwhite@ets.org>
Date: Tue, 9 Jul 2019 15:51:10 +0000
To: Joshue O Connor <joconnor@w3.org>, "public-apa@w3.org" <public-apa@w3.org>
CC: RQTF <public-rqtf@w3.org>
Message-ID: <SN6PR07MB4864E6803967F8E0D87E3B53ABF10@SN6PR07MB4864.namprd07.prod.outlook.com>
Thank you, Josh, for these informative notes. I look forward to further discussion within the Research Questions Task force and the APA Working Group more broadly.

One question that comes to mind immediately is, in each case, how comprehensively the Web of Things protocols enable the use and operation of the device. Suppose a device has its own user interface that is not adequately accessible to the user. However, there is an accessible UI available for remote operation that depends on Web of Things protocols. Do the protocols sufficiently support the functionality of the device to enable the user to operate it remotely, or are there important (perhaps even essential) functions that can only be used via the "on device" UI, and which thus create barriers to access for the user due to missing features in the Web of Things implementation?

I would welcome comments on whether this statement of the problem makes good sense.

-----Original Message-----
From: Joshue O Connor <joconnor@w3.org>
Sent: Tuesday, July 9, 2019 11:32 AM
To: public-apa@w3.org
Cc: RQTF <public-rqtf@w3.org>
Subject: WoT Architecture Accessibility review notes

Hi all,

As promised as per my action 2198, here are my notes from my initial Web Of Things Architecture review. It poses questions relating to accessibility and the WoT space, that I hope we can discuss in APA, or in RQTF. [1] [2]

This isn't fully complete as I still have some more to complete, but hope to complete shortly and will update the doc as I go.

I hope this helps, and provides the basis for interesting discussion - all comments etc welcome.


[1] https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Fwiki%2FWoT_Architecture_review&amp;data=02%7C01%7Cjjwhite%40ets.org%7C1134968025f04157234a08d704826f8d%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636982830574437796&amp;sdata=li6ieuNcDBdv42T1vC3GF4ihwkJ%2BQN56KUsDLvgQ%2F%2BE%3D&amp;reserved=0

[2] https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Ftrack%2Factions%2F2198&amp;data=02%7C01%7Cjjwhite%40ets.org%7C1134968025f04157234a08d704826f8d%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636982830574437796&amp;sdata=PPa0wH%2FNz%2F81L321pzEWxNKIwtJifBiE4WMt1wn%2FMcU%3D&amp;reserved=0

Emerging Web Technology Specialist/A11y (WAI/W3C)


This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.

Thank you for your compliance.

Received on Tuesday, 9 July 2019 15:51:36 UTC

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