W3C

– DRAFT –
Accessible Platform Architectures Working Group Teleconference

12 May 2021

Attendees

Present
janina, jasonjgw, John_Paton, Joshue, Joshue108, scott_h, SteveNoble
Regrets
-
Chair
jasonjgw
Scribe
Joshue108

Meeting minutes

RAUR: Status.

JW: This is to discuss CFC

Some favourable responses

JS: Open till midnight Boston Friday

XAUR: open issues.

<jasonjgw> Josh: acknowledges that we need to publish a new working draft, or address the comments and proceed to publication. Josh is considering the schedule.

<jasonjgw> Josh notes we have new user needs/requirements.

<jasonjgw> He also notes there aren't many outstanding issues at this point. We could address them in the coming weeks.

JW: I think we can proceed on that basis that we will have a CFC shortly

If we need another review we can add one.

Reasonable?

JOC: Sounds good

<jasonjgw> Josh is waiting for responses on several comments.

[New User Need] 4.20 Wayfinding - Review of XR Accessibility User Requirements COGA

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

JS: Why mono?

JB: Don't understand that? Why?

For sign posts having spatial orientation is useful.

JP: Espec for limited vision - you would need 3D sound?

JB: What about hearing on one side?

JS: That is a separate question. This is listed as accomodation for vision

I don't understand

JOC: I'll follow up on that

NEEDS INFO

JS: Are bread crumbs needed? Is that useful?

NEEDS INFO

JB: May be useful in some environments, but not something that is found too much in gaming.

There is a functional issue for people with spatial disorientation. Will that carry over into virtual space?

There is also a NEEDS INFO request to COGA from me on this one

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

4.12 Does not provide enough information for actionable implementation [XAUR]

Immersive time limits

JW: This could be useful in some contexts but also dealt with by other means, portals etc

JS: Why is this specificly useful for vision.

JB: What if not just for vision? Something that they raised, multisensory etc.

JS: Yes - it may be

Could be a series of reasons.

JB: Regarding https://github.com/w3c/apa/issues/176 I can thinks of lots of reasons why this is valid.

acj judy

<Zakim> janina, you wanted to note that we have a technological solution with MQ5

JS: Regarding Gottfrieds students preso, this showed us a solution

Via Media Queries 5 - we can control that.

JB: The Immersive Captions CG may also have some useful research.

[New User Need] 4.21 Understanding Actionable Targets - Review of XR Accessibility User Requirements COGA #181

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

https://raw.githack.com/w3c/apa/6d5bf713d9d7c65ecda104c213ad47b0e98cfbe1/xaur/index.html#interaction-and-target-customization

JOC: Read out the new suggested need etc

JW: In the 'real world' e'thing is touchable and actionable.

SH: Is this covered by character sets?

SH: There is already indication that something is a target, for personalisation this is covered already.

JS: There is semantic confusion here, about how words are used

JS: They may mean the palette of controls by which you can do something to a target.

SH: Already covered.

<Zakim> Joshue, you wanted to talk about affordances

JOC: What do you mean by palette of controls?

JS: Actionable items etc like in a browser radio buttons, sliders etc

JOC: Does this relate to the translation of affordances?

JS: Gives a medical example.

JW: <reexplains for Josh>

JW: I think some things do need to made conspicuous

JOC: I think there is a potential need here.

JS: Agreed but it is not clear,

JOC: I'll take an action for more info on this.

NEEDS INFO

SH: I'm not clear of how this would be implemented?

JOC: This is covered to some degree already, a la Personalisation AAC etc

JW: We need more detail on the use cases.

Accessibility of remote meetings.

SH: We have been working on this, thanks for suggestions etc

<Go Notepad>

SH: Wording has been tightened

We have clarified some key points, definitions on Hybrid meetings

We have outlined sections, issues - there are 5 sections.

<Gives over view of structure>

SH: We relate much of it to existing W3C guidance.

There is a new section in this draft, hosting an accessible hybrid meeting.

Still Work in Progress - looking forward to feedback.

JB: I'd like to mention some new things I've added.

Would like a more indepth discussion soon, when we have gone through backlog.

JB: Question around structure and presentation.

https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Accessibility_of_Remote_Meetings:_Structured_Draft

There are placeholders for some new things..

Such as W3C is starting to look at accessible virtual conferencesplatforms

JB: I'll update that.

Also a new section on working with vendors to improve a11y

JB: Reactions to these?

JW: Seems like a chance for W3C members to look at their platforms a11y support.

JOC: Sounds like a good direction.

JB: Scott and I have been discussing hybrid meetings

https://www.w3.org/WAI/APA/task-forces/research-questions/wiki/Accessibility_of_Remote_Meetings:_Structured_Draft#Holding_accessible_hybrid_meetings

JB: Where virtual and real meetings can interface correctly.

JB: Any ideas on the hybrid meetings?

JS: Yes, It is important to look at what tech resources are available.

You can treat e'one there as if they are remote.

There are also solutions that will keep the camera on who is talking, and move the focus accordingly - as well as only pipe the active content down the wire.

SH: <Gives overview of experience with hybrid meetings>

SH: There are challenges.

JB: This is great feedback.

<Gives over view of hybrid meeting in Seattle for Inclusive Web etc>

JB: THere is a big section of unprocessed comments

JB: The language needs to be regularised - here is what you need to know.

Then we need review/vetting.

JW: I'm happy to review after next round.

JB: Anyone else?

JW: With hybrid meetings we also need to look at captions etc

Media synchronization.

JW: This may be a discussion for later. Janina has suggested that this move towards a NOTE track deliverable.

JS: Very much

There is value here - the wiki would be useful but better elevated to NOTE status.

JW: Ok, it can evolve on the wiki and can be moved later.

JS: Anyone concerned?

<crickets>

JS: I'll follow up with APA

Web of Things and Devices/Sensors use cases - introduction to topic.

JW: This is coming via APA - we can note this but discuss later.

JS: This came up in APA a la our new work etc

<SteveNoble> have to jump off to prep for my next meeting

I'd like RQTF to see if we can identify a11y specific applications for some devices and sensors.

Similar to WoT request

JS: Is there an a11y use case that we should cover?

There is a WG being rechartered.

Can we take some time soon to explore?

Joint working group meetings at TPAC 2021.

JW: We have to start thinking on this.

Meeting with Immersive Captions Community Group.

JB: I'll co-ordinate necessary supports

JW: We can find tune agenda etc - then circulate meeting etc

Minutes manually created (not a transcript), formatted by scribe.perl version 131 (Sat Apr 24 15:23:43 2021 UTC).

Diagnostics

Succeeded: s/JS: Dont/JB: Don't/

Succeeded: s/virtual meeting /virtual conferences

Maybe present: JB, JOC, JP, JS, JW, SH