Meeting minutes
Any updates regarding meeting logistics.
JW: Any update on logistics?
I think we addressed much of this last week
XR Accessibility User Requirements - open issues.
If anyone has issues we can come back
JW: We have a series of open issues
A branch relating to COGA feedback has been created
https://
JW: Where do we stand?
4.20 Wayfinding - Review of XR Accessibility User Requirements COGA #180
https://
https://
<jasonjgw> Josh: way finding - Josh has added material related to mono audio.
<jasonjgw> It is important for spatial orientation.
https://
<jasonjgw> Josh broadened the scope of an existing User Need to address spatial orientation issues.
<jasonjgw> Josh updated the title (of the section).
<jasonjgw> Josh added a note characterizing the orientation issues.
<jasonjgw> Josh notes that the suggestions regarding placement of accessibility options are reasonable, but Judy's concerns are well founded.
<Judy> +1 to the importance of discoverability
https://
<Zakim> janina, you wanted to suggest incorporation by reference
<jasonjgw> Josh notes a further issue on orientation/navigation.
JS: I think we shouldn't discuss that here, as it is a general issue
we may just need a pointer
+1 that
<jasonjgw> Josh changed the title to reflect that the orientation and navigation issue is about focus and navigation.
SH: As a screen mag user I think the wording is great
Works well now to have that guidance
JW: Can we pick a doc or cross reference, or note on discoverability?
JB: We should look at what we are pointing people to..
Regarding authoring tool a11y guideance that is old./
JS: Dont have a pointer.
JB: Our stuff may be a little stale or more web.
We may need to do a separate thing on this.
JS: Or ask Silver?
JW: Everyone happy with these changes?
JS: We have a +1 in Zoom
JOC: I will move these changes into main
4.21 Understanding Actionable Targets - Review of XR Accessibility User Requirements COGA #181
https://
https://
<jasonjgw> Josh: Based on discussion at last week's meeting, Josh drafted a note to the effect that these issues are best addressed through the further development of accessibility APIs.
<jasonjgw> Under "interaction and target customization", Josh has added a note regarding the role of assistive technologies in indicating to users what targets are actionable and how to interact with them.
JS: I think this is a general need
But doesn't need we shouldnt say it
Good that COGA surfaced it
It is also a screen reader need
JW: Sounds reasonable
JOC: Any concerns?
JW: This is a general need - essential for some useful for all etc
JW: There is a layer to provide this info on the user side, then there is providing affordances in the UI
Then you have met the requirement
Also relates to https://
<jasonjgw> Josh: we still need to discuss 182, 183 and 176.
https://
Janina commented on this before
Immersive semantics and customization #182
JOC: Gives overview of backstory
JS: I dont think we need every UI dev to make up their own
this would be confusing
We have overlay mark up technology emerging
So we can say support the personalisation technology
<jasonjgw> Josh will discuss this on a meeting tomorrow and clarify it further.
https://
Does not provide enough information for actionable implementation [XAUR] #176
https://
<jasonjgw> Discussion of the issue led to reference to an article on losing track of time in immersive environments.
<janina> https://
<janina> Oops, wrong link , one moment ...
JB: I dont know that community
<janina> APA Videos: https://
SH: Most devices have some sort of health and well being section etc
DOnt know if it needs to be referenced
Logical that XR would have it too
JS: I'd expect the platform to allow the XR environment to do this.
JS: It should talk about integrating with platform provided tooling tools, such as digital wellbeing, alarms etc.
Josh to update user need 12 with this.
JS: There is a relevant video here on media queries
<Raja> So some accessibility issues veer into health (and to be located under digital well-being). Is there a consistent way to make that distinction?
JS: Josh to add these changes to the branch and merge into main etc
JW: This closes issues
Then we will have a draft to review and consider any further concerns etc
I've noticed a couple of editorial issues
Minor things
We are on track towards publication
Come back to this next week, and then proceed with a CFC
JS: Absolutely
Accessibility of Remote Meetings.
JS: Scott wanted to highlight recent work and request review
SH: I need some more time if ok?
JW: Sounds good
SH: All good
Updates and coordination regarding other work (Media Synchronization, audio transformation, Web of Things use cases, etc.).
JW: Janina has update on a user needs document
JS: We have ongoing work in APA, in a cross group effort relating to the Accessibility Guidelines WG
To specify user needs it will help APA in spec reviews of other groups
JS: It will help with gap analysis
Only two questions
All of our TFs can participate
JB: With new people joining the references and the process may be hard to understand.
JB: This relates to the FAST - Framework for the Accessible Specificiation of Technology
https://
JB: < Gives background>
JB: There is also a checklist of this
https://
JB: Is a helpful document, and not sure how much others have looked at it.
JB: This has not come up for review many times before
JS: You will need a login
JB: Raja and Frances will need accounts to login
JS: We can take comments via email
<Raja> ok
<Josh extended the questionnaire closing date till July 7th>
<Raja> I'll check and get access if needed
JS: Regarding the Media Sync and Natural Language Interfaces, I've been working on those