See also: IRC log
<janina> trackbot, start meeting
<trackbot> Meeting: HTML Accessibility Task Force Teleconference
<trackbot> Date: 02 April 2015
<scribe> scribe: MarkS
<janina> Mark is it
JS: We need to talk about Web VTT
review
... hopefully JF will be on the call when we bring it up
PC: I sent an email to the TF to contact the Media TF for discussion items at the F2F
JS: We already have an item for that
JS: Registration closes today. If
you are planning to go and have not done it yet, register
... Paul has sent a request for agenda topics related to
media
CN: we have transcript to talk
about. Working on wiki and work items to structure
discussion
... we have a bug, leonie looked and says its alright
... no other direct issues as far as I know
JS: That is my understanding as well
<chaals> Poll for possible meeting dates in europe
JS: Chaals put out a poll for
participation in a TF F2F in Europe
... also a discussion about meeting during TPAC
... i expect to meet April 30th deadline for responding RE TPAC
participation
... hope to have a TF meeting as part of TPAC
... should start thinking about participating in Japan
<Zakim> chaals, you wanted to say we have transcript and a bug on EME and to
CN: If we have a PF meeting and
the same time as a HTML meeting, most people in here are in
both groups. Would need more coordination.
... may not be a need for a TF meeting if that is the case
JS: PF would probably meet at the same time as WebApps, not HTML
LW: RE: April meeting, Brian Kardell was interested in participating remotely to discuss panels. Wondering if that is a possibility?
PC: i would ask cynthia
... i can't see why not, all the rooms have the ability
... just need to setup zakim
... RE: conflicts with PF and HTML meeting times. If you think
about it, a lot of the work is happening in task forces. I
think we would have simultaneous TF meetings going on during
the WG meetings
... can schedule TF meetings on Thursday afternoon. Should
solve problems of overlap
... could be a conflict for people who are in multiple TF's
CN: That sounds like a great idea to me
PC: would be helpful to get a commitment from the TF for participation.
JS: Slight delay in getting it
published. Must get transition request in and approved, get
announcement ready for FPWD. April 7 is the target date.
... i personally think that date is reasonable
PC: I agree
JS: Waiting for some language from Chaals and some staff work from Liam. Then the WG can run it through their processes. Bringing this in sync with parent group operating procedures and cleaning up out of date references
JS: I plan on informing the canvas-api list of the recent development with Chrome on implementation support.
JS: Next steps are to approve publishing this as the final publication. Start a call for consensus.
<liam> http://www.w3.org/2015/03/alt-draft.html
DM: is this document in sync with what is in HTML 5.0?
JS: What we discovered is that this doc fully mirrored what was in HTML 5 and didn't see a point in that, so we created a stub document that would allow us to park it permanently. Then any edits we want in the spec would be filed as bugs on HTML
<paulc> Do we have a list of filed bugs?
JS: I will try to get the CfC out today
PC: Do we have a list of the filed bugs on alt?
JS: do we have them filed
SM: not against HTML5
PC: are we going to move them off the alt doc component, move them to HTML5 component...
LQ: Create bugs against 5.1.
PC: ED will be used to describe the changes you want, like a written proposal
JS: I think we are looking for a coherent read from top to bottom, hard to do because the spec is so big
<chaals> [+1
JS: there is a response from
Media TF in response to the bug we filed. Leonie provided a
nice summary. I think we are satisfied with response
... JF since the response was addressed to you, can you reply
and thank them?
JF: yes
JS: Cyns talked last week about
how to track a11y bugs against IE. Reminded me that we don't
have a formal process for doing such work for other UAs
... We used to have Bug Triage. I don't expect we need to
reconstitute that at this point. Not a lot of bugs left. If we
see this change, we may consider it.
<LJWatson> +1
JS: should use the TF call to handle it now. We should have a Wiki page to track issues against user agents, tracking support and implementation.
+1
<David> +1
scribe: Liam, can you set that up if everyone agrees?
LQ: anyone on the TF can create a wiki page
JD: I like the idea, conceptually. However, I feel like editing a wiki is a lot more work than is needed. Bugzilla has a feature to track bugs in other Bugzilla instances. Not sure how to set it up. Mozilla and Webkit both use Bugzilla. Not chrome though
BK: I think it would be valuable
for developers (outside this group) to have access to this
information, too.
... what has worked out really well for HTML5 is
caniuse.com
<chaals> [chaals leaves]
<chaals> [+1 to bkardell]
BK: very popular reference for developers.
CS: does bugzilla allow tracking against other databases?
JD: other bugzilla instances, not others AFAIK
+1 for a caniuse for accessibility
<bkardell_> MarkS I can definitely reach out to them
JF: I reached out to caniuse.com
a few years ago. they said they would be interested, but they
would need someone to provide the entire dataset.
... at CSUN a couple years ago, we attempted to do this and
while it got off to a great start, it lost steam
CS: I'm hoping our web driver work will help with that.
JS: can we start with a wiki page? Liam?
LQ: yes
JS: Need to look at WebVTT, more specificity on that. I know JF has some interest in that. I think we need more expertise. Perhaps we don't have to worry about depth as much as just what is covered, what is not
JF: I think I could do that in the next couple weeks. There is also a WebVTT2 that is being worked on. Provided by MediaLabs? I can take a look at it. I believe some representatives will be at the F2F in Seattle. Should be able to comment on it then
JB: What they are looking for from us is a review of their current draft, to make sure it satisfies MAUR
JS: not WebVTT2, just the current version
JB: yes
<paulc> Where is the TF wiki with the new features we want to work on?
<Judy> judy: Thierry Michel should be available for questions if needed while you're going through the MAUR & WebVTT review
JS: we can talk on Monday at Media a11y TF
JF: yes
SM: yes
<Judy> Thierry is staff contact for that WG
<liam> [ https://www.w3.org/WAI/PF/HTML/wiki/Browser_Bug_Trackers created ]
JB: suggest reaching out to Thierry if you have questions, and then potentially inviting him into a discussion if you identify gaps.
<janina> zkim, next item
JF: 7 open actions
... 3 past due
... Steve Faulkner about contacting James Nurthen re
imagemaps
... next is on me
JS: reassign to me.
ACTION-308 reassigned to Janina
<JF> http://www.w3.org/WAI/PF/HTML/track/actions/308
JF: We can close the one on
Leonie RE EME
... ACTION-189 on lang attribute and ACTION-204 are on Cyns,
due next week
... last one is a proposal on menus, due later this year
[adjourned]
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/no/not against HTML5/ Succeeded: s/*other* bug trackers/other Bugzilla instances/ Succeeded: s/open bug tracking system/Bugzilla/ Succeeded: s/an Bugzilla/Bugzilla/ Succeeded: s/all use/both use/ Succeeded: s/webdriver/our web driver/ Succeeded: s/WB/WG/ Succeeded: s/if you identify gaps/if you have questions, and then potentially inviting him into a discussion if you identify gaps./ Found Scribe: MarkS Inferring ScribeNick: MarkS Default Present: Janina, Judy, Plh, chaals, +1.617.319.aaaa, Joanmarie_Diggs, ShaneM, David_MacDonald, paulc, marks, LJWatson, BrianKardell, JF, Liam, Cynthia_Shelly Present: Janina Judy Plh chaals +1.617.319.aaaa Joanmarie_Diggs ShaneM David_MacDonald paulc marks LJWatson BrianKardell JF Liam Cynthia_Shelly Found Date: 02 Apr 2015 Guessing minutes URL: http://www.w3.org/2015/04/02-html-a11y-minutes.html People with action items:[End of scribe.perl diagnostic output]