Meeting minutes
RTC Accessibility User Requirements (RAUR) open issues.
josh: starting to work through RAUR issues
NEW Use Case Pinning audio output #118
<joconnor> https://
josh: new use case for pinning audio output
josh: mutkple use cases fo rpinning something, different items for different TTS/audio items
janina: does that make sense?
jjason: direct to channels via shortcut key
<joconnor> There may be a broader issue around the use of the term pinning
<joconnor> is it relevant for this case?
janina: eg pinning parts of screen to braille display
<joconnor> SH: It makes sense to me.
scott: makes sense o tme
<Zakim> joconnor, you wanted to say it could be a useful catch all
josh: good t ohave catch-all term, pinning = sticking something on screen, whatever that is
janina: eg who's speaking, what message came up in chat,
josh: good to define that
use cases: audio, Brialle,
jason: status messages
e.g. who jsut arrive din ameeting, conveyed via status message
josh: issue of atomic intersting - audio, brialle, routing options
josh: we also have teh generic use case of routing tihngs in RAUR< cross-link
josh: currently have window anchoring/pinning,
three requirements: ability to pin (sign language/interpreter), flexible pnnning of captions, e.g. second screen rdevices
differential is the atomic idea
janina: yes, all from WCAG ACT, atomic tests.
Zoom have variet of views constructed on-the-fly.
josh: so need to add atomic and current pices of data: who's speaking, lat message, etc to pin that as new requirement
added to first one - 1(d) ensure that atomic pieces of date
in relaiton to who is speaking, last message was, can be pinned in user interface
janina: given we're using both ZOom and IRC, may need two sign language - multiple streams requriements?
judy: have been in meetings with 3,4 speech interpreters - not speculative
josh: yes e.g. ISL and BSL
<janina> https://
josh: have new text, updated
WebRTC needs mechanism to handle the metadata needed to re-aggregate Pinned audio content #119
<joconnor> https://
jason: complicated that some devices can come and go, display could all happen in midst of a session
josh: mentioned that if we have mutliple atomic data points for Braille spacing
didn't know you could break up Brialle dispaly - great example
jason: there are status cells, ways to put different informationin
janin: yes, but can you update cells some cells without others?
jason: yes, but the user wouldn't know
<joconnor> JOC: Adding a reference to sending atomic content to different sections of the braille display would be helpful to readers to understand the user need for atomic output
josh: back to the point on referring functionality within Brialle output - would help RAUR readers understanding atomic
janina: not much difference from a tabular display: file, size, etc.
josh: yes, but not common knowledge
<joconnor> JOC: Can you route live region output to different sections of a braille display?
<joconnor> JS: Not yet
jason: complicated when there is mutliple channels of information coming in and only one channel output
janina makes point that ARIA is about screen readers and speech, not screen readers and Brialle
jasoN: how's it looking regading this issue?
josh: still need to address what metadata means in this context
josh: making the point that atomic items may not be pinned next ot each other, but may have relationship
how do we capture dependencies/mechanisms?
janina: let the user deifne that?
jason: this paragraph/seciton will need some work, need discusson on github or list
josh: agreed, will come back with suggestions
Future Task Force publication opportunities and the APA Working Group Charter proposal.
jason: the APA working group is preparaing proposal for new charter,
need to include deliverables inlcuding non-normative Note track
need to discuss with APA before end of month
janina: would like to send new charter end Jan/early Feb
how to discuss our work in a proposed charter
judy: good to be specificlly on technical reports that RQTF publishing through APA
however RQTF is also exploratory
RQTF was taken from a preexisitng working group, restrctivie to take research questions - new area that needs deeper dive
RQTF doing well - good to take a fresh look
jason: will discuss what we want ot work on
has been some discussion on MAUR as revision opportunity
are there other things?
janina: think about that and start next week
need scope to explore - eg new things to add to RAUR
can also point to work done eg CAPTCHA
judy: also consider focus on scope with more flexible deliverables