W3C

- DRAFT -

Accessible Platform Architectures Working Group Teleconference

06 Mar 2019

Attendees

Present
jasonjgw, scott_h, Judy, MichaelC
Regrets
Chair
SV_MEETING_CHAIR
Scribe
janina

Contents


<scribe> scribe: janina

CAPTCHA Note draft - changes introduced since last meeting.

<jasonjgw> Everyone agrees that Janina's changes are appropriate and well done.

<jasonjgw> Scott notes that the supposed alternative raised in the comment isn't a genuine CAPTCHA alternative.

<jasonjgw> Janina suggests we need to clarify why it's out of scope for purpsoes of the Note.

<scott_h> sorry everyone - webex just kicked me out, will try to come back in

<jasonjgw> Janina and Judy recapitulate the comment response process - replying to each comment and explaining how it has been addressed, giving the author of the comment the opportunity to participate in the dialogue regarding the resolution.

<jasonjgw> Janina will take the responses to comments to the APA Working Group.

<jasonjgw> Janina: review is open until the 24th; there will not be a CfC until the review period is over.

<jasonjgw> Janina: the WCAG-related changes require a CfC that can occur soon.

<scott_h> still having trouble getting on - won't ccept WebEx password. Ironically just proivded traditional CAPTCHA after too many attempts!

<jasonjgw> Janina regards these changes as important due to the cross-references to WCAG.

<jasonjgw> The last remaining issue on the alleged CAPTCHA alternative needs a little more analysis.

<jasonjgw> Janina will contact Google regarding ReCAPTCHA.

<jasonjgw> Janina and Judy will determine the channel of communication to engage Google on this issue.

Augmented/virtual reality accessibility.

jgw: Conversation is building in W3C on both areas, now being called XVR

mgw: A cg and a wg ... immersive web?

jgw: Would be useful we identify considerations likely to emerge
... e.g. issue identifications

<jasonjgw> Janina: we should also identify opportunities for XR to solve accessibility problems.

janina: Also identify opportunity, e.g. possible solution for forced line breaks with large print

sh: When talking 360 video, we also mean audio, correct?

jgw: Good question, not sure how scope is defined

sh: Happy to take on literature review, but need to know the defined scope

<jasonjgw> Janina: suggests looking at any documents taht the W3C is working on in this area - including charters.

<jasonjgw> Janina suggests we should also seek to identify early areas that may not be included in the scope of current W3C work.

<jasonjgw> Example: opportunities to solve scrolling problems for users with low vision.

<jasonjgw> Janina: expanding the use cases is one of the "solid services" this task force can provide to W3C.

<jasonjgw> Jason will create an accessibility use cases/requriements for XR wiki page.

<jasonjgw> Janina: it should be possible to suppress audio or video channels where they are not needed and are merely band width consumptive.

jgw: Useful, also we were speculating on sign language opportunities as well
... One more piece is APA liaison to move forward

Updates - accessibility of domain-specific content.

<jasonjgw> Janina is still working on the framework document regarding domain-specific content.

<jasonjgw> Janina notes the DIAGRAM Center meetings last week as well, where relevant topics were discussed.

<jasonjgw> Janina: design patterns for publishing of extended descriptions, mathematics and chemistry were addressed - the same patterns may be applicable to table summaries.

<jasonjgw> Janina the scheme is to provide an object (image, table, etc.), in the image case, probably in SVG. A text alternative is supplied, if necessary. The aria-details property refers to an alterantive (e.g., the MathML, ChemML, extended description). There is thus a programmatic cross-reference for AT users.

jgw: Interesting set of ideas

jgw; Doesn't require user to expand anything, just a link

jgw: May not always be needed
... Some would be auto generated by javascript, not hand authored

<jasonjgw> Janina: next steps - the aria-details-based approach will be implemented in the EPUB mathematics test book.

<jasonjgw> Janina thinks the proposed approach would be useful in some cases, including relatively short examples (e.g., short music fragments).

<jasonjgw> Janina suggests we're essentially waiting for the EPUB example to be created and to become available for discussion.

<jasonjgw> Janina will help to identify a suitable facilitator for the community group.

jgw: Discussion and agreement to create a Wiki page on RQTF presentations which will be ongoing

Other Business

jgw: No call next week because of CSUN
... Next call is 20 March
... Please note time change for some, U.S. will be on Daylight Time

<scribe> ACTION: jasonjgw to Create wiki page to showcase RQTF presentations around the planet

<trackbot> Error finding 'jasonjgw'. You can review and register nicknames at <https://www.w3.org/WAI/APA/track/users>.

Summary of Action Items

[NEW] ACTION: jasonjgw to Create wiki page to showcase RQTF presentations around the planet
 

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/03/06 14:53:38 $

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)

Default Present: jasonjgw, scott_h, Judy, MichaelC
Present: jasonjgw scott_h Judy MichaelC
Found Scribe: janina
Inferring ScribeNick: janina

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 06 Mar 2019
People with action items: jasonjgw

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]