In-Vehicle Best Practices

[Introductions]

Ted summarizes activitity, best practices effort and a11y conversations last time

https://www.w3.org/community/autowebplatform/wiki/Best_Practices#Accessibility_.28A11y.29

Josh: this seems like a good area to create needs and requirements
… . glad to hear privacy conseriderations part of this

Ulf: for the next version of VISS, it might be late to introduce accessibility capabilities but certainly in subsequent

https://raw.githack.com/w3c/automotive/gh-pages/spec/VISSv2_Core.html

<bruce_bailey> Recent U.S. Access Board forum series archive is here:

https://raw.githack.com/w3c/automotive/gh-pages/spec/VISSv2_Transport.html

<bruce_bailey> https://www.access-board.gov/av

Bruce: ability to bring your own device is key
… you would expect end users to have a device that is trusted by the vehile. security issues are pretty profound, the car might have too much sensitive information about them

Josh: privacy of individuals' data is critically important as is providing what is useful for accomodations to be made

<Joshue108> https://www.w3.org/TR/did-core/

<Joshue108> https://www.w3.org/2017/05/vc-data-model/CGFR/2017-05-01/

Josh: there are a couple specs that may be useful, one is DID and another is verifiable claims as ways to anonymize data while being sure of its integrity

proxy_re_encyption:
* explanatory resources
* conditional scenario
* minutes 2021-01-12
* minutes 2021-01-25

<Zakim> bruce_bailey, you wanted to give another example

Bruce: AV is outside domain of Access Board, we do regulatory work around ADA, right of way, rails but personal vehicles are outside our scope - Section 508
… there are some resources linked before on presentations, recordings and soon summaries
… if a car is at speed, door should stay locked. what about at a stop light? if person has alzheimer's, maybe keep it locked. sometimes you want more restrictions

Josh: DID is a way of providing a node or data point which could contain needs for an individual but without giving away too much, disposable information even
… it works with verifiable claims to attest to the assertion made
… we want to enable IT systems to adapt to needs but want to avoid risk of misuse of that data

<bruce_bailey> Our purview is also Section 508 of the Rehabilitation Act

<bruce_bailey> https://www.access-board.gov/ict

Ted wonders about regulatory route on open api for a11y and bring your own device, use of data?

Bruce: yes but you can also pressure them via moral influences
… 508 is flexible and can be used for opening conversations. Fed gov didn't mandate making accessible software but would have that requirement for software the governement uses
… the power of the purse, why would you want two variations or products. same thing could happen with AV. you're right it is a large, untapped market

Bruce: re adaptive controls, that really something we should enable?

Ted: standard used more for informational purposes than to control vehicle, you want better integration and understand what Uber & Volvo did was using our standard more for machine learning
… GENIVI and W3C are seeking to push some aspects of our standards down the stack toward the underlying control units. Under very controlled, well authenticated scenarios with trusted devices within a vehicle, could see the type of integration we are talking about

Gunnar: agree it could be feasible and worthwhile