14:07:43 RRSAgent has joined #private-a11y 14:07:43 logging to https://www.w3.org/2022/09/14-private-a11y-irc 14:07:45 Zakim has joined #private-a11y 14:12:36 Meeting: Architecting for Privacy, Media Accessibility and Product development: the video element - TPAC 2022 breakout 14:12:39 Chair: Nigel_Megitt 14:12:41 Agenda: https://www.w3.org/events/meetings/8aca01fe-feb7-4cde-9837-6dcd126a27ac#agenda 14:12:45 RRSAgent, make log public 14:12:47 RRSAgent, this meeting spans midnight 14:18:08 RRSAgent, stay 14:18:10 Zakim, stay 14:18:10 I don't understand 'stay', dom 15:14:58 dom has joined #private-a11y 15:51:45 englishm has joined #private-a11y 16:12:55 agenda+ breakout 18:15:49 dom has joined #private-a11y 20:15:05 dom has joined #private-a11y 20:26:12 Massa has joined #private-a11y 20:29:03 Wilco has joined #private-a11y 20:29:27 nigel has joined #private-a11y 20:30:10 dom has joined #private-a11y 20:30:35 gkatsev has joined #private-a11y 20:32:25 gendler has joined #private-a11y 20:32:36 Ben_Tillyer has joined #private-a11y 20:32:39 present+ 20:32:42 present+ 20:32:43 Meeting: Architecting for Privacy, Media Accessibility and Product development: the video element 20:32:48 Present+ Nigel_Megitt 20:32:57 Present+ Gary_Katsevman 20:34:09 atai has joined #private-a11y 20:34:31 mateus has joined #private-a11y 20:34:57 cyril has joined #private-a11y 20:35:34 gpellegrino has joined #private-a11y 20:35:34 present+ 20:35:36 wendyreid has joined #private-a11y 20:35:38 present+ 20:35:41 present+ 20:35:55 ShawnT has joined #private-a11y 20:36:00 present+ 20:36:00 present+ 20:36:09 scribe+ 20:36:43 nigel: Summary for this is to think about architectural models for maintaining privacy in accessibility 20:36:49 mbgower has joined #private-a11y 20:36:51 ... referncing the video element in particular 20:37:01 ... allow user choices without fingerprinting 20:37:01 present+ 20:37:26 ... context, people with barriers to access need to adjust display settings 20:37:39 ... the lack of consistency in how those settings are done is a problem in itself 20:37:49 ... user settings made portable between systems 20:37:57 ... ITU is working on this, as part of the UN 20:38:07 ... ???? group 20:38:14 ... working on the common user profile 20:38:37 ... in the US the FCC has the CTA, working on something similar to allow users to set their preferences for media 20:38:48 ... a standard format document made available to apps, websites, etc 20:38:53 ... the user can edit and share it 20:39:06 ... and different settings for different scenarios, like screen size or type 20:39:14 ... which is very powerful, but there is risk 20:39:26 ... the document has high entropy, user fingerprinting is very possible 20:39:34 ... privacy is a concern 20:39:48 ... to meet user needs, product developers must suit their output to the user needs 20:40:00 ... they have a legitimate need to know how users use the features 20:40:17 ... knowing data like how people prefer captions would help with product decisions 20:40:34 ... it's difficult to polyfill things on areas like the video element 20:41:09 ... how can we improve accessibility while also ensuring privacy, and the communication of user needs to product developers 20:41:15 ... mentioning the video element 20:41:21 ... key features 20:41:30 ... video does not take child elements 20:41:48 ... it's a shadow host, but cannot have a shadow tree attached 20:42:00 ... there is no parent-child layout 20:42:14 ... try to put content on top of the video 20:42:20 ... it's clunky if not impossible 20:42:39 ... you need to create sibling or related elements and make them work together through CSS 20:42:47 s/???? group/Intersector Rapporteur Group Audiovisual Media Accessibility 20:42:51 ... ever tried tracking the video as the page changes? 20:43:21 nigel: no general purpose polyfills 20:43:37 ... that tracks data and uses it, but it's difficult 20:43:47 ... you still cannot access the user accessibility settings 20:44:21 ... the only way to see things, you can access through captions in VTT, entry and exit handlers 20:44:30 ... good for privacy but difficult for product improvement 20:44:49 ... two choices, children with VTT captions and browser renders 20:45:05 cyns has joined #private-a11y 20:45:08 ... any default styling is possibly overridden or tweaked 20:45:45 ... option 2, create a separate container element and render captions, use CSS to colocate, customisation is whatever the page offers 20:45:45 jcraig has joined #private-a11y 20:45:49 ... you can get data 20:46:00 ... but no relationship to existing accessibility preferences. 20:46:14 ... tension between user and product owner needs, but there is no real tension 20:46:17 ... so end goal 20:46:23 s/so/same/ 20:46:32 nigel: Here are my ideas 20:46:49 ... allow the