See also: IRC log
<LJWatson> Scribe: Hans Hillen
<hhillen> scribe: hhillen
HH: 16 new bugs
... Majority were bugs from Leif about longdesc
... not sure if we need to track these
LW: Just add the number to the chat, Charles is probably on top of those since it's his extension
HH: Longdesc related bugs:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21436&list_id=7384
@longdesc should, like @src, be a valid *non-empty* URL.
Longdesc related, Fixed, no need to track
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21437&list_id=7384
Say that @longdesc should point to *accessible* descriptions
Longdesc related, not sure if this needs to be tracked
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21438&list_id=7384
Relocate the informative NOTE on authoring Best Practices to where it is relevant.
Not sure if this needs to be tracked
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21493&list_id=7384
Describe the longdesc link rot issue and suggest how to combat it
Longdesc related, not sure if this needs to be tracked
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21494&list_id=7384
Describe data URIs as a valid use of the longdesc attribute
Longdesc related, not sure if this needs to be tracked
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21501&list_id=7384
Advice to conformance checkers section
Longdesc related, not sure if this needs to be tracked
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21564&list_id=7384
Allow ATs/UAs to use heuristics to suppress presentation of erroneous or pointless longdescs
Longdesc related, not sure if this needs to be tracked
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21565&list_id=7384
Should it be an error to use @longdesc on presentational images? And/Or should it _affect_ the role of the image?
Longdesc related, not sure if this needs to be tracked
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21566&list_id=7384
User agents must present longdesc through normal interfaces.
Longdesc related, not sure if this needs to be tracked
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21571&list_id=7384
The sub-sentence "but there are many resources available" etc.
Longdesc related, not sure if this needs to be tracked
HH: Additional bugs:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21420
Bug 21420 - note about conforming image is incorrect
No need to track
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21421&list_id=7384
add aria-label and aria-valuetext to list of translatable attributes in html 5.1
HH: no need to track
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21579&list_id=7384
Empty @alt should not imply role="presentation" if the <img> has @usemap
LW: We should probably push this up to the TF, I will get their decision on it and if necessary add the keyword later.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21615&list_id=7384
refer to details not summary in reference to open element
<MichaelC> scribe: MichaelC
hh: seemed editorial
lw: agree
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21623
hh: editorial, looking for example, no need to track
lw: agree
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21563
hh: this essentially functions as Steve´s announcement that he plans to remove hgroup from the spec
lw: no need for TF tracking of the bug
mc: are we happy with the decision to remove hgroup? There were various opinions
lw: there´s discussion about using <small> element for sub-headings
mc: seems worse than hgroup
lw: agree
hh: what is point of hgroup
mc: for sub-headings
do see value in it
though lots of room for author misunderstanding and a11y problems from bad implementation
lw: can take to TF
hh: seems marginal value compared to other stuff we´re working on
mc: see no value in pushing if it´s not implemented
but too bad, thought was good to meet the use case
hh: you could meet this with ARIA, and aria-level
https://www.w3.org/Bugs/Public/show_bug.cgi?id=9280
looks like this was moved to WhatWG product, and Ian started processing
lw: a couple seem to be assigned to CSS, why do they have TF keyword
mc: they may have been originally HTML bugs that were subsequently moved to other groups
may be legitimate to do that, we´ve seen bugs that were more appropriate to another spec
lw: but then they´re not TF bugs, they´re PF issues
mc: yes, something to worry about process-wise to hand off
lw: will raise question with TF
https://www.w3.org/Bugs/Public/show_bug.cgi?id=9544
mc: has TF keyword, but we never triaged this in
somebody just randomly added it, not sure who that person is
lw: will remove TF keyword
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12999
another one moved to WhatWG, but cloned to HTML as 19039
lw: so can move the TF keyword from the WhatWG one, and just track the HTML one
but that one was promptly marked resolved later, so we´ll need to track that
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13576
mc: also moved to WhatWG
again cloned to make 19044
similarly promptly marked as resolved later
lw: we´ll look at resolved later next week
<hhillen> MichaelC: The minutes link leads to a 404 page, is there something else I need to do?
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) Found Scribe: Hans Hillen Found Scribe: hhillen Inferring ScribeNick: hhillen Found Scribe: MichaelC Inferring ScribeNick: MichaelC Scribes: Hans Hillen, hhillen, MichaelC ScribeNicks: hhillen, MichaelC Default Present: [IPcaller], +44.117.929.aaaa, Cooper, Michael_Cooper Present: Léonie_Watson Hans_Hillen Michael_Cooper Got date from IRC log name: 10 Apr 2013 Guessing minutes URL: http://www.w3.org/2013/04/10-a11y-bugs-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]