Meeting minutes
APA Working Group Charter development and the RQTF contribution.
Jason: potential meeting topics and deliverables for RQTF?
Janina: we don't have to be overly precise in defining deliverables
Jason: using "such as" language would be appropriate
Jason: one item of late was revisiting the MAUR, as well as machine learning
Scott: one topic - parts of physical devices like TVs that have interfaces with varying degrees of accessibility
Janina: some discussion in Silver around web of things, so that might be a connection
Janina: one issue is when software that run these devices break down and the accessibility infrastructure stops working
Scott: guidance for "good" accessibility implementation in devices? Some parts of these work well, while other aspects may sometimes not be accessible
Scott: like changing the input from HDMI to something else
Scott: how we could reference the work of Mobile or Silver
Janina: really hard for a consumer to know what elements in a device are accessible before purchasing
Jason: European Accessibility Act may be something to consider for device accessibility
Jason: Web of Things discussion coming up in two weeks - may be a good time to discuss these issues initially
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
Josh: including some specifics in a charter is good, but there is a good balance
Judy: Increasing usage of machine learning for automating a number of accessibility linkages is something to keep in mind
Janina: if you identify the knowledge domain, this helps the machine learning process to be more successful
Jason: understanding what metadata is vital for the content creator is important so that the efforts of humans is put to the best efforts
Janina: right now just work on the charter in github
<jasonjgw> https://
Status (and discussion, if needed): RTC Accessibility User requirements (RAUR) open issues.
[ITU-T] 2.1 Incoming calls and caller ID #121
<joconnor> https://
Josh: relates to caller ID - can we indicate that a relay call is coming in?
Jason: indicating the identity of the caller seems the highest need
Janina: it seems knowing the original caller on the other end (not just the relay service) seems the greatest need
Jason: knowing both pieces of information at the same time
Josh: could expand this my user need
<joconnor> Steve: From outside an a11y perspective, one of the things we need is for call forwarding.
<joconnor> What phone they are dialling into.
<joconnor> You may be working from home, an capture calls
<joconnor> When calls are forwarded I can choose.
<joconnor> Mainstream need.
Need to figure out the core user need on this