WAI Coordination Call Teleconference -- 01 Aug 2018

<Judy> meeting: WAI Coordination Call

<janina> scribe:

<Judy> scribe: Janina

scribe, rrsagent, agenda, next meeting date

jb: Do we need to meet 15 August?
... Any additional regrets for the 15th?
... Any regrets for 29 August?
... I'm actually at risk on the 29th

<Judy> CONFIRM NEXT MEETING AUG 15TH

upcoming publications & announcements?

[crickets]

<Judy> Judy will check back into pending questions on epub publishing of echidna Recs

update on WAI charter renewals (thanks!)

jb: Thanks all around for all help in reviews, moving drafts forward, etc.
... APA progressing with comment responses, seems will be OK
... ARIA may take a bit longer with responses
... Believe this covers all WAI charters for the time being

APA's Community Group update

<Judy> scribe: Judy

<MichaelC> https://www.w3.org/WAI/APA/wiki/Community_Groups

JS: MC, can you queue up the APA CG Wiki? Thx
... APA WG did it's nearly annual CG review
... we identified some that were relevant to track
... for instance blockchain

JB: trying to identify from the APA CG Wiki which ones you're looking for help with

JS: may not have been updated the way I thought

JB: think that would be useful for WAI CC to hear which ones you think have relevant activity, and which ones you want help tracking

JS: I'll bring this back in two weeks with a clearer report

JB: Is there a CG requirement that the work is visible in the CG?

TS: [before previous comment] there is an issue that the work isn't necessarily visible on the CG page, if it is happening in Github
... there's an AB issue related to this

JS: It is possible to add your GH repository to your CG page -- but it's not very discoverable

MC: Hard to get that one fixed.

tzviya: follow up with AB on GH issues with visability of CG activity and proper IP attribution

<scribe> ACTION: tzviya follow up with AB on GH issues with visability of CG activity and proper IP attribution

<trackbot> Created ACTION-9 - Follow up with ab on gh issues with visability of cg activity and proper ip attribution [on Tzviya Siegman - due 2018-08-08].

<scribe> ACTION: judy follow up with systems team about CG captcha problem

<trackbot> Created ACTION-10 - Follow up with systems team about cg captcha problem [on Judy Brewer - due 2018-08-08].

<scribe> ACTION: michael discuss with ralph the issue about discoverability of CG resources

<trackbot> Created ACTION-11 - Discuss with ralph the issue about discoverability of cg resources [on Michael Cooper - due 2018-08-08].

<scribe> scribe: Kim

<kimpatch> Janina: work we did to get transcripts for media in HTML 5 – failed on that but might be a basis for a framework

<kimpatch> Janina: way to go about it master that might include full video or partial video here and there

<kimpatch> Janina: cover both cases – coordination with video and not coordinated

<kimpatch> Janina: lead person from Daisy to work on it with community group

<kimpatch> Janina: inclined that if we don't use the same approach were going to reinvent something relatively similar – look at what already exists and that's a good path forward

<kimpatch> Janina: trying to socialize this conversation in a couple of fora to get people involved and Get it moved forward so we can have good conversation on TPac

<kimpatch> Janina: after we've looked at proposals will figure out what has promise

<kimpatch> Janina: what organization is Marisa from – Daisy

<tzviya> Marisa's 4 month old requirements (may be out of date): https://github.com/w3c/sync-media-pub/tree/master/drafts/

<kimpatch> Janina: primary resource was a word we had to invent – it was just the video. And for You have alternative representations. We have this whole list and the user accessibility requirements. The one we never got was transcript and there were several proposals kicking around for that including an approach sufficiently elaborate – you could tag down to the level of the word. You could keep things really really synced. I think it may cover a lot of use c[CUT]

<kimpatch> digital publishing.

<scribe> scribe: Judy

Kim: glad you're following up on this

Janina: SMIL tag set doesn't quite cover it

<kimpatch> Janina: even if we want to highlight down to the syllable level

<scribe> scribe: Kim

APA's Publishing-intersections update

[re-trying] common architectural approach/batching for mathml, chemml, music?

<kimpatch> Judy: approach on this is what we wanted to hear more from Janina on

<kimpatch> Janina: we could make a very long list – all kinds of specialized knowledge where we probably don't present that information as accessibly as we could for students especially at graduate levels.

<kimpatch> Janina: vendors aren't going to do this – have to know Biology and aria

<kimpatch> Janina: is there something that we can do to get this started – everyone takes on the task of something we can do to get this started for a particular knowledge discipline. I have some very high-level ideas that I could elaborate on but the whole idea is to talk about things enough so that there could be a meaningful conversation at TPAC

<kimpatch> Janina: what I think might be the minimal skeleton that we probably could all agree on – but on its own even as limited as it is would probably be a major platform with Web WG

<kimpatch> Judy: problem statement – next the potential direction for a solution?

<kimpatch> Judy: can we have an equally short version of potential direction for solution?

<kimpatch> Janina: the potential solution – all the specialized markup knowledge math, chemistry etc. is not going to be the bulk of the digital publication – probably English or German or whatever the main languages. But interspersed throughout possibly heavily math formulas, physics, whatever. So you're gonna want to know where this special markup starts and what it span is.

<kimpatch> Janina: and you're going to want to be able to say I have this particular type of markup is – declare them, nowhere it start so you don't have to parse every word – you know where it is and you know where to hand it off to

<kimpatch> Judy: that addresses the case where you have specialized markup interspersed with native language markup. What about when the whole thing is just like a music score or a set of chemistry formulas

<kimpatch> Janina: I think the music store has the same requirements whether it's a full symphony or short excerpt in a harmony textbook

<tzviya> more discussion

<kimpatch> Judy: quick reactions – need more discussion in this setting on another call?

<kimpatch> Judy: thinking of this for silver – some tiein

<kimpatch> Janina: take a look at Kim's Minutes after the call and see if you could polish up a statement – problem statement potential solution

Any WG or TF updates or infoshare?

<scribe> scribe: Janina

js: APA's new charter calls for work on correct TTS pronunciation, which ETS has agreed to take on.

jb: i18n?

js: Yes, will do

other business?

<Judy> [crickets]

rechecking github issues

jb: Reminding the desire to bring github a11y issues to Microsoft's attention, as they're more likely to do something about that as they take ownership of github

WAI Objectives

jb: Notes annual W3C practice of highlighting 2-3 objectives per area per year

<Judy> Some candidate items being brainstormed currently, team-side: Roadmapping AI for accessbility conformance testing

<Judy> Accessibility training

<Judy> Systematizing accessibility work on verticals

<Judy> Defining next steps on guidelines

<Judy> scribe: Judy

Janina: Accessibility impact statement for every spec, along with privacy and security

<janina> mc: Notes that spec tools prompt for Privacy/Security, but our request for a11y has been rejected

<janina> jb: Will raise and explore

<janina> mc: Notes that many specs have Priv/Sec sections that say "No impact"

- DRAFT -

WAI Coordination Call Teleconference

01 Aug 2018

Attendees

Contents