<Judy> agenda order?

<scribe> Scribe: Katie Haritos-Shea

<scribe> ScribeNick: Ryladog

Confirm scribe, agenda, next meeting date (May 10)

JB: One month from because of Beijing AC meeting
... That date will be may 10th

WCAG 2.1 FPWD reception, progress, problems, messaging

JB: WCAG 2.1 is the topic, maybe we should wait until AWK gets here

Rechecking EOWG new charter scope/focus

<Judy> agenda order is 3, 4, 5

JB: For EO charter, they are thinking about it. Like APA EO has a parallel role as it is for reviewing/supporting all groups
... They may recharter in maybe October

SHAWN: Redesigning WAI webiste, updating and redoing document, and outreach\

JB: Will you potentially be working with more technical groups?

SH: We are considering that

JB: Any thoughts?
... We need you you comments

KHS: I was thinking maybe EO was going to help with new WCAG 2.1 UNderstanding Doc?

SH: Dont know about that

MC: Dont know about that

KHS: It will be very hard for the AG WG to do all SC work and do the Understanding Doc

MC: The cahirs and I are working on this, I do not think EO is technical enough to write Understanding

JB: We dont use EO for crunch work

GK: Reminder of publishing entering the EO fray at some time soon

JB: Yes. When IDPF before they did Accessibility EO stuff in their realm there - now there is an opportunity to plan and carry out the intersection of our work
... Lets talk about this

GK: We are looking at the W3C MOOC - a good item to talk about

JB: Please share your MOOC review stuff with Shadi, me and Shawn
... Share confidentiallyif needed

SH: George can you say abit more now. Who shoudl I follow up with about EO Publishing?

GK: We have Publishing Business Group is probably the best place - but there will be a Working Group Rec track that hasnt gone out for review yet
... It might be good on May 10th to discuss

SH: Need a better idea what EO might be helping with or developing specifically

GK" OK

JB: We need to remind what EO does
... WAI needs to have a coordinated set of activities, even with the re-org
... Shawn and Brett when do you think youll have the draft charter? Certainly by May 10th

SH: Sure

JB: Any quick last EO thongs?

<shawn> in progress work list https://www.w3.org/WAI/EO/wiki/EOWG_Current_Projects#2017_Charter_Work

JEanne: What about Silver?

JB: You will have some things on that right

SH: Can you give us some specfics?

Milestones and publications check

JB: Reorg PM part is now getting more into monitoring milestones. MC you were checking in for your three groups
... Are tthere any documents expected

MC: ARIA WG Personalization FPWD
... WCAG 2,1 Cognitive having a Working Draft of something
... April 18th, so I dont think we are going to make it

JB: Is there already a plan for the messaging

KHS: I thought it would be a huge mistake having monthly drafts

MC: We will not be able to address all comments each time

JB: This has been hughly tricky
... Too many interdependencies
... We created misunderstanding that multiplied. I would suggest that for that portion I would like to be able to help with that messaging.
... Maybe there are things we can do on WAI IG that might help
... Any other publications?

APA participation suggestions

JB: APA has ebbs and flows of groups. We have that now post CSUN for APA. There is a blog coming. Sometimes the best way to find folks is to actually look for referals
... Can we brainstorm this?
... What topics do you need help with ?

JS: We need help with CSS, someone to help facilitate this. It is a black hole

MC: We need more through put, and who are able to communicate it to CSS people

JB: I heard CSS and what else?

MC: Lots of comes and goes categories. Media, in all forms. Authentication. Graphics needs ore attention

JS: Graphics in general becasue SVG has ground to a halt

JB: Dont worry, SVG nmay be picking up again. ANy ideas from foks here that know of people to fill these needs?

JS: APA is a great way to get a view into the world of accessible web technology

WCAG 2.1 FPWD reception, progress, problems, messaging

JB: MC anything to report on issues with WCAG 2.1?

MC: I am guilty of not having read all of the comments. It is not too many and not too few.
... Many say that "this is not ready in its current form". There are some comments that dont understand what the end point of 2.1 is.
... Progress, the bizarre thing, GitHub haas lead to folks just diving into comment comments. So Iam not sire. We will try to address all comments in some way by the end

<MichaelC> https://www.w3.org/blog/2017/02/wcag21-fpwd/

JB: Wondering if biggest challenges what has started to happen recently and what are the stages of this. I think you did a blog for the FPWD. Maybe we shoukd do a 1 or 2 ststaus summary
... So folks have an understanding on the current status and might help demystify the process of WCAG 2.1
... It could be a running blog for each month
... Do you think that is feasiable?

Roadmap next stage: sample roadmaps; populating technical roadmap

MC: I can say tenetively, but I will need to discuss with the chairs

ISC SC35 change of status, accessible products doc for review

JB: Janina

JS: First I have been the formal liaiason between WAI and ISO 35 TC, that is no longer possible - we fellbelow the membership threshold so we had to disband
... Two WG under S 35, one is 8 with is under Gottfried it is the V2
... I can no longer participate because the US deligation no longer has a deligate

JB: So Shadi may be able to as he is a liaison
... What were you tracking?

JS: Their guidance on described video. There was not much of an intersection. I do have a specific item

JB: The usual W3C person must be a staff member, so maybe we can discuss this off line
... And feed it back throught ethe W3C technical liaison

JS: We need to be sure we are not providing conflicting guidance. Part 1 ISO IEC O7-1.

