<oedipus> http://www.w3.org/AudioVideo/TT/
<oedipus> http://www.w3.org/TR/2006/CR-ttaf1-dfxp-20061116/
<oedipus> cyns have you tried the markup specification "view"
<oedipus> cyns, can you colect examples so we can work on actual wording?
<oedipus> http://dev.w3.org/html5/markup/
<scribe> scribe: jcraig
<oedipus> http://dev.w3.org/html5/markup/aria/
CS: there should be markup examples in the spec
<oedipus> scribenick+jcraig
JS: not rready for a bug, but we
shouldn't drop this issue yet
... guests, any thoughts before we move on?
<Lachy> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/232
LH: i have a demo of the <details> element
*shows details toggle demo*
CS: That's what I thought it would be, but the readability of the spec was hard to parse/understand
<oedipus> NOTE: we are now logging to www.w3.org/2009/11/04-pf-minutes.html due to UTC day change
CS: so toggle() would be built in?
LH: yes, native implementation
<oedipus> scribe: jcraig
<oedipus> scribenick: jcraig
CS: doesn't specify whther there is a focus style, default tabindex, etc.
LH: I agree. If it does not specify that, it should.
GR: now logging to new URI, due to GMT date switch
CS: In each tag section, I'd like
to see markup code examples and plain English descriptions of
browser interaction
... re: command element, if content model is empty, there can't
be tags inside?
LH: yes, there is no content, b/c
it's a hidden element
... command is bound to other controls, but remains empty
... e.g., menuitemradio example, command element is the data
store for data binding other element's views to a single data
source
CS: didn't understand
relationships between commands and bound elements, that part of
the spec could be more clear
... why are synthetic events more limited that physical
events
... this worries me. What are the security reasons? b/c this
could get in the way of some AT
... The spec should say why it's not allowed
<richardschwerdtfe> say it isn't so
MC: the readability issues could be that we're just not familiar with the docs
JC: in fairness, our own docs have some readability issues too
<richardschwerdtfe> I need to blow this garage
<richardschwerdtfe> you all have a great evening
<richardschwerdtfe> bye
<richardschwerdtfe> :-)
MC: let's review Ben Caldwell's comments
embed element, figure, img, etc
only img and area have @alt
needed for figure, embed, video, canvas, audio, etc.
MC: as in WCAG, it's been unclear
as to what "fallback content" means
... even if the content is rendered, is it perceivable to the
user
... spec doesn't even provide the ability to render fallback
content in other modalities based on user pref or ability
<oedipus> "cascade" of escriptors (alt, title, etc.)
[details of ben's comments, will be submitted to html wg bugzilla]
<kford> Interesting because in UAAG 2 we are looking at asking user agent to offer this cascade of alternatives.
<oedipus> http://esw.w3.org/topic/PF/XTech/Iframe
GJR: spec explicitly forbids iframe resizing
for low vision users, that means excessive scrolling
s/cascase/cascade/
<oedipus> http://esw.w3.org/topic/PF/XTech/IFrame
GJR: cross-check with Open AJAX group
MC: let's switch to low-hanging fruit
<oedipus> caution: fruit may appear to hang lower than it actually does
KF: tomorrow's schedule, create an accessibility birds of a feather table?
JS: it should be more specific than just "accessibility"
JC: 'canvas accessibility' for example
<oedipus> http://www.w3.org/TR/2008/PR-xhtml-modularization-20080611/DTD/xhtml-iframe-1.mod
<oedipus> http://www.openajax.org/member/wiki/OpenAjax_Hub_1.1_Roadmap#Leveraging_IFRAMEs_for_mashup_security
KF: 'media accessibility' too
<oedipus> http://www.w3.org/html/wg/html5/#the-iframe-element
JF: would continue discussion from Sunday
<oedipus> talk to alessio cartucci about flash accessibility -- or MATT!
LH: on by default , but overrideable by a pref
CS: could cause seizures
JS: browser vendors attorneys should review whether marquee should be on by default
MC: unlikely that marquee will cause seizures
JS: are UAAG comments in HTML bugzilla?
KF: I'll follow up
and make sure they are added to bugzilla
MC: we've now met the chairs request to submit issues
<scribe> ACTION: cooper to create candidate HTML Bugzilla entries from PF comments for PF consideration [recorded in http://www.w3.org/2009/11/04-pf-minutes.html#action01]
<trackbot> Created ACTION-538 - Create candidate HTML Bugzilla entries from PF comments for PF consideration [on Michael Cooper - due 2009-11-11].
JS: What about PF concerns that
we're not yet ready to bring up with the HTML WG? How do we
track those?
... I'm hopeful the HTML a11y task force will be officially
created this week.
MC: we could track them in the PF Wiki
GJR: or ESW wiki
... I'm willing to track the issues there
JS: guests, what areas of out HTML5 review matrix still need the most review?
MC: *summarizes review state of specific sections*
SF: There is ASCII art of dialogs in the spec somewhere. Just a bug.
JS: assigning the HTML5 forms review to both GJR and CS
MC: Drag and drop still assigned to Ben Caldwell
<scribe> ACTION: Rich to review HTML 5 section 7.10 Drag and Drop [recorded in http://www.w3.org/2009/11/04-pf-minutes.html#action02]
<trackbot> Created ACTION-539 - Review HTML 5 section 7.10 Drag and Drop [on Richard Schwerdtfeger - due 2009-11-11].
(missed the action from this morning)
<kford> kford to look at sections 11.1-3 in html 5 spec and also window object from section 6.
Kelly Ford: I will review 11.1, 11.2, 11.3, and I will find someone from UAAG to review the window and windowProxy stuff in section 6
Frank Olivier and James Craig to review contenteditable, section 7.8
<scribe> ACTION: folivier2 to review HTML 5 section 7.8, contenteditable [recorded in http://www.w3.org/2009/11/04-pf-minutes.html#action03]
<trackbot> Sorry, couldn't find user - folivier2
<scribe> ACTION: Frank Olivier to review HTML 5 section 7.8, contenteditable [recorded in http://www.w3.org/2009/11/04-pf-minutes.html#action04]
<trackbot> Sorry, couldn't find user - Frank
<scribe> ACTION: jcraig to review HTML 5 section 7.8, contenteditable (and remind frank olivier to do so as well) [recorded in http://www.w3.org/2009/11/04-pf-minutes.html#action05]
<trackbot> Created ACTION-540 - Review HTML 5 section 7.8, contenteditable (and remind frank olivier to do so as well) [on James Craig - due 2009-11-11].
KF: please file UAAG bugs as well
<oedipus> bless you
<kford> kford will also look at 6.7 on user prompts.
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/menuitemcheckradio/menuitemradio/ Succeeded: s/cascase/cascade/ FAILED: s/cascase/cascade/ Succeeded: s/prefs/pref/ Found Scribe: jcraig Inferring ScribeNick: jcraig Found Scribe: jcraig Found ScribeNick: jcraig Default Present: Steve_Faulkner, Janina_Sajka, Sally_Cain, Cynthia_Shelly, Michael_Cooper, James_Craig, Frank_Olivier, John_Foliot, Kelly_Ford, Laura_Carlson, Matt_May, Rich, Gregory_Rosmaita, Lachlan_Hunt, Loretta_Guarino_Reid Present: Steve_Faulkner Janina_Sajka Sally_Cain Cynthia_Shelly Michael_Cooper James_Craig Frank_Olivier John_Foliot Kelly_Ford Laura_Carlson Matt_May Rich Gregory_Rosmaita Lachlan_Hunt Loretta_Guarino_Reid WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 Guessing minutes URL: http://www.w3.org/2009/11/04-pf-minutes.html People with action items: cooper folivier2 frank jcraig olivier rich WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]