Accessible Platform Architectures Working Group Teleconference

17 Jul 2019


janina, Matthew_Atkinson, jasonjgw, MichaelC, SteveNoble, scott-H, Judy


<scribe> scribe: janina

Accessibility of Web games.

<Matthew_Atkinson> Here's a technical summary of the Web Games workshop: http://matatk.agrip.org.uk/articles/w3c-workshop-on-web-games/

<Matthew_Atkinson> Thanks again to everyone who helped with the paper, and The Paciello Group for funding my trip :-).

ma: Wide ranging discussion at the workshop
... Notes that a11y wasn't just discussed during the a11y sessions
... A. Rodrigous presenting on mobility a11y
... Almost all participants were aware of a11y, and about half had done a11y work to some degree
... Sessons were recorded, now being captioned, and will be made available online
... Unity has been asking for a11y feedback, which is great because they're the #1 gaming platform
... In the a11y ws itself ...
... Bdige between semantic world of gaming and perhaps aria
... Wroking on expiriments to see what can be made to work even today
... May be sufficient simply to demonstrate proof of concept
... Another reason UI was first focus is CVAA mandate in the U.S.
... Point of games is to make them immersive and fun ... best success now is self-voicing
... we need some kind of bridge for building better UI

<Judy> 21st Century Communications and Video Accessibility Act (CVAA)

ma: Looking for new web assembly bindings
... New to me was pronunciation reqs -- to cover variants for locales
... gender neutral variants? We don't know how to pronounce some of them


<jasonjgw> Janina notes the Pronunciation Task Force and its applicability to Web games (among other contexts).

<Zakim> janina, you wanted to note the Pronunciation TF

ma: Also discussion on game pads aond work on a11y use cases, and binding controls
... See the article -- Ian Hamilton came up with use cases for this
... Noting everyone was open to contributions
... Loads of discussion between WebXR and the gaming groups
... We'll see what comes out in the minutes, definitely overlap in interest
... GLTS key protocol -- promising but early days

jb: Expect the edited report from the WS soon

ma: Minutes are already available
... Content design is the key in gaming, so key to making good a11y as well

<Judy> day 1 of web games workshop: https://www.w3.org/2019/06/27-games-minutes.html#item09

<Judy> oops

ma: Spatialized audio builds a better sense of a windy cave

<Judy> https://www.w3.org/2019/06/27-games-minutes.html

<Judy> https://www.w3.org/2019/06/28-games-minutes.html

<Zakim> MichaelC, you wanted to talk about use cases to AOM people and to mention spoken pronunciation TF

<Judy> day one and day two minutes for web games workshop are now above

mc: Notes discussion of AOM

<Judy> there will also be a report available

mc: Important to let AOM know about these use cases

jb: AOM also cam up at WebXR

js: Suggests an overview session with AOM at TPAC to get everyone up to speed on the various threads

sh: Curious why the sudden interest in a11y from gaming platforms?

ma: Not sure

jb: There's been an active a11y gamer community who have done much of the education
... One approach has been to precook a11y templates for reuse
... Have a simple starting level, and then increasing sophistication

<Matthew_Atkinson> Here's a link to the Game Accessibility Guidelines (also linked from the technical summary post above): http://gameaccessibilityguidelines.com/

jb: Also an effort in advance to make sure a11y was well integrated in ws

sh: Thanks! Good to hear
... Also interested whether there's focus on particular hw? Or more on semantic support

ma: I was surprised by how many features controllers can have today, so am unsure on the balance
... Good news is that dev is open
... Adaptive controller recognition can be taken up via github
... remapping should be in game ideally, because different game activities may suggest different controllers
... most discussed was remapping, but github community very open to further exploration

<jasonjgw> Janina: APA is tracking the emerging specifications.

<jasonjgw> Janina inquires as to next steps.

ma: Have some personal next steps in my writeup
... After the official report next steps should be clearer

jgw: Notes RQTF welcome for further examination

Documents: review and discussion.

XR accessibility.

jgw: Notes Monday evening and all day Tuesday,
... Wide ranging as well
... Ranging from policy to standards, and detailed considerations/challenges in various techs on making them a11y
... Input methods, etc
... Similar to gaming
... Several breakout groups
... WS aimed at organizing a wide group to work on issues

jb: Notes many demos during ws
... Breakouts on all kinds of areas, input/output, metrics which then joined a11y
... some 10 people focussing on standards and policy
... Highlevel goal -- a11y and flexible standards
... Verizon and Cornell were Symposium hosts, two standards orgs there, W3C and CTA
... Agile, born a11y, multiple topics ...
... How to do ed
... A few orgs reported they are exploring applying WCAG in XR, and doing gap-identification
... Discussion on meeting regulatory reqs in XR,
... Though none of the regs exclude, what's required is still unclear
... Some discrete areas for standardization were noted
... interop, graphix standards, captioning, 3d space, saliency and proximity objects,
... How to think about this and leverage AI
... People did commit to followup work

jb; included rqtf, I will create a landing page on that

jb: Many ws participants unaware of standardization activity in this area
... A WebXR API hoping to go CR
... Web GL dependency on Canvas may be an accessibility concern

jb; WebGPU is incubation, but may also have canvas drawbacks

jb: Noted gaming ws and glTF applicability potential
... Noted also the discussion of a possible A11y XR ws
... Perhaps a teach-in on relevant accessibility and XR standards in progress?

js: Asks for follow on?

jb: about 120 participants; organizers want to have some ffollow on

sh: How can RQTF help here?

jb: XAUR is in need of much work
... It needs to be more circulatable
... WebGPU is preparing a W3C WG Charter
... Curious to explore glTF capability in relation to XR
... Also AG relevance
... So, lots of specific work that would be very helpful
... We should look at Josh's XAUR soon in RQTF

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/07/17 14:12:47 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Succeeded: s/oolow/follow/
Succeeded: s/a teachin/a teach-in on relevant accessibility and XR standards in progress/
Succeeded: s/Notes not just a W3C WS, also CTA .../Verizon and Cornell were Symposium hosts, two standards orgs there, W3C and CTA/
Succeeded: s/Incl reports on applying wcag in xr/A few orgs reported they are exploring applying WCAG in XR, and doing gap-identification/
Succeeded: s/WebGL dependency --/Web GL dependency on Canvas may be an accessibility concern/
Succeeded: s/glts/glTF/
Succeeded: s/Vector based grx will be more performant, which is needed//
Succeeded: s/glts/glTF/
Succeeded: s/draft docs before he returns/XAUR soon in RQTF/
Present: janina Matthew_Atkinson jasonjgw MichaelC SteveNoble scott-H Judy
Found Scribe: janina
Inferring ScribeNick: janina
Found Date: 17 Jul 2019
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]