W3C

– DRAFT –
Accessible Platform Architectures Working Group Teleconference

21 April 2021

Attendees

Present
janina, jasonjgw, joconnor, John_Paton, Judy, SteveNoble
Regrets
-
Chair
jasonjgw
Scribe
JPaton

Meeting minutes

RAUR: open issues.

jasonjgw: Josh has narrowed down to the questions that need discussion.

joconnor: many of the suggestions from Gunnar are editorial and have been folded into main.

<SteveNoble> I am on the call now...sorry that I was delayed

<joconnor> #161 https://github.com/w3c/apa/issues/161 13.16 "IRC style - describe requirement rather than referring to IRC"

Judy: Met with immersive Captions community group to talk about work of RTQF are would

Judy: some members of that group were interested in coming to this group to understand the work.

joconnor: IRC may soon be forgotten as a service (so IRC-style may become outdated terminology)

<joconnor> notes: that the IRC being forgotten is Gunnars opinion

joconnor: Gunnar states that a definition of IRC-style is needed and offers a definition

janina: disagree that IRC is going anywhere

<joconnor> We can leave this - we should be adding the ability to buffer for speech to expand and contract correctly.

<joconnor> We may need a cross reference to latency and supporting messaging.

<joconnor> http://raw.githack.com/w3c/apa/main/raur/index.html#internet-relay-chat-irc-style-interfaces-required-by-blind-users

<joconnor> Pull the text 'required by blind users'...

<joconnor> in User Need 18 - to expand it for different groups.

joconnor: Some user requirements work for several demographics so removing explicit reference to user groups may help

<joconnor> #175 https://github.com/w3c/apa/issues/175 Encryption support references

joconnor: we may need to tighten the reference for encryption support

janina: security and privacy are out of scope for this group

janina: out of scope topics are better handled by other w3c teams

jasonjgw: Don't want users to become more vulnerable attacks because they're using a relay service

<joconnor> Josh to take out references to encryption support

joconnor: this was already covered by the original text but I added some extra reference to encryption support which I'll take out again

joconnor: I created a new req: ensure webrtc can connect to video relay services

<joconnor> Draft req for WebRTC to connect to PSTN ?

<joconnor> SIP can use RTT, and be connected by appropriate gateway

<joconnor> JP: SIP can be the text and the Voice

<joconnor> I'm not clear on the user requirement is

<joconnor> <discusses options>

<joconnor> JS: <May not be relevant>

<joconnor> JS: We are talking about a WebRTC service

<joconnor> JS: This doesn't happen in the US

<joconnor> JP: <describes UK situation>

<joconnor> JP: There is not an app that allows text and voice at the same time.

<joconnor> I'm not sure if it allows video relay or not

<joconnor> There used to be no funding for this service

<joconnor> people had to have their own connection to video service

<joconnor> http://raw.githack.com/w3c/apa/main/raur/index.html#video-relay-services-vrs-and-remote-interpretation-vri

<joconnor> SUggested changes from COGA

<joconnor> http://raw.githack.com/w3c/apa/COGA-feedback-Apr-2021/raur/index.html

joconnor: routing and comm channel control seemed minor

joconnor: users with cognitive needs may need assistance when using audio or video

janina: "Assistance" needs to be expanded before we can specify what changes need to be made to systems and services.

<janina> https://docs.google.com/document/d/19-aB1v8f9BGNeSoedbFrn2HgxR4TDpSpeu7NHm8YO_g/edit?usp=sharing

Minutes manually created (not a transcript), formatted by scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).