W3C

- DRAFT -

WAI Coordination Call Teleconference

24 Apr 2019

Attendees

Present
Joanmarie_Diggs, stevelee, Judy, MichaelC, jamesn, jeanne, janina, Katie_Haritos-Shea, Brent
Regrets
george, kathy, charles_lapierre
Chair
Judy
Scribe
Steve

Contents


<Judy> scribe: Steve

Scribe, rrsagent, agenda, next meeting date

<jeanne> regrets for 8 May

<Judy> NEXT MEETING MAY 8TH

Upcoming announcements & publications

james: regular Aria working draft publication in mid may

joanie: still focused on role parity right now but need to evaluate how many ARIA roles to add

judy: do other WGs depend on aria so want to be in the know?

joanie: will keep other groups in mind before we publish

Checking knowledge domain community group progress?

judy: I keep checking back, seems to have palteaued at 15 members

janina: hoping to find a co facilitator but no response to email

judy: saw Bill Kasdorf (?). Running 1/2 year behind TPAC so may need to restart momentum

concerned that unless somehting happens soonish it will become even harder

any thoughts on next steps

janina, it is important for moving the web forward

still a priorty to find facilitator - should be someone from Library sciences

Recent forum on inclusive library science

judy: A forum by MIT 2 weeks ago about Library Science accessibility

wnated to pull together a Library science discussion with strong a11y plus diversity themes

i attended part

after a few of us discussed doing as a Community Group

will put Katy (?) in touch with Janina, for potential facilitator interest in the KDCG

Check TPAC draft grid

Draft grid for TPAC meetings now available. A swap already requested by APA and thanks to ARIA group for agreeing

<Brent> EOWG confirmed our meeting days are correct.

<Judy> https://www.w3.org/2019/09/TPAC/schedule.html

everyone should make sure group info is correct as required

I'll keep checking on

janina APA aiming for back of week

jeanne: Silver also will be there

Judy: Silver is listed for the developer meetup on Mon Sept 16

oh, looks like a display anomaly.

judy: suggest check for community group attendance

<Brent> Jeanne, EOWG is Mon and Tuesday as well. If you want to coordinate any kind of Silver/EO touch base let us know as summer progresses.

cant see any a11y community group meetups - surprised by that

Silver rolled it in to day

A few FYI's from AC meeting

Judy: as mentioned in last cord call the recent AC meeting (member confidential as usual)

W3C look into more agile peublish process

lots of discussion about Horizontal review

and different app format used in China

Judy and W3C starting to explore this

maybe no dom in mini apps? Is any one else looking into this at all.

katie may be software not web but converge testing

steve: is this wechat?

judy: yes - super apps which have mini apps

katie: there is already some a11y testing guidance for these apps.

janina: DOM is not required for accessibility - eg linux

Judy, so is there a proble wit hA11y APIS when there is no DOM

so perhaps we should start checking now

katie: I don think we need to worry. Some ATs use DOM as well as OS APIs

joanmarrie: sounds correct but I missed some of discussion.

Judy: where would this be mentioned? WCAG, UAG? This could be critical.

W3C is not necessary specific to Web - it could support more

janina: should think in terms of User Agents and think terms of using plat form A11y APIs

<Ryladog> This is not new stuff, it is just software using web protocols (not a browser). The tools have to work with the AAPIs of operating systems

<Ryladog> SEction 508 already does this

jeanne, wcag should apply and aps will be included in Silver

katie: Section 508 is already applying WCAG to software - like web to ICT

<jeanne> WCAG doesn't apply because of strict definition of Web. UAAG applies, but is not REC. Silver plans to cover this area, but there may be opposition from the AC.

especially if we are adding WGs for networks

judy: for apps in Silver I'm wonder if pushback you are experience is old>

jeanne - some are keen to include apps as well

<Judy> jb: perhaps (super rough) in cases where mini-apps aren't using the dom, especially important to use accessibility api's" -- with note that this probably fits scope of a potential update to WCAG2ICT

jb: want to stay on topic of super apps, mini apps and APIs

for AGW charter - one of key things I will be tracking advanced scope

many conversations seem to mention some sort of UA

eg low vision TF items that didn't make it 2.1, and might not make it into 2.2, rely on UA support, andand may be somehting for Silver

I'm curious if any comments here from others for high level assumptions on UAG

katie: another intersection is Gaming

WCAG to ICT means convergence with UAs as AT

jeanne: proposal in Silver is to set up guidleines that apply across many technologies

and then look at how entire accessibility stack might alter the advice

oriented to how all the aspects of the stack would implement that guidenace

<Judy> steve: very clear that something like the high-contrast theme, it is usually cross-cutting concerns

<Judy> katie: but this is beyond browsers

<Judy> ...user agents, as far as web goes, is not @@@

<Judy> steve: browsers, just one area on the stack

<Judy> jeanne: important to note that this is not yet worked out on a detailed level. we would not make requirements normative for the stack.

jeanne, will are not expect normative advice for across stack

<janina> https://www.w3.org/WAI/APA/wiki/Web_Games_Workshop_Position_Paper

Judy, let's drop item 8 as Matthew has a paper out

janina we should help him

Judy: any info shares?

jb: you mentioned Authoring Guidance - do you have details?

jeanne, yes I'll dig it out.

we wish the AG working group and expect some discussion on scope- we should help them

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/04/24 19:44:10 $

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/Paris/role parity/
Succeeded: s/memmbers/members/
Succeeded: s/kasnorth/Kasdorf/
Succeeded: s/behind/behind TPAC/
Succeeded: s/present +//
Succeeded: s/yet/yes/
Succeeded: s/W3C WAI/W3C/
Succeeded: s/Silve/Silver/
Succeeded: s/entire stack/entire accessibility stack/
Succeeded: s/jeanne/jb/
Succeeded: s/in touch with Janina/in touch with Janina, for potential facilitator interest in the KDCG/
Succeeded: s/eg low vision group items that didn't make it do include some dort of UA support /eg low vision TF items that didn't make it 2.1, and might not make it into 2.2, rely on UA support, and/
Succeeded: s/ something like the high-contrast @@/ something like the high-contrast theme/
Succeeded: s/rssagent, make minutes//
Succeeded: s/rssagent, make minutes//
Present: Joanmarie_Diggs stevelee Judy MichaelC jamesn jeanne janina Katie_Haritos-Shea Brent
Regrets: george kathy charles_lapierre
No ScribeNick specified.  Guessing ScribeNick: stevelee
Found Scribe: Steve
Found Date: 24 Apr 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]