<scribe> Scribenick: Joshue108

Accessibility of remote meetings.

JW: We are starting with the remote meetings page, then open Github issues - then at the end we will discuss TPAC collaboration.

SH: Sounds good

JW: I've been looking at this, seems the advice we give to various players is reasonable.

We could clarify some parts - a la relevant W3C guidance.

Relevant WCAG SC's etc..

Mostly there - all seems reasonable.

JB: joins

<getting up to speed>

We need to clarify relevancy.

JB: I can clarify - IMO the unclassified issues represent a substantial checkin.

There are things missing from this. Needs better sequencing and organisation.

I do feel this is urgent. Am looking at what other orgnanisations are doing.

Especially WCAG 2.2.

There has been internal discussion on getting Zoom to take up RTC.

They may also be referring back to this doc.

It may be feeding into these background discussions.

Anyone had thoughts on input into WCAG 2.2?

Anyone else had ideas? I have.

JW: I'm not totally prepared but there are some places.. when looking at WCAG 2.1 - there are SCs that deal with pre-recorded material, syncronised media etc.

But there is no corresponding one for live.

This eliminates live meetings - etc

But looking at something modelled on existing requirements but looking at live would be a good starting point.

JB: Yes, that is pressing.
... We need a draft of input for this.

Could be a matter of pushing what is there or if additional wording is needed. Thoughts?

JW: For Live Captions, we could increase the priority.

Also maybe Audio only, or something that only covered pre-recorded criterion etc

Identifying those would help.

That may have to be at AAA - at least there would be a requirement there.

Modelled on the guidelines..

JB: Would it be AA for some, most, all situations?

Maybe not all, but to increase situations for AA recommendations would be a significant change - need to rethink the context.

JB: Any comments?

JW: I can go thru the page and clarify where we identify them and refer to lack of coverage for live content.

Make it obvious that this is an open issue - we can then take to AGWG.

JB: Very good, thanks.

JW: Will I wait for Judys comments before revising?

JB: Open season.

JW: Ok
... Other comments?

Can others review once I've made the changes. We can publisize more broadly.

JB: Will ping the list and chat about this soon.

SH: I've added to it, and some Education related stuff.

Other sectors should be represented here. Thoughts?

JB: What did you put in? What educational guidance?

SH: I may need to review again - but was looking at how our meetings may interact..

JB: <drops>

JW: Agrees with Scott.

Open issues on working drafts.

https://github.com/w3c/apa/issues/80

<jasonjgw> Josh notes a significant list of substantive comments.

4.18 4.18 Binaural audio track alternatives #80

<jasonjgw> Mono audio modes of operation can benefit people with hearing impairments and should be recommended. (comment in issue.)

<jasonjgw> Josh: XAUR doesn't refer to mono.

<jasonjgw> Janina notes that

<jasonjgw> Janina notes that XAUR already addresses spatial audio.

<jasonjgw> Janina notes that mono gives a good mix of audio channels without the spatial data.

JOC: So it looks like we need this.

JW: This is desirable addition.

<scribe> ACTION: Josh to draft text around the need for Mono. addresing comment 80

<trackbot> Created ACTION-2254 - Draft text around the need for mono. addresing comment 80 [on Joshue O Connor - due 2020-05-06].

# 4.4 Immersive personalisation https://github.com/w3c/apa/issues/83

<jasonjgw> Immersive personalization: the comment suggests taht users should be able to categorize symbols to make them easier to remember.

<Zakim> Joshue, you wanted to ask what is the spec that Janina was referring to that should be supported?

Personalisation spec in APA.

JS: This is what needs to be supported so the XR doesn't need to specify it.

Mechanism to map via the Bliss index.

Sounds like a list Robert Heinlin novel :-)

<janina> For the Personalization specification activity, please consult:

<janina> https://www.w3.org/WAI/APA/task-forces/personalization/

JOC: We should have a pointer to the TF wiki.
... ACTION: Josh to draft new text for XAUR on this and reply to OP for #83

<jasonjgw> t is agreed that two actions will be taken: Josh will draft revised text for the XAUR reflecting the user requirement, and write a reply to the issue on GitHub.

JS: Autoplay is a standard WCAG requirement.

JOC: Lets just reference WCAG.

JW: Is it clear enough in the doc that the scope is XR requirements - but may be covered elsewhere.

JS: Good point and similar to what I've been saying in Silver about XAUR and WCAG 3.
... Before we get to the new stuff - we need to cover the things we already know but should be considered in a 360 environment.

I bring up the issue of subtitling/captioning in immersive envs.

JW: Also some of the motion requirements.

Could create new requirements - or extensions to existing ones.

Needs gap analysis.

JS: So we are chatting with Silver soon - so there is an overlapping effort.

+1 to Janina

Important points from Jason and Janina - a lot of what we are doing is building on what we already have.

# 4.13 Immersive time limits https://github.com/w3c/apa/issues/84

<jasonjgw> The comment suggests that users may need to be notified when they've reached a time limit in an immersive environment. This could be customized in a preference regarding how time is tracked.

JS: Is this an a11y issue or a main stream need?

JOC: This could be a COGA type thing.

JS: Looks like a mainstream requirement.
... We choose our alarms in Android etc.

JW: Timelimits are controlled by WCAG.

JS: This is a different use case - WCAG relates to not having or extending timelimits.
... Seems like an equivalent - where you can extend a limit.
... We may not be using the term in the same way.

JW: Timelimits on activity is one thing..

If there is an action or process in XR that needs to be slowed down.

Timescale modification is supported in HTML5 -

JW: In the MAUR?

JS: Yes.

JW: So should this go in as a requirement in the MAUR reference?

<jasonjgw> Josh concurs with the proposal to refer to MAUR.

<jasonjgw> There is a generic requirement to be notified of expiry of time limits.

JOC: This may be a generic user requirement on reflection.

JB: Mentions use cases on neurodiv, vertigo etc

We don't have a lot of dialog with those communities.

JS: We should ask what is the specific a11y user need?

JB: Needs more info

JW: Just you wanted to circle back..

SH: You were asking what education related use cases did I add to the remote meetings doc?

JB: Yes, thanks.

SH: <gives overview>

JB: Our ability to cover some topics at length and deeply may be limited.

We need certain use cases and techniques - needed also for elearning and telemedicine.

Matrix needed -

SH: That's good.

JB: Lets chat.

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)

Default Present: jasonjgw, janina, scott_h, Joshue
Present: jasonjgw janina scott_h Joshue Joshue108
Found ScribeNick: Joshue108
Inferring Scribes: Joshue108
Found Date: 29 Apr 2020
People with action items: josh

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.)