<Judy> [JB sends partial regrets as she is held over in another meeting, will join as soon as able]

RTC Accessibility User requirements (RAUR) open issues.

<scribe> scribe: SteveNoble

Josh: working draft of RAUR has been updated

<joconnor> https://www.w3.org/TR/raur/

<joconnor> Updated working draft

issue 111

EQ adjustment for the end user

Janina: example of apps that reduce background noise
... the ability to use binaural sound to increase comprehension

Josh: the ability for the user to independently adjust audio characteristics

issue 112

Josh: substitue "any user"

issue 113

POTS availability going away "plain old telephone service"

Josh: not sure if this document is the place for this discussion

Janina: perhaps identify the issue as jurisdictional

issue 114

Josh: will leave open for now

issue 115

can close

issue 116

<joconnor> ITU-T Overview of Remote Captioning services https://www.itu.int/pub/T-TUT-FSTP-2019-ACC.RCS

Issue of sensitive data and security for captions

Potential privacy issue - use of encryption?

<joconnor> https://github.com/w3c/apa/issues/116

<joconnor> Are there security and privacy issues around remotely captioned content or other alternate formats?

Judy: one question is the extent to which technology can support these considerations

<Judy> [JB: this might parallel what happens in the telehealth field, for instance such as the US "HIPAA Certification" https://www.hipaacertification.net/

Josh: what we could do is suggest that communication channels that have privacy policies also be applied to alternative access

Janina: off-minutes captioning...can this be done?

Flag to treat alternative access text as first-class content

Josh: will put something together to address this expectation

issue 117

Commenter about limitation mostly to ASL, suggesting more general language

Josh will make the change

issue 118

pinning content output to different channels or hardware devices

Janina: may also require support from an RTC API

Josh: will need to come back to this for more clarity

Consensus to not meet again until the new year

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/HIPPA/HIPAA/
Default Present: jasonjgw, janina, SteveNoble, scott_h, JPaton_, joconnor
Present: jasonjgw janina SteveNoble scott_h JPaton_ joconnor
Found Scribe: SteveNoble
Inferring ScribeNick: SteveNoble
Found Date: 09 Dec 2020
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)