See also: IRC log
<trackbot> Date: 17 January 2013
<Stevef> chaals:np
<MichaelC> scribe: lwatson
<Stevef> http://lists.w3.org/Archives/Public/public-html-a11y/2013Jan/0096.html
JS: Did you update the summary Steve?
SF: I just responded to two points with James.
JS: The original point James made
was that we hadn't correctly positioned his objection in the
summary.
... We should at least correctly reflect people's positions. We
could ask him to rewrite that part?
SF: I'll update it and ask James to look at it.
JS: This is waiting on me.
<paulc> Can we have the bug numbers?
SF: Not directly related, but
there are some alt text issues related to HTML5 that I filed
some bugs against.
... They were discussed and addressed quickly and positively,
which is a good sign we can get things done.
PC: What are the bug numbers? Are there more coming?
SF: The bugs were closed and the updated text went into 5.1. My email after that suggested the same changes should be made to the 5.0 CR.
<Stevef> http://lists.w3.org/Archives/Public/public-html-a11y/2012Dec/0090.html
PC: Do these bugs cover all the problems previously identified?
SF: This is an sample of relatively minor things that need to be changed.
PC: I understand.
... Bug 12726 has a tracker, and it's held up in the works. The
WG has been asked to hold off discussing it. We need to know
what the status of the remaining tracker issues is.
JS: With Plan 2014 we agreed to take up the conflict between WCAG and section 4.8 with the editors to see what could be resolved. Sorry, I've been unable to move that forward.
<Stevef> http://lists.w3.org/Archives/Public/public-html-admin/2013Jan/0002.html
PC: I thought the result would be
that bugs would be filed and resolved through this discussion
with the editors. Hence me asking where are the bugs.
... I'm not wild about the editors making changes to either 5.0
or 5.1 without a papertrail of bugs.
... Steve, your email is why I put it on hold with the WG.
SF: Thank you.
JS: We don't want W3C specifications to be rubbing against each other.
PC: Another reason it would be good to do this via bugs... If we make changes via bugs, Ian tracks those, so it may be more likely the same changes will be applied to the WHATWG spec.
<JF> scribe: JF
Bug triage reports: Leonie
LW: making good progress and have cleared all that have been marked closed and/or won't fix
there remain 3 that may require some more TF input
<lwatson> https://www.w3.org/Bugs/Public/show_bug.cgi?id=13541
the balance of open issues have been assigned to specific people, and now this is becoming something of a project managament issue
JS: shall we look at those 3
SF: reviewing the 1st bug
Accessibility and SVG
JS: Rich has been active in deploying ARIA in SVG - wonder if there is anything they might have to contribute
<lwatson> https://www.w3.org/Bugs/Public/show_bug.cgi?id=13657
SF: Suggest we ask Rich to review
MC: will assign to Rich
LW: believe this was filed by Cyns
MC: Ted (on this call) was the person to initially reject this bug
SF: Not clear why this is an a11y issue - seems to be something of a more general issue
possibly affects more than just PWD
Hober: Agree that it doesn't seem to be an a11y issue, is more about the design of input range
assumption that any kind of range input is more coarse than a direct input of a value
is that correct? value judgement - the platform also provides for a finer input control
SF: suggest removing a11yTF keyword
Hober: likely worth revisiting n the larger WG, but not really an a11y issue
<lwatson> 13639 (CSS bug?):
JS: we should email person (Cyns) that this should likely be brought to the the larger WG, but that a11yTF keyword being removed
<MichaelC> https://www.w3.org/Bugs/Public/show_bug.cgi?id=13639
LW: will notify Cyns
<lwatson> https://www.w3.org/Bugs/Public/show_bug.cgi?id=13639
MC: it is true that this should actually be taken up with the CSS-WG, but we want to ensure that this is not lost - perhaps we need to hand this to the PF
we can perhaps close this and re-open at PF
SF: if this has no direct impact on the HTML spec, perhaps we should do that
+Q
JS: not happy that we just drop this, but perhaps PF should talk directly to the CSS-WG
<MichaelC> HTML says ¨CSS2 System Colors are not recognised¨
<MichaelC> CSS 3 says system colors are deprecated
<lwatson> JF: Perhaps this is an issue PF could discuss with CSS at the F2F later in the year?
<lwatson> MC: My recollection is that the colours were deprecated to be replaced by something better, excpet the "something better" never happened.
?me Leonie, are you taking back scribe duties?
s/ ?me Leonie, are you taking back scribe duties? /
<scribe> scribe: lwatson
MC: HTML is choosing to honour the deprecated status, but doesn't have to, but it's difficult to know where the responsibility sits.
JS: Ted, you're on CSS, any ideas?
TOC: Contact CSS and describe your concerns.
MC: We did that a while
back.
... We'll triage the bug as reopened, and reassign it to
someone.
JS: I can work with Michael on this, let's put Michael as placeholder assignee.
<paulc> I need to leave a little early today to get ready for the HTML WG Weekly teleconference.
<paulc> Anything else on the agenda for me?
<paulc> ok
LW: We really need the sub teams to process the outstanding bugs.
SF: The main element has been
added to 5.1 core.
... It's another sign of the good working relationship we have
with the editors.
SF: Everyone, pplease review that email.
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/Rick/Rich/ FAILED: s/ ?me Leonie, are you taking back scribe duties? // Found Scribe: lwatson Inferring ScribeNick: lwatson Found Scribe: JF Inferring ScribeNick: JF Found Scribe: lwatson Inferring ScribeNick: lwatson Scribes: lwatson, JF ScribeNicks: lwatson, JF Default Present: John_Foliot, hober, lwatson, Michael_Cooper, Janina_Sajka, Steve_Faulkner, paulc Present: John_Foliot hober lwatson Michael_Cooper Janina_Sajka Steve_Faulkner paulc Regrets: chaals WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 17 Jan 2013 Guessing minutes URL: http://www.w3.org/2013/01/17-html-a11y-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]