See also: IRC log
<trackbot> Date: 06 December 2012
<janina> Meeting: HTML-A11Y Task Force Teleconference
<janina> document)
<scribe> scribe: JF
<richardschwerdtfeger> Hi judy, I am just lurking on the call. … working on aria cr tests
JS: looking at longdesc spec whi8ch would give us a FPWD
after last week, decide to look at all objections with care
chaals: sent out an email
starting on that - hoping that someone with more time can take
up the thread
... we have o0ne objection to publishing, and one statement of
noting "issues"
so we must respond to at least the first one
JF volunteers to assist chaals with this effort
David: I have some concerns still, and want to discuss this before it goes out the door.
chaals: agree, and we have a bug filed against that too, so it will be addressed
JS: hearing violent
agreement
... does not appear that there are any new objections that have
not surfaced previously
key is to be succinct in response to the current objection(s)
JS: document developed by text sub-team created to assist in this effort
goal is to avoid 2 W3C specs that disagree with each other, especially around the use of @alt
JS: email from Leonie noting some bugs marked wontfix that have relevance to this topic
JB: Leonie asked that the text sub-team address these bugs, hoping to re-convene that group next tuesday
have also done an initial review of the set
JB: notes that the co-chairs have also invited the TF to be in discussion with the editors over the next while
JS: question is, do we need/want to associate the bugs against the problems identified in David's docujment
believe that this has been requested in the past
PC: looking for some record or
indication of which new bugs have been filed, so that Robin can
meet the direction identified by Judy
... is there a definitive list of which items have been
addressed by editorial team?
JB: that would be helpful, but unaware of direct information to supply that?
JS: seems nobody is directly discussing this with editors
chaals: SteveF and I are in discussion with them, and watching their progress
JB: can we ask that they provide some form of list/notes of what has been processed to date?
chaals: yes
<chaals> ACTION: chaals to report on what HTML editors are doing wrt alt text issues [recorded in http://www.w3.org/2012/12/06-html-a11y-minutes.html#action01]
<trackbot> Created ACTION-150 - Report on what HTML editors are doing wrt alt text issues [on Charles McCathie Nevile - due 2012-12-13].
JS: 2 areas of work - alt
guidance and then actual examples used in the spec
... Question: is anyone thinks we need to move forward with alt
guidance in section 4.8 and the use of alt in HTML spec in
tandem with Steve's document?
JB: I think we've already answered that question, and that we should be moving forward independantly
JS: just wish to be sure that there is full clarification here - but seems that perhaps not
PC: best outcome is that we resolve all problems in the document and it goes away. Perhaps put the question of publishing the alt document be put on hold until the other issues are resolved
chaals: support Paul's observation, propose that we request HTML postpone the question whether Steve's document be published one way or other until all the other issues are resolved
JS: should we make that a formal resolution?
chaals: what I am proposing, yes
<chaals> proposed resolution: We request HTML to defer the question of publishing Steve's doc while we determine whether we can resolve the issues instead.
+1 to proposal
chaals: suggest to defer for 4-6 weeks
(+1 to that too)
JS: any objections on this call?
[none heard]
JS: will run a CFC via email for next seven days
<chaals> provisional resolution: We request HTML to defer the question of publishing Steve's doc while we determine whether we can resolve the issues in the next 6 weeks or so
JS: Leonie is not here
JB: looks like they gathered their remaining stuff and tossed over to me
{laughter}
JB: looks like som have also been sent to some others
(JF notes he has some to review as well)
JS: moving on...
... AAPI Mapping?
cyns: Hard to get everyone
together on a call - may need to look for an alternative
time
... progress is slow
JS: important document, has a
ways to go
... if anyone may not have noted, we have agreed to not have to
map to MSAA, as it has been overtaken by other APIs that are
more current
David: just curious what the new way of referring to MSAA today?
cyns: generally I say UIA
... but if there is a need for more detail then I expand on
that
JB: anyone on this call (John, David, others) - are you available at the old time next tuesday?
David: have a conflict
(JF & JS available)
JB: just want to process Leonie
s list against what we have
JB: ... will look to set up a call for next tuesday then to try and make some progress
<richardschwerdtfeger> problem above is that i.e. supports msaa + UIA Express
<richardschwerdtfeger> iE does not support UIA directly
JS: media has been dormant for a while - we have a charge to propose an extension specification around the old Issue 194
wondering if we should re-convene that group in the new year
JS: we should likely not ignore other efforts underway
PC: just want to be sure that everyone knows that the 2 sub-groups (encrypted media and streaming) are likely to publish FPWDsearly in the new year
JS: hoping that protected media and accessibility goals can be achieved
<paulc> Leaving to get ready for the WG meeting
JS: anyone?
<chaals> ACTION-149?
<trackbot> ACTION-149 -- Charles McCathie Nevile to follow up old action items and see which remain relevent -- due 2012-12-06 -- OPEN
<trackbot> http://www.w3.org/WAI/PF/HTML/track/actions/149
chaals: have not had time to address that
action 148 on JF - stalled
<trackbot> Sorry, couldn't find 148. You can review and register nicknames at <http://www.w3.org/WAI/PF/HTML/track/users>.
147 - ongoing
146 - will be closed
145 - completed
144 - incomplete at this time
anything prior is covered by action 149
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/the text sub-team should be in/the TF to be in/ Succeeded: s/CfrC/CFC/ Succeeded: s/instead/in the next 6 weeks or so/ Succeeded: s/yeart/year/ Succeeded: s/JSW/JS/ Found Scribe: JF Inferring ScribeNick: JF WARNING: No "Present: ... " found! Possibly Present: Cynthia_Shelly David David_MacDonald IanPouncey JB JF JS Janina_Sajka John_Foliot Judy MichaelC Microsoft P11 PC Stevef chaals cyns darobin davidb hober html-a11y inserted janina joined paulc richardschwerdtfeger trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Found Date: 06 Dec 2012 Guessing minutes URL: http://www.w3.org/2012/12/06-html-a11y-minutes.html People with action items: chaals WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]