<scott_h> I'm trying ot join Zoom and have entered meeting iD but it keeps asking for password. Does anyone know password?
<jasonjgw> I've found the password and sent details by email to everyone. Please keep the password strictly confidential.
<janina> Hello, do we have a passwd? Can you /me it?
<scott_h> scribe: scott_h
remote meetings; more real-time, more urgent
wokrignwith some colleages and classes: how to get deaf students onlne
thought deaf community in some countries relied on video conferencing tools,
but not necessarily in these tools and in large classroom settings
Getting quesitons like 'how can I pin multiple windows in zoom call?'
emersive captiosn community group: all use zoom
and multipel differnet interpreters
we have content, presenters, pinned
May need to link out to accessibility info facts on a per-tool basis
but also have a generic seciton
I think we're missing section: how ot deal wiht kids of qudsitons
jason: also rasies quesitons for me,
how would multiple windows work and how webRTC would support it
does video informaiton get combined?
not sure if it all gets mixed in like audio or sent out as seprate streams that client can direct and what are the technical requirements
i.e. RAUR draft
<jasonjgw> Scott: still intends to add education-related material to the wiki, including LMS integration.
<jasonjgw> Scott notes that some LMS platforms have specific tools designed to make content accessible. He considers references to those would be useful.
scott: in the educaiton space, lots of differences in accessiiblity between LMS platforms
e.g. Blackboard Ultra, Moodle, Canvas
would be good to ahve both generic and tool-speicifc guidance
jason: at least knowing what htey are and links to tehir accessibilty pages woudl be good
judy: yes, can look at generic feature set wish list and list features of tools
the most requested feature is pinning of windows.
<Joshue108> That is a good use case
josh: use case on pinning windows is useful
UI guidance, RTC guidance, WCAG?
judy: needs to be a user tips section
planning to add
<Joshue108> Sounds good.
and continuing ot think of this doucment has havng auidence
where users want to know what feature allows you to od things,
while other parts with developers focus on htese features should be there
No reelvant part of UAAG
janina: who benefits?
judy: someone who is deaf
janina: capture this in RTC doc?
josh: yes, great use case
<Joshue108> scribenick: Joshue108
<jasonjgw> Josh: RAUR could be an appropirate place for it. It's a UI feature, but it may need browser support.
JS: <gives overview of the need to switch devices etc>
JOC: Like a profile thing to transport accross devices.
JS: Yes.
Interoperability.
JOC: I suggest adding Judys use case to the Accessibility of Remote Meetings doc first.
JW: So we could map the RAUR use cases to where they need to be addressed.
JOC: We just need to define the use case primarily.
JS: +1
JOC: It would be best if Judy drafts this there.
Then we can review and refine, and schedule it for RAUR update.
JS: Sounds good
JW: The scenario relates to multiple sign-language interpreters etc and the party that was speaking.
JS: Sounds like sub use
case.
... That where is starts, we also have captioning.
<Judy> [JB: clarifies that the core case is not multiple sign language interpreters]
JS: There is another use case here, putting the call on hold without having to re-input e'thing.
<Judy> [JB: it is one content window, one presenter or chair window, and one window for an interpreter or a real-time captioning stream]
JOC: Sounds good also.
JS: How do you jump between your monitors and audio devices
JOC: So we have potentially a couple more use cases?
JS: Yes, they are variants of head pinning - tracking the locus of control accross devices etc
JW: Janina is right as there are reasons to set the point of regard.
We need to document etc
So with this Remote Meetings doc - we have clarified its relationship with existing guidance..
referencing capabilities of existing tools..
JW: Any other changes?
JS: Thats fine, we also have
other agenda.
... I've a request
JW: We have an update on this.
Josh getting some valuable input from PING
With potential for a joint.
<jasonjgw> Josh: he is meeting with PING; there was a coordination request from them. They are planning to provide comments related to our work, and at that point we should be able to arrange a joint meeting in the next few weeks.
JW: Thats helpful
Any issues or matters of interest that we should take up?
JOC: Something that has come up is touch surface in XR content.
There is a potential for profiling in XR along these lines
WebXR API allows 2 or 3 bits of fingerprintability
https://github.com/immersive-web/webxr/issues/983
https://immersive-web.github.io/webxr/#dom-xrsystem-issessionsupported
JW: Right, so how can we just what can be disclosed there?
JS: Its also situation dependent? The tech isn't a problem, its governance.
<existential discussion around fingerprinting and real or imagined privacy concerns for people with disabilities>
JW: <gives overview of potential use case>
JS: I want to be clear with the PING that this also a potentially very interesting and useful use case that can be useful for good stuff
JW: The potential for positive use cases in there.
But it we need to gain informed consent.
These are policy issues - and how they impact on the default behaviour is important.
JS: I want to hear their thinking.
JOC: the points Janina makes are
broadly applicable.
... This would be a good topic to have with someone from
PING
JS: Lets put this on the agenda.
JW: +1
https://github.com/immersive-web/webxr/issues/983
JW: We are waiting for their comments to come thru.
JS: So re Verifiable Claims.. I was doing are action.
And could not find our ranked listing
JW: I re-ordered this on the wiki page that collects them
JW: The ordering on that page reflects our prioritisation
JS: I'll go to minutes and follow up.
JB: +1 to discoverability
... Should be a priority.
... I want to send info on what to do with A11y and Remote.
Do we need a landing page?
Would like a more public user friendly page?
<jasonjgw> Josh thinks a document that is not in a wiki format would be useful.
JOC: +1
https://www.w3.org/WAI/standards-guidelines/mobile/
JOC: Looks more professional
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 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/thought deaf /thought deaf community in some countries / Succeeded: s/in large classroom settins/in these tools and in large classroom settings/ Succeeded: s/beenfits/benfits/ Succeeded: s/benfits/benefits/ Succeeded: s/hwo/who/ Succeeded: s/contnet/content/ Succeeded: s/bassis/basis/ Succeeded: s/government/governance/ Default Present: jasonjgw, SteveNoble, scott_h, Judy_, Joshue Present: jasonjgw SteveNoble scott_h Judy_ Joshue Joshue108 Found Scribe: scott_h Inferring ScribeNick: scott_h Found ScribeNick: Joshue108 ScribeNicks: Joshue108, scott_h Found Date: 01 Apr 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.)[End of scribe.perl diagnostic output]