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

Re: Position Statement re Accessibility

From: Janina Sajka <janina@rednote.net>
Date: Tue, 9 Jul 2019 05:21:37 -0400
To: Léonie Watson <lw@tetralogical.com>
Cc: W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Message-ID: <20190709092137.GJ1832@rednote.net>
Thanks, Leonie. These are all good points to be taken into

At this point I think the best contribution to the workshop is to
introduce the notion that users will need personalized guidance when a
delivery robot rings the doorbell. There's certainly need for
elaboration, as you suggest. And, we haven't even started on the "Sign
here" part!


Léonie Watson writes:
> I haven't been following this thread, so don't have the background knowledge
> to comment widely, but I wanted to comment on one part of your text Janina:
> "*	Similarly, robotically delivered parcels will need to guide
> *	blind customers to the retrieval of their goods, e.g. "beep
> *	beep, your pizza is here," i.e. at the locus of a sonic alert."
> It strikes me that this could leave people vulnerable to having their
> packages stolen by opportunist thieves who heard the "Your pizza is over
> here" message being played.
> I also wonder how people living in close proximity might manage the
> possibility of multiple parcels being delivered at the same time, and being
> able to tell theirs apart from their close neighbours.
> Lastly, there is the noise pollution thing. What if you're not in all day
> and your parcel is burbling away to itself all day to the annoyance of
> people nearby.
> I don't know anything much about the security of parcels delivered in this
> way, the mechanisms by which theft is prevented, messages might be triggered
> etc. but thought it worth mentioning.
> One possibility might be for the customer to be able to select a noise/sound
> that is unique to them, to be able to trigger the alert at a time convenient
> to them, and perhaps for the alert only to be given via an app or other
> device (though this reduces the efficacy of the location of course).
> Léonie.
> On 09/07/2019 03:24, Janina Sajka wrote:
> > Colleagues:
> > 
> > A brief statement follows. The statement reflects my personal views on
> > the topic. Although we have discussed these views on the APA email list,
> > we have not yet formally adopted this statement as an APA consensus
> > view. However, we are considering doing so. Should we take that action,
> > I will update accordingly.
> > 
> > 
> > Cut Here ...
> > 
> > ***One Size Can't Fit All***
> > 
> > Supporting the accessibility needs of persons with disabilities in our
> > emerging transportation industry will require personalized adaptation in
> > service delivery. Because the user can't change, the industry must adapt
> > its data modelsto accomodate the varying requirements of different
> > users.
> > 
> > We note this requirement requires strong privacy protections because the
> > user is voluntarily disclosing data about themselves they would prefer
> > not to broadcast to any and all eavesdroppers. It is well known that
> > users who are persons with disabilities will disclose the nature of
> > their disability to a service providing goods or services of particular
> > value. However, this cannot be seen as license to leverage that
> > information by selling or otherwise exposing that data to third parties.
> > 
> > We would characterize this data modeling requirement as personalizable
> > onboarding/offboarding support.  Here are a few examples to illustrate this
> > requirement:
> > 
> > *	Some transport customers will require wheel chair accessible vehicles.
> > 	Others may only need to store their chairs securely before occupying a
> > standard passenger seat. It must be possible to order up a wheelchair
> > accomodating vehicle through the standard requisitioning process,
> > whether by the ride or by a calendar interval. It must be possible to do
> > so without requiring the user to provide this nonvarying data point with
> > each request regardless the local language.
> > 
> > *	Persons using wheelchairs have a very strong requirement to be
> > *	delivered to a location which allows them to proceed in their
> > *	wheelchairs. This is often not the front entrance to a large
> > *	facility such as a train station. It may even be a location
> > *	inside a secured facility such as a sensitive research campus.
> > *	Think the National Institutes of Health (NIH) or the National
> > *	Institue of Standards and Technology (NIST) in Montgomery
> > *	County, Maryland in the U.S. In many cases this accessible
> > *	offboarding will require communication to the appropriate
> > *	officers at the destination facility so that the customer
> > *	needing assistance can be met and assisted personally when the
> > *	vehicle arrives.
> > 
> > *	The industry already has rudimentary awareness of its onboarding responsibilities	in that they typically provide a photo and the
> > *	license plate designation of the requisitioned vehicle to the
> > *	ordering customer for reasons of security. However, blind
> > *	customers aren't served by license plate numbers and transmitted
> > 	photos of their drivers. Rather, they need the driver (or
> > 	vehicle) to identify themselves upon arrival. In the
> > 	circumstance of a customer who is blind, it's the user's name
> > 	and photo which should be transmitted to the vehicle driver with
> > 	a note reminding the driver that it's their responsibility to
> > 	identify themselves as the driver of the requisitioned vehicle
> > 	and to guide the individual to the vehicle. Furthermore, we
> > 	likely need a mechanism for a vehicle to identify itself upon
> > 	arrival to the user's smart device. Various strategies for
> > 	disambiguating which vehicle is intended for whom will be
> > 	particularly important in high traffic areas such as airports.
> > 
> > *	Similarly, robotically delivered parcels will need to guide
> > *	blind customers to the retrieval of their goods, e.g. "beep
> > *	beep, your pizza is here," i.e. at the locus of a sonic alert.
> > *	The data model should support visual and sonic alerts on a per
> > *	user need basis.
> > 
> > *	App based transport services today provide a compelling payment
> > 	mechanism that avoids requiring the international traveler to possess
> > and exchange foreign currencies. However, they also need to facilitate foreign
> > language communication of key personal data, e.g. how do I tell my Uber
> > driver: "I'm blind, so you need to see me and identify yourself to me as I
> > won't be seeing you when you arrive?" What's the word for "blind" in Chinese?
> > French? Etc? And, why should I have to learn it when the app can
> > communicate my critical factors on my behalf?
> > 
> > ***Internal Systems Assistive Technology Support***
> > Systems internal to any vehicle should interface readily with any
> > customer's personal devices, including their assistive technologies.
> > This clearly includes on board entertainment, but also command and
> > control of any autonomous vehicle to the full extent that vehicle is
> > autonomous, whether it's an automobile or a private jet.
> > 
> -- 
> @TetraLogical TetraLogical.com


Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Tuesday, 9 July 2019 09:22:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:55:34 UTC