Open issues on working drafts.

<scribe> scribe: janina

jgw: Goal is addressing open issues today

<Joshue108> [RNIB] 4.6 Voice commands #88

<Joshue108> https://github.com/w3c/apa/issues/88

jo: Started this discussion previously
... We can't be that categorical was our previous notion
... We want to support user choice and situations can be complex

<Joshue108> Here is the suggested new requirement REQ 5c: Feedback to the user must be audible or audible feedback must be an option to enable people with sight loss to use the voice interaction

jgw: Usual solution is screen reader running in addition to any browser/app provided speech

jo: Essentially, it says feedback needs to be audible -- that's a given, certainly

sh: Wouldn't sr just be there via api support?

<Joshue108> https://github.com/w3c/apa/issues/88

jo: General theme of managing AT within SR

jgw: One should be able to choose one's modality

<Joshue108> I think we have enough with this to flag the general issue of the need for managing AT in XR

<Joshue108> JS: I've experienced a little managing these various AT audio inputs and outputs - all mono.

<Joshue108> Less functional than my old phone environment..

<Joshue108> Having sound on left is useful - also I had things going thru a mixer

<Joshue108> Locating things is important -

<Joshue108> JB: Spacial Audio

<Joshue108> JS: Yes.

<Joshue108> JS: Having to figure out where it goes.

<Joshue108> JW: Is that in XAUR

<Joshue108> JOC: Yes.

<Joshue108> JW: Should be in both XAUR and RAUR.

<Joshue108> JOC: Will add this spatial audio issue to our list..

<Joshue108> [RNIB] 4.8 Magnification context and resetting

<Joshue108> https://github.com/w3c/apa/issues/89

jo: User need #7
... User may need to check context of their view

sh: Not quite following the connection between the two -- as a user myself
... Zoom plus where one is in context makes sense
... Is that menus should appear as before?

jo: Agree. This may just be mischaracterized in the writeup

sh: Believe this is already quite clear as currently written

jgw: Also in WCAG 2.1

<Joshue108> We should make sure than reflow of Captions and Subtitles etc are covered for XR in Silver

jgw: Notes conversation in Immersive Web about integrating 2D DOM content

<Joshue108> github.com/w3c/apa/issues/90

<Joshue108> [RNIB] 4.10 Gestural interfaces and interactions

jo: Comments that blind users felt headsets weren't necessary

js: Do they mean goggles -- the visual feed?

jb: Spatial audio on headsets can be powerful and as good as visual 3D

sh: mind control headset ...

<Joshue108> JS: I suggest the audio environment is richer.

js: Notes that headset for 3D audio isn't actually necessary with Dolby Atmox and DBX systems

jgw: Perhaps we talk about hardware and diverse combinations in that section?

<Joshue108> We should indicate the need for hardware diversity.

<Joshue108> JS: And isn't it that the blind user wants the interact the same as anyone.

<Joshue108> JS: +1 to Jasons idea, look for a higher level point.

jgw: Notes that section frames everyone's understanding of what's possible and available

<Joshue108> https://github.com/w3c/apa/issues/98

<Joshue108> 4.4, 4.11, and 4.19 similarities, and standardizing personalization and text transformation #98

jsh: Notes that text language and sign language aren't direct translations

<Joshue108> JS: You can't rely on a machine to make that transaction or translation.

<Joshue108> JS: It's more like representing different languages.

<Joshue108> SH: Exactly

jgw: Good papers at last year's Assets conference on machine translation to sign

<Joshue108> wants to give this to Scott to reply on

jb: It's fascinating, though.
... Also signlanguages are localized

js: Notes there's a ISO table of international sign languages
... Good for research and experimentation, eventuall may be useful; but no where equivalent today

jo: interesting for content personalization vs text personalization -- possibly useable distinction

<Joshue108> JS: We also have a TF in APA supporting people using AAC.

<Joshue108> ACTION: Scott H to follow up on Issue https://github.com/w3c/apa/issues/98 Personalisation vs Transformation

<trackbot> Created ACTION-2257 - H to follow up on issue https://github.com/w3c/apa/issues/98 personalisation vs transformation [on Scott Hollier - due 2020-05-27].

<scott_h> josh - github username is sehollier

js: Points out we also have emerging specification for AAC support

<Joshue108> Thax Scott thats assigned.

<Joshue108> personalization vs text customisation

<Joshue108> JOC: There are subtle distinctions here

<Joshue108> JS: We need to work out a way to support these things.

<Joshue108> Build it in..

Accessibility of remote meetings.

jgw: Made text changes and followed up with email requesting review
... Believe we have our most high level concerns noted
... Have proposed resolutions ... We need to decide what to do

jo: Notes his draft

Verifiable Claims

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/js: GGood/js: Good/
Default Present: jasonjgw, scott_h, Joshue, sajkaj
Present: jasonjgw scott_h Joshue sajkaj Joshue108 sajkaj1
No ScribeNick specified.  Guessing ScribeNick: sajkaj1
Found Scribe: janina
Found Date: 20 May 2020
People with action items: h scott

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