13:55:09 <RRSAgent> RRSAgent has joined #rqtf
13:55:09 <RRSAgent> logging to https://www.w3.org/2021/01/13-rqtf-irc
13:55:11 <trackbot> RRSAgent, make logs public
13:55:11 <Zakim> Zakim has joined #rqtf
13:55:13 <trackbot> Meeting: Accessible Platform Architectures Working Group Teleconference
13:55:13 <trackbot> Date: 13 January 2021
13:55:22 <jasonjgw> chair: jasonjgw
13:55:25 <jasonjgw> present+
13:55:30 <jasonjgw> agenda+        APA Working Group Charter development and the RQTF contribution.
13:55:30 <jasonjgw> agenda+        Status (and discussion, if needed): RTC Accessibility User requirements (RAUR) open issues.
13:55:33 <jasonjgw> agenda+        W3C Workshop on Wide Color Gamut and High Dynamic Range for the Web.
13:55:36 <jasonjgw> agenda+        MiniApp accessibility.
13:55:38 <jasonjgw> agenda+        Miscellaneous updates and topics relevant to Task Force work.
13:55:51 <jasonjgw> zakim, list agenda
13:55:51 <Zakim> I see 5 items remaining on the agenda:
13:55:52 <Zakim> 1. APA Working Group Charter development and the RQTF contribution. [from jasonjgw]
13:55:52 <Zakim> 2. Status (and discussion, if needed): RTC Accessibility User requirements (RAUR) open issues. [from jasonjgw]
13:55:52 <Zakim> 3. W3C Workshop on Wide Color Gamut and High Dynamic Range for the Web. [from jasonjgw]
13:55:52 <Zakim> 4. MiniApp accessibility. [from jasonjgw]
13:55:53 <Zakim> 5. Miscellaneous updates and topics relevant to Task Force work. [from jasonjgw]
13:59:39 <scott_h> scott_h has joined #rqtf
14:00:42 <SteveNoble> SteveNoble has joined #rqtf
14:01:06 <SteveNoble> present+
14:01:30 <scott_h> present+
14:01:42 <joconnor> present+
14:02:08 <SteveNoble> scribe: SteveNoble
14:02:13 <jasonjgw> zakim, next item
14:02:13 <Zakim> agendum 1 -- APA Working Group Charter development and the RQTF contribution. -- taken up [from jasonjgw]
14:02:52 <SteveNoble> Jason: potential meeting topics and deliverables for RQTF?
14:03:08 <becky> becky has joined #rqtf
14:03:58 <SteveNoble> Janina: we don't have to be overly precise in defining deliverables
14:04:34 <SteveNoble> Jason: using "such as" language would be appropriate
14:05:35 <SteveNoble> Jason: one item of late was revisiting the MAUR, as well as machine learning
14:07:27 <SteveNoble> Scott: one topic - parts of physical devices like TVs that have interfaces with varying degrees of accessibility
14:08:08 <SteveNoble> Janina: some discussion in Silver around web of things, so that might be a connection
14:09:25 <SteveNoble> Janina: one issue is when software that run these devices break down and the accessibility infrastructure stops working
14:10:51 <SteveNoble> Scott: guidance for "good" accessibility implementation in devices? Some parts of these work well, while other aspects may sometimes not be accessible
14:11:24 <SteveNoble> Scott: like changing the input from HDMI to something else
14:12:21 <SteveNoble> Scott: how we could reference the work of Mobile or Silver
14:14:10 <SteveNoble> Janina: really hard for a consumer to know what elements in a device are accessible before purchasing
14:15:23 <SteveNoble> Jason: European Accessibility Act may be something to consider for device accessibility
14:18:18 <SteveNoble> Jason: Web of Things discussion coming up in two weeks - may be a good time to discuss these issues initially
14:19:46 <SteveNoble> Janina: casting to other devices is a good area to consider because lots of people without disabilities use this, so it has wide interest in the community
14:21:56 <SteveNoble> Josh: including some specifics in a charter is good, but there is a good balance
14:24:45 <SteveNoble> Judy: Increasing usage of machine learning for automating a number of accessibility linkages is something to keep in mind
14:26:13 <SteveNoble> Janina: if you identify the knowledge domain, this helps the machine learning process to be more successful
14:27:22 <SteveNoble> Jason: understanding what metadata is vital for the content creator is important so that the efforts of humans is put to the best efforts
14:30:02 <SteveNoble> Janina: right now just work on the charter in github
14:31:06 <jasonjgw> https://raw.githack.com/w3c/apa/charter-2021/charter.html
14:34:50 <jasonjgw> zakim, next item
14:34:50 <Zakim> agendum 2 -- Status (and discussion, if needed): RTC Accessibility User requirements (RAUR) open issues. -- taken up [from jasonjgw]
14:37:00 <joconnor> TOPIC: [ITU-T] 2.1 Incoming calls and caller ID #121
14:37:06 <joconnor> https://github.com/w3c/apa/issues/121
14:38:04 <SteveNoble> Josh: relates to caller ID - can we indicate that a relay call is coming in?
14:40:26 <SteveNoble> Jason: indicating the identity of the caller seems the highest need
14:42:37 <SteveNoble> Janina: it seems knowing the original caller on the other end (not just the relay service) seems the greatest need
14:43:34 <SteveNoble> Jason: knowing both pieces of information at the same time
14:45:07 <SteveNoble> Josh: could expand this my user need
14:54:51 <joconnor> Steve: From outside an a11y perspective, one of the things we need is for call forwarding.
14:55:04 <joconnor> What phone they are dialling into.
14:55:25 <joconnor> You may be working from home, an capture calls
14:55:56 <joconnor> When calls are forwarded I can choose.
14:56:04 <joconnor> Mainstream need.
15:01:52 <SteveNoble> Need to figure out the core user need on this
15:03:08 <janina> janina has left #rqtf
15:03:16 <jasonjgw> zakim, bye
15:03:16 <Zakim> leaving.  As of this point the attendees have been jasonjgw, SteveNoble, scott_h, joconnor
15:03:16 <Zakim> Zakim has left #rqtf
15:03:25 <jasonjgw> rrsagent, make minutes
15:03:25 <RRSAgent> I have made the request to generate https://www.w3.org/2021/01/13-rqtf-minutes.html jasonjgw
17:01:37 <becky> becky has joined #rqtf