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

Re: W3C Workshop: Transportation Data Models -- Due Monday

From: Janina Sajka <janina@rednote.net>
Date: Wed, 3 Jul 2019 10:06:17 -0400
To: Becky Gibson <becky@knowbility.org>
Cc: W3C WAI Accessible Platform Architectures <public-apa@w3.org>, public-rqtf@w3.org
Message-ID: <20190703140617.GB1832@rednote.net>
Hi, Becky:

All good points, but the Workshop wants the focus on ontology. So, it's
an emphasis on the what, not the how.

Still, what should include a presentation that can be auto adapted for
user needs, imo. Will add that and get another draft up later.

Janina

Becky Gibson writes:
> Janina, this is great. Just a few quick, additional thoughts.  I’ll ponder more during the day.
> 
> Should we mention accessibility of transport apps?  This is covered under WCAG but might be good to call out that any transport related apps should work with assistive technologies - screen reader, voice, magnification, enlarged fonts, etc. 
> Autonomous vehicles must also support assistive technologies and alternative interfaces.
> 
> We should probably expand to include low vision in addition to blind customers as those folks may have some of the same difficulties identifying the driver, car, or package.
> 
> -becky
> 
> > On Jul 3, 2019, at 8:43 AM, Janina Sajka <janina@rednote.net> wrote:
> > 
> > Colleagues:
> > 
> > It's heartening to see accessibility requirements specifically called
> > out in the Workshop announcement for this upcoming event in California
> > this coming September. However, since the deadline for submissions is
> > this coming Monday 8 July, I'd like to consider what our position
> > submission might say on list. A draft follows. Please help improve this
> > very quick and dirty start!
> > 
> > We will take up the issue of who might be able to attend and speak on
> > behalf of accessibility in the days that follow.
> > 
> > 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.
> > 
> > Some examples illustrate this point:
> > 
> > *	Some transport customers will require wheel chair accessible vehicles.
> > 	Others may only need to store their chairs securely before occupying a
> > standard passenger seat.
> > 
> > *	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. Perhaps, in this circumstance, it's the
> > user's photo which should be transmitted? Similarly, robotically delivered
> > parcels will need to guide blind customers to the retrieval of their goods,
> > e.g. "beep beep, your pizza is here."
> > 
> > *	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?
> > 
> > 
> > -- 
> > 
> > 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
> > 
> > 
> 

-- 

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 Wednesday, 3 July 2019 14:06:44 UTC

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