17:06:35 RRSAgent has joined #auto 17:06:35 logging to https://www.w3.org/2021/09/20-auto-irc 17:06:37 RRSAgent, make logs Public 17:06:38 Meeting: Automotive Working Group Teleconference 17:06:43 Meeting: In-Vehicle Best Practices 17:06:54 Present+ Randall, Ashish, MagnusG, Ted 17:07:01 Topic: Introductions 17:07:03 https://www.w3.org/community/autowebplatform/wiki/Best_Practices#Accessibility_.28A11y.29 17:16:24 Ted introduces scope and intersection of A11y and Privacy 17:16:42 Randall: we should maybe focus more on features instead of users and needs 17:17:15 … eg share my photo with the rideshare driver instead of providing health related information (eg visually impaired) 17:18:15 … there are a number of things that can be toggled under smartphones for example. using a feature doesn't mean you have a specific need 17:19:09 Ted: for visually impaired rider for example, share photo with driver and have them look for me 17:19:21 Randall: also unwilling to cross the street 17:22:00 Ted: @@ADA - more an education for drivers 17:22:33 Randall: for the law to work, you need to say what your need is without disclosing specific disability 17:22:40 … a single bit could provide the legal protection 17:23:08 Magnus: from a Swedish point of view we have laws that prohibit discrimination based on disability 17:23:44 Randall: that is suppose to be the case here (US) as well 17:26:43 [tangent on website a11y, stronger requirements if store/entity physically exist] 17:27:47 Randall: case laws are always being challenged. back to person wanting to be picked up, again want to go feature approach 17:29:01 Ashish: a11y is not something I am very familiar with but isn't providing information on features revealing individual's disability 17:29:33 Randall: not necessarily, you may want a ramp for a stroller or groceries as a convenience 17:33:17 Ashish: what if every individual needs to set a certain number of features/preferences which would obfuscate a11y need 17:38:08 Randall: still have pickup being dismissed is a concern 17:38:21 … should be addressed through training 17:38:50 Ted: @@want harsh ADA reminder with potential fines if any features are requested and driver tries to dismiss 17:39:32 Randall: @@scope of standards 17:40:27 Ted: @@capabilites of vehicle, pairing of device for alternate interface 17:44:45 Randall: I can see this being useful for SAE, working on a roadmap with them on different standards and developing them 17:45:05 … being able to point them to W3C documents would be helpful 17:45:45 … curious about Mitsubishi's direction, if they are moving to Android or other OS with a11y features built in for their head unit? 17:46:15 … much of what is already in WCAG is addressed in them 17:47:49 … example is vehicle distance in adaptive cruise control or adherence to speed limit to address anxiety concerns 17:48:12 Magnus: we are moving to Android indeed 17:48:26 … from a Tier 1 perspective, we deliver what the customer (OEM) wants 17:48:45 … we do have many sensors or capabilities we want to encourage/push to customers 17:49:10 … not aware of any that address a11y other than system UI. that is limited to sound, speech input, etc 17:49:35 Randall: do you know if any of the Andoid a11y features such as large text are preserved? 17:49:57 Magnus: not sure with Android, on our earlier Window's development it was based on requests from OEM designers 17:50:22 … the Windows system that is phasing out it was usually disabled 17:50:37 Randall: that is unfortunate 17:51:17 Magnus: Windows automotive was very different than their OS for a laptop, also very old at this point 17:52:10 … do you have any contact with Google? in order to use AA you need to comply with various requirements, not sure this is occuring or a point they require for using AA 17:54:04 [discussion on how to get intros and follow up on this topic] 17:54:19 Randall encourages people to try out the a11y features in Android phones 17:55:32 Magnus: seems to me, especially for AV you need a better means of pushing information to individuals besides just the driver 17:56:09 Randall: unsure if you saw news of a Toyota AV hitting a blind pedestrian during the paralympics... 17:56:34 … vehicle needs to be able to identify a11y needs of not only passengers but pedestrians 17:57:01 … however at this point we get into collecting personal, sensitive data 17:57:25 Ted: never succeeded in getting a formal with SAE and W3C 18:03:18 … joined from my current employer and very interested in being part of that upcoming conversation with them and can help connect them 18:05:03 I have made the request to generate https://www.w3.org/2021/09/20-auto-minutes.html ted 18:06:06 s/@@want harsh/people ignore or forget training so I want a harsh/ 18:06:41 s/@@scope of standards/what is the scope of the standards being worked on, how much may they be influencing AV?/ 18:08:40 s/@@capabilites of vehicle, pairing of device for alternate interface/primary focus is on static and dynamic data from the vehicle, could include capabilities such as lift, ramp and be used for alternate interfaces and paired devices for some vehicle-human interaction. I know it was used for a prominent ride hailing & OEM collaboration for AV/ 18:08:43 I have made the request to generate https://www.w3.org/2021/09/20-auto-minutes.html ted 18:09:39 s/@@ADA/I guess ADA aspects can be addressed through better training of ride hail service drivers/ 18:09:46 I have made the request to generate https://www.w3.org/2021/09/20-auto-minutes.html ted