<jasonjgw> zakim list agenda
<scribe> scribe: scott_h
working on XAUR for a while, comments on github
took action to review and timeline of XAUR v2
bringing comments on an ad-hoc basis,
will have 8 left after today's comments
likely we'll be through all 2-3 weeks
end june/early july have document updated
janina: updated working drafft? reasonable projection handing issues
woudl liek to run past immersive web charis
in preparation for TPAC
jason: how does it fit with RTC work? last time n succession with small interval
josh: suggest stick with XAUR, not too man comments on RTC can move to that after
judy: timing of RTC - moving ahead and people starting to plan ahead,
janina: had coversation at joint meeting explaining expectations
These requirements are for next version
judy: may be relevant messaging of RTC as foundation element
janina: yes, absolutely important messaging opportunity
judy: this call not best to sort out, but jason - can you put on agenda next week,
<Joshue108> https://github.com/w3c/apa/issues/89
<Joshue108> [RNIB] 4.8 Magnification context and resetting #89
josh: wanted to talk about this,
want to talk about specifying what's in XAUR vs WCAG/Silver
I suggest some text
relating to the context menus and interface elements
We discussed one half of this issue last week,
but didn't go over the draft text
so good to discuss here and context with silve
<Joshue108> <draft text> Req 7.b: Where it makes sense (such as in menus) interface elements can be enlarged and the menu reflowed to enhance the usability of the interface up to a certain magnification requirement.
quesiton: any concerns/issues?
jason: so basically we're asking is it covered in WCAG 2.1
janina: yes seems relevant to WCAG 1,2 or 3
jason: yes, cross-reference to Revlow SC which is more specific to its requirements
<Joshue108> WCAG 2.1 Reflow 1.4.10 https://www.w3.org/WAI/WCAG21/Understanding/reflow.html
janina; so in virtual envrionemnt, menus are in field of view, not out of line of slight? what is line of sight for someone with low vision/tunnel vision?
wondering if there's a nexus between wiring framework for bieng able to focus on captioned content
judy: great point
<Zakim> Joshue, you wanted to say the scope of Reflow is squarely in 2D layouts.
josh: refleow is really around 2D information, much more narrow. Coudl be a candidate to upscale in Silver
jason: so suggestion is to add it with cross-reference, and if there are issues with field of view
coudl be separate matter but important one
josh: will need to consider use case of focus issues that people with vision impairments may have
<Joshue108> https://github.com/w3c/apa/issues/92
<Joshue108> [RNIB] 4.15 Routing to second screens #92
josh: had a partiuclar use case when drafted,
looked a lot at message/different outputs
the point is bieng made that we need to focus specifically on ruting navigaiton
Sonali: put in one of my UX colleags,
undrstand importance of alerts/sounds for peoel that use Brialle,
josh: need to flag there's a reaosn to route content to second screen, one we dont' specify at all and can route anytihng, or we specify in detial
the first would work, but benefit to be explicit woudl be to teach mortance of accessibility
sonami: wanting to put out as much informaiton as possible in desired format, e.g. Brialle
janina: second screen interesting case in second screen
for more adanced technologies getting what you're accusotmed to
also could second screen manage captions to know who is speaking?
<Joshue108> SH: The second screen doesn't have to sit outside the XR environment
scott; could second screen be in the immersive envrionment, e.g. briallle display inside XR using tactile interface?
janina: why not?
jason: might need a convergence between mutlimodal and virutal environments
janina: ideally user configurations, not machine decisions
<Zakim> Joshue, you wanted to say there may be no need to call out these things explicitly - as this may be cover by 'audio'
josh: perhas what has been suggsted is alreayd covered
I think navigaitonis implict as it would already be audio output
janina: add 'including second screen devices'?
josh: change ...to a Braille or second screen display. would that cover it?
sonali: as long as second screen mentioned, should work
<Joshue108> [RNIB] 4.16 Interaction speed
<Joshue108> https://github.com/w3c/apa/issues/93
josh: original comment: user-step automations may be helpful, machine-learning noting patterns
<Joshue108> SH: This may be more mainstream
janina: seems more mainstram
scott; yes, thinking GOogle Stadia to pre-empty user input, more mainstream use
janina: accessibility coudl be about interacitng/making choice before timeout
<Joshue108> SH: Is this more about time? OR the machine carrying out the pattern.
<Joshue108> +1 to Scott
scott; yes, but don't think its about itme, but more about carring out repetitive task
josh: quite intersting, bringing in new patters base don preivous patterns
<Joshue108> SH: Its like Switch key support - programmable things that you can issue
<Joshue108> Where the machine can work things out..
<Joshue108> I see the a11y benefit but is it something that should go into a requirements doc
scott: I can see benefit, like switch keysupport but automated instead of pre-programmed, but is it a user requiemnet?
janina: maybe shoudl be added to mainstream
josh: accessibiity anticipates future tech, can spot generic needs but others may onot see it
<Joshue108> SH: Coming back to the specific requirements - doesn't fit.
scott: don't tthink it fits directly. Useful as mainstream but not specific requirement
janina: agree
josh: any other thoughts? Sonali?
sonali: agree, will go back to team to update on the discusison
<Joshue108> https://github.com/w3c/apa/issues/94
<Joshue108> [RNIB] 4.18 Binaural audio track alternatives #94
josh: comment was to add user need to provide original soundtrack in AD to build up
judy: binaural? I've heard it used in the audio work for distinguishing headphone and speaker output
janina: confident its headphone-specific
judy: can have a more general meaning
jasoN: can make sure its clear about the intent
janina: yes, is the intent that is' mro than stereo, as close to 360 environment?
Sonali: we were referring to spatial audio
one of the most important things was spatial audio, immersion
thought this would be quite important,
not just auido but AD supporting track
judy: +1
janina: want to void 'binaural',
josh: so agree that audio description track and spatialised along with everytihgin else
<Joshue108> The new requirement is that the audio needs to be spacialised and original soundtrack and audio description.
<Joshue108> +1 to leaving out binaural
<Joshue108> SH: Are you talking about spatially moving sounds from front to back? WIthout ducking?
josh: I'll update, thansk everyone
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/expecaitons/expectations/ Succeeded: s/ envrionment/ environment/ Succeeded: s/pattners/patterns/ Succeeded: s/requirments/requirements/ Succeeded: s/used for speakers/used in the audio work for distinguishing headphone and speaker output/ Succeeded: s/ can make srue its clear aobu the itent/ can make sure its clear about the intent/ Default Present: jasonjgw, janina, scott_h, SteveNoble Present: jasonjgw janina scott_h SteveNoble Found Scribe: scott_h Inferring ScribeNick: scott_h Found Date: 27 May 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]