– DRAFT –
Accessible Platform Architectures Working Group Teleconference

Inaccessibility of CAPTCHA.

<SteveNoble> jasonjgw: CAPTCHA discussion - issues we can keep working on?

<SteveNoble> janina: Still need to look at the Cloudfare implementation

<SteveNoble> janina: Need to get an handle on where the work on trust tokens is at

<SteveNoble> jasonjgw: seems like two parts - (1) trust tokens and privacy

<SteveNoble> jasonjgw: (2) overall conclusions and recommendations are the other

<SteveNoble> janina: Shifting responsibility to user agents and away from authors seems like the direction

<SteveNoble> jasonjgw: Have not seen any new comments on github so far

SN: Lionel has joined

<SteveNoble> Lionel_Wolberger: Let's keep going and not slow track it

<SteveNoble> janina: Maybe asking is shifting to user agents may help generate comments?

<SteveNoble> Lionel_Wolberger: Maybe hardware tokens as well...emits a sound, for example

<SteveNoble> Lionel_Wolberger: Many organizations that people encounter have regularized processes - may need to look at those examples

<SteveNoble> Lionel_Wolberger: Mutually trusted third-party can broker a connection

<SteveNoble> jasonjgw: Any more at the moment to discuss?

<SteveNoble> Lionel_Wolberger: Not much to report this week

<SteveNoble> Lionel_Wolberger: Previous focus has been on proven humanity

<SteveNoble> Lionel_Wolberger: 2-factor authentication has been around for a while

<SteveNoble> Lionel_Wolberger: Maybe using 2-factor approach can allow someone to bypass CAPTCHA approach

<SteveNoble> Lionel_Wolberger: Example of people bypassing typical security screening at the airport by setting up TSA pre and such things

<SteveNoble> janina: Probably not much to add to the legacy CAPTCHA language

Synchronization Accessibility User Requirements.

JW: steve commited some changes

do you have more?

<Lionel_Wolberger> Lionel thanks the group for its work on improving Captcha for people with disabilities. Looking forward to more progress next time.

<SteveNoble> https://github.com/w3c/apa/issues/211

sn: we are close

would like to address this, xr related

i have created some text

sn: reads text

<SteveNoble> Virtual reality and other forms of immersive digital environments are relatively new and can present a number of accessibility challenges. Both captioning of speech and video description of visual and auditory information presented in immersive environments are required to provide an inclusive experience. However, virtual reality, augmented reality, and other forms of interactive 360-degree audiovisual experiences generate particular access[CUT]

sn: that addresses john P and rajas comments

rk: relating to blind and wayfinding a la noise in 360 - games use radar, maps and directional.

we can brainstorm now

or we could add the word, wayfinding which is indicative

js: is a little concerned about scope

we may deal with this in xaur

more appropriate

https://www.w3.org/TR/xaur/

dont want to mix up too many things here

jw: we can clarify research limits and indicate new directions

js: didnt we do that in xaur?

we should cross reference?

<SteveNoble> Joshue108: Wayfinding and directions are mentioned in the XAUR

<SteveNoble> Joshue108: Being able to translate into different modalities was covered

https://www.w3.org/TR/xaur/#spatial-orientation-mono-audio-option

<SteveNoble> janina: We may want to reopen XAUR to deal with new developments

+1 to Janina

on keeping the SAUR lean and focussed

<SteveNoble> janina: Better to keep SAUR focused on syncronization

<SteveNoble> raja: Keeping this focused on synchronization sounds good

jw: will review the xaur again

https://www.w3.org/TR/xaur/

JW: Steve does that help?

Sn: Yes

We should link to the XAUR

SN: to say John P is on the call

JW: We can frame this as something that needs further research

JS: We should re-read and compare both SAUR and XAUR etc

JS: I'm concerned about saying the same things in two docs

they can get out of sync

SH: Asks a question about video descriptions - is that audio description?

JS: We do want AGWG to clean up their language.

JS: <MAUR was the first doc - history lesson>

JS: Amazon has been challenging by creating audio out of text streams

SH: So WCAG 3 will move to video description?

SH: No one in OZ will understand that

JS: Indeed - <discussed text description and pausing video to pause video>

We have use cases that are not covered by audio

JS: MAUR could be updated also

JW: Anything else Steve?

SN: That takes care of the last issue in GH

JW: I can merge that

JOC: Go for it

<SteveNoble> Joshue108: Messaging on SAUR update?

<SteveNoble> janina: Need to establish if this is going to be a joint publication first

JOC: wfm

<SteveNoble> jasonjgw: This will change the messaging text

Accessibility of Remote Meetings.

<SteveNoble> jasonjgw: Major work has been going on for Remote Meetings documents

<SteveNoble> jasonjgw: Lots of work by Scott!

<SteveNoble> scott_h: Have worked through most issues, a few remain

<SteveNoble> scott_h: Issue 266

<SteveNoble> scott_h: Insuring when a waiting room is used that status messages are accessible

<SteveNoble> scott_h: Broader considerations of the developer's perspective of how access to these messages is provided

<SteveNoble> scott_h: Proper to point to WAI spec about alert messages

<SteveNoble> jasonjgw: This was added to WCAG 2.1

<SteveNoble> jasonjgw: Meant to make sure this was available to API - applies to 4.1.2

<SteveNoble> janina: Providing these (according to 4.1.3) to the API is needed

<SteveNoble> scott_h: But all of these messages can be overwhelming

<SteveNoble> janina: Pinning some of these to a braille display is a good process

<SteveNoble> scott_h: Issue 292

<SteveNoble> scott_h: How all people should be able to see and hear each other in virtual and hybrid meetings

<SteveNoble> scott_h: The problem of how close to a microphone someone needs to be

<SteveNoble> janina: This is a bit overstated...do we really need to mention these?

Natural Language Interface Accessibility User Requirements.

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

<SteveNoble> jasonjgw: Document by MITRE on chatbot accessibility - this has been added to Github

Take into account Mitre Corporation work on chatbot accessibility. #262

<SteveNoble> Joshue108: some COGA comments on voice menus - we will need to push dicsussion to next week

<SteveNoble> janina: APA meeting time is changing starting next week, starting at 10:00 AM Eastern, so will need to leave this meeting a bit early as regular course