<janina> https://www.iso.org/standard/70913.html

JB: What do you want WAICC to address. Please send mail to Shadi about this update. I am w3c secondary liaison to ISO for WAI
... Anything else?

eme and accessibilty

JB: Many have heard about the EME and accessibility. Theer are many perceptions about it. There had been concerns raised about Accessibility. I wwant to share a resources.
... APA/PF looked at this back in 2013 and several times since then and had a F2F meeting with HTML and MTML Media WG. The upshot was that there were not many Accessibility concens. I wanted to ensure Accessibility testing was done on the ME spec

<Judy> https://www.w3.org/2017/03/eme-accessibility.html

JB: Very specifically we have had more analysis is here. I am not saying it is flawless. Some folks seem to think there might be an issue with many use cases. Being possibly blocked. We are not finding that.

<janina> scribe: janina

gk: Is our AC rep expected to comment on EME?

jb: There is an AC review for EME
... Rep should have email requesting EME review, but it's not required

<Ryladog> I'm back

<Ryladog> GK: We were not sure about the content when using AT. I think this is the only comment we need to make

<Ryladog> JB: That is something we looked at very carefully

<Ryladog> JB: One thing that is very starightfirward - Accessibility information for transcript etc are in the clear - the spec say these thing SHOULD not be encrypted

<Ryladog> JB: thet become de-crpyted

<Ryladog> JB: Even some of the other adaptations we havnt found evidence that they are blocked. But, we cant test everything

<Ryladog> JA: What about the HTML?

<Ryladog> JA: Like a paragraph

<Ryladog> JB: I am thinking about a video track

<Ryladog> JA: EME includes a digital book that is encrypted and then decrypted

<Ryladog> JS: I think maybe you are thinking about the timing

<Ryladog> JB: And that timing is not encrypted

<Ryladog> JB: The time code is exposed to the public -

<Ryladog> JA: So EME excludes text files

<Ryladog> JB: The current EME does not encrypt text files

<Ryladog> JS: Ad the spec actaully encourages that it be in the clear

<Ryladog> JB: If you do encrypt them then you MUST provide a way to get the accessibility information to users.

<Ryladog> JB: It is a very compliacted topic. I wanted to help make clear that Accessibility should not be a considering factor in whether decificng EME is good for the W3C to support

<Ryladog> JS: Our guidance was heard to not excrypt the accessibility information

Roadmap next stage: sample roadmaps; populating technical roadmap

<Ryladog> JB: Last meeting I mentioned I want to help lead get a clearer idea of what the Accessibility Goald are

<Ryladog> JB: Part of that includes a roadmap for technical specs, a roadmap for guidelines work, etc

<Ryladog> JB: I actually want to start with technical specs such as ARIA and APIs. What do you think need to be in that portion of the raodmap?

<Ryladog> JS: I want to be sure that soemthing isnt dropped - to disciver available devices. You pretty much cant go inot FF and say "discover all available devices"

<Ryladog> JB: Discoverability APIs - does WebRTC know that?

<Ryladog> JS: I dont know and I dont know that they feel it is in scope

<Ryladog> JB: Please cc Ralph and copy me - I was talking to him about this today.

<Ryladog> JB: Does API space itself does it itself have a roadmap? I was thinking it does.

<Ryladog> Joannie: You mean like ATK?

<Ryladog> JOanie: I am not aware of them happening right now

<Ryladog> Joannie: a long time ago we tried

<Ryladog> JB: Are they a gleam in somebodies eye?

<Ryladog> JS: Ther are two on windows, one on MAC, one on ..

<Ryladog> JB: Thos e are platform APIs, we want spec APIs

<Ryladog> JB: I want to surface those. To get some of that stuff more visible would help when people have colliding ideas

<Ryladog> JB: I think it might be better if I do some pre-discussion for each of the topics. Then I will ask for review topics

<Ryladog> JB: Joannoe and Micheal expect a ping from me on what would be in the Raodmap _ iwill cc Janina

<Ryladog> technical specs

Announcements, topics, reviews for WAI IG?

<Ryladog> JB: Any nominations for announcements on WAI IG?

<Ryladog> KHS: If AG chairs decide they want regular WCAG 2.1 blog, that would be good to have on WAI IG

<Judy> s/The timing code/The HTML time code/

<Ryladog> GK: We are doing testing of eREader readinf systems. I was planning on a call for more participation. I was thinking about putting that on WAI-IG

Any other business?

<Ryladog> KHS: I will send you the 4 things that need to be in the announcement, I iwll send that to you after this call. Then you can just send it

<Ryladog> JB: We will be coming back to thing including Roadmap

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
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/ redoing document and outreach/ updating and redoing document, and outreach/
Succeeded: s/else??/else?/
Succeeded: s/bazaar/bizarre/
Succeeded: s/Sadi/Shadi/
FAILED: s/The timing code/The HTML time code/
Present: MichaelC allanj Katie_Haritos-Shea janina shawn Judy Joanmarie_Diggs Kathy George Brent jeanne
Found Scribe: Katie Haritos-Shea
Found ScribeNick: Ryladog
Found Scribe: janina
Inferring ScribeNick: janina
Scribes: Katie Haritos-Shea, janina
ScribeNicks: Ryladog, janina

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


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

Got date from IRC log name: 12 Apr 2017
Guessing minutes URL: http://www.w3.org/2017/04/12-waicc-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.