See also: IRC log
<Steven> SOrry, I'm at a Forms FtF and not able to join by phone
<Steven> Hmm
<Steven> I don't think Mark is joining by phone either
we might want to take a week off...
<oedipus> reviewed latest draft of RFDa - excellent - should be required reading for the HTML WG!
rotfl
<Steven> Thanks Oedipus
<oedipus> s/RFD w/RDF
regrets from Yam. Partial regrets from Tina, Mark, and Steven
<markbirbeck> Hi everyone...I'm Skyped into the XForms FtF, so can't attend.
<markbirbeck> I regret nothing.
<alessio> hi mark
<markbirbeck> hi
<markbirbeck> (Not even partially.)
Oops...
Gregory likes it
Shane wants it in the XHTML 2 Working group publication system.
<oedipus> gregory would like to be able to point to it as required reading on HTML WG wiki
<Steven> I will talk to Ben about his position in integrating it into our system
<Steven> he is one of the editors, and it is in XML Spec
Rich wants to know if we should add an attribute to access that defines the event to be triggered... where the default would be focus
<Steven> so it would mena a change for him
Gregory points out issues with accessibility and event triggering....
Shane mentioned that we tend to avoid talking about processing model at this level. But thinks it is a good idea.
Shane asks if Gregory has a concrete proposal? Not quite yet. It is a question of bidirectionality of the event model.
Need a way to support enqueueing an event that may percolate into the operating system backplane, as opposed to only working in the context of the application.
webbie.org.uk has a suite of tools that are accessible; might be a good example to look at?
<scribe> ACTION: Gregory to put together a proposal for how to connect the access module into the event model. [recorded in http://www.w3.org/2007/06/13-xhtml-minutes.html#action01]
<scribe> ACTION: Shane to investigate a wiki space for XHTML 2 working group [recorded in http://www.w3.org/2007/06/13-xhtml-minutes.html#action02]
<oedipus> latest version of Embedding State and Properties Roles in HTML: http://www.w3.org/WAI/PF/adaptable/HTML4/
<oedipus> editor's latest draft of Embedding State and Properties: http://www.w3.org/WAI/PF/adaptable/HTML4/embedding-20061212.html
(still)
Rich would like to have XML Events tied to it. I think that is icing on the cake.
Default is to give something focus. Do we want to have the option of activating the target.
Originally the model was if you want to do that you would use an xml events attribute to indicate that. Since we are not requiring
http://www.w3.org/MarkUp/2007/ED-xhtml-access-20070606/
Rich asked if there was a way to describe the element. @title seems to be the way.
<alessio> i agree
Shane thinks we should be able to fire any event when an accessor is selected.
HTML4 problem is that we dont know what the key was going to do at all.
Sometimes a document author wants to create an accelerator....
Sometimes this stuff is really about enabling assistive technologies.
What we say now is: The Character assigned to a key, and its relationship to a role or id attribute, are a suggestion of the author. User agents may provide mechanisms for overriding, disabling, or re-assigning keys. In such user agents, user-specified assignments must take precendence.
We probably want to say something similar about what event fires.
We need to look at the list of potential events...
Agreed that we are going to allow the firing of essentially any DOM event. Some may not make sense.
Need some concept of "hang fire" so that the user agent can suspend and offer options to the user.
Is there a way to introduce / permit the document author or AT to specify an intermediary step.
Rich points out that xml events deals with this.
requiring xml events will impede adoption.
<Tina> Can XML's method of dealing with it be used directly?
Rich would like to put a shortcut in there... the same way we have done for a keybinding.
Shane proposes that we call the attribute "raise". Or "trigger"
Only include the discrete events that do not require coordinates...
If you really want to have full support, use XML Events. say that in the spec.
No objections.
<scribe> ACTION: Shane to update access module draft to include new attribute and text. [recorded in http://www.w3.org/2007/06/13-xhtml-minutes.html#action03]
Rich sent in comments. No one else has.
Everyone was very quiet - it must be perfect.
Out of things to discuss without Mark and Steven...
<oedipus> like the fact that the example in section 3 uses accessibility markup!
<scribe> ACTION: Vote on last call for Role and Access next week. [recorded in http://www.w3.org/2007/06/13-xhtml-minutes.html#action04]
<oedipus> quit
This is scribe.perl Revision: 1.128 of Date: 2007/02/23 21:38:13 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) FAILED: s/RFD w/RDF/ No ScribeNick specified. Guessing ScribeNick: ShaneM Inferring Scribes: ShaneM Default Present: +1.763.767.aaaa, ShaneM, Gregory_Rosmiata, alessio, [IBM] Present: +1.763.767.aaaa ShaneM Gregory_Rosmiata alessio [IBM] Steven Mark Tina Regrets: Yam Agenda: http://lists.w3.org/Archives/Public/public-xhtml2/2007Jun/0008 Got date from IRC log name: 13 Jun 2007 Guessing minutes URL: http://www.w3.org/2007/06/13-xhtml-minutes.html People with action items: gregory shane vote WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